Rust Player Stats
Live UTC 75,412 playing

Online EA 162.43.16.74:28015 checked 13m ago

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け

quad biweekly wipes vanilla
Players now3
Slots100
Full3%
7-day average2peak 6
Rank#2,495top 11% · #250 in EA
Last wipe12d agobiweekly schedule
Next wipe1d 19hFri 30 Oct, 08:51 UTC
Launch Rust and join Website

By the numbersMatch stats

against its 100 slots
Players now3
3% of the slots taken
7-day average2
players on an average hour this week
7-day peak6
the fullest it got this week
48-hour peak4
the busiest hour of the last two days
On the list47 of 48 hours
hours it answered in the last two days
Server fps146
average over 48 hours; 60 or more is smooth
Standingtop 11%
of all ranked servers, on player hours over seven days
Replay

The story of the match

Players, performance and rank, hour by hour and day by day.

CrowdPlayers

AveragePeak
0123414:0023:0008:0018:0003:0012:00

Hourly average and peak, UTC.

FitnessServer performance

010020030040014:0023:0008:0018:0003:0012:00

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

FormRank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k2 Oct7 Oct12 Oct18 Oct23 Oct28 Oct

Top 11% of all ranked servers, top 45% in EA, and #144 of the quad servers (top 17%). Ranked on player hours over the last seven days.

FixturesWipe schedule

from its schedule tag

Next wipeFriday 30 October, 08:51 UTCin 1d 19h Its biweekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

  1. 1d 19hFri 30 Oct, 08:51 UTC
  2. 8d 5hThu 5 Nov, 19:00 UTCFW
  3. 15d 19hFri 13 Nov, 08:51 UTC
  4. 29d 19hFri 27 Nov, 08:51 UTC
  5. 36d 5hThu 3 Dec, 19:00 UTCFW
  6. 43d 19hFri 11 Dec, 08:51 UTC

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.

ResultsWipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:51 UTC12d ago 2 – running 0

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Other matches on now

Similar servers

The same kind of game, then region, group limit, rate and wipes.

The pundits

Quick answers

From the figures on this page.

About the server

Is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け online, and how reliable is it?

Online now, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is up. Going by the uptime it reports, the last restart came about 21 hours ago. 168 of 168 hours were up over the last 7 full days, 100% of the time. Rust Player Stats logged it for the first time on 2 October 2026.

Does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け run smoothly?

146 server fps on average over 48 hours, and never under 96. Its entity count reached 58,066: buildings, deployables and the rest of the world. The memory ceiling was 3,264 MB. Lag, to a player, is these two together: low fps and a rising entity count.

Which Rust version is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け on?

On Linux, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け runs Rust network protocol 2635 and build 168909. To get in, your game needs the same protocol; Steam handles the update.

Where is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け located?

The EA tag on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け puts it in Asia. Rust Player Stats takes the server's word on where it is and does not look up the machine's real location. You will find it at 162.43.16.74:28015.

Lists and filters

What do the server tags on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け mean?

Tags published by [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け and picked up by the in-game browser: gmrust (Game mode): The standard Rust survival rules apply here; mp100 (Max players): The cap is 100 slots; ts4 (Group limit): Teams cap at 4; v2635 (Protocol): To join, your game has to run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer RakNet is in use; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is two weeks per wipe; ^v (Vanilla): No changed rates, kits or rules: it's the game as Facepunch ships it; EA (East Asia): East Asia is where the browser lists it. You will also find its current players, its queue and the age of its world in the tags, shown at the top of this page.

Which Rust Player Stats lists and filters include [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

These Rust Player Stats lists take [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け: Community servers, ranked live and Vanilla Rust servers. Searching the server list with these filters returns it: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b and Vanilla ^v; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Rules and settings

Which map is running on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

The procedural map on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is size 3,500, generated by the game from seed 1029781210. You can look at it on RustMaps from this page, since size and seed give the same map.

What are the rules and settings on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

No gather rate appears in the name of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. The group cap is 4 players (quad). It plays as survival, gather, build, raid: the standard game. PvP is on, and so is raiding. Community is its server browser category. Its self-description is vanilla: no changed rates, kits or rules: it's the game as Facepunch ships it. VAC is on, so Valve's anti-cheat is watching.

Live counts

How full is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け right now?

Out of 100 slots, 3 are taken on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け at this moment. Seven days back gives an average of 2 players and a peak of 6. It drew its biggest crowd of the last 48 hours at 17:00 UTC: 3 players on average.

Where does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け sit in the rankings?

In Asia it is #250, and #2,495 on seven-day player hours, in the top 11% of all ranked servers: [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. Among servers in the quad group, it ranks #144.

Wipe timing

What is the wipe schedule on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

With so few of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's wipes logged, its tag is what the prediction goes on, not a confirmed schedule. On Friday 30 October at 08:51 UTC, its next wipe is due. The world it runs now was made 12 days 4 hours ago. The wipe schedule in its tags is every two weeks.

What does wipe day look like on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

At their busiest, its recent wipes drew 2 players on average. 5 hours after the wipe, the crowd peaked on the latest wipe.

Joining the server

How do I join [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

Console route: F1 in Rust, then client.connect 162.43.16.74:28015. Or use Launch Rust here, which opens Rust through Steam and connects you. You will find the website at https://discord.com/invite/n4cemh8hm5.

GlossaryServer tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^v,EA,gmrust,cs168909,ts4

Game

gmrust
Game mode The standard Rust survival rules apply here.
mp100
Max players The cap is 100 slots.
ts4
Group limit Teams cap at 4.
v2635
Protocol To join, your game has to run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer RakNet is in use.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The cycle is two weeks per wipe.

Difficulty

^v
Vanilla No changed rates, kits or rules: it's the game as Facepunch ships it.

Region

EA
East Asia East Asia is where the browser lists it.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.