LiveLive coverage · EA
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 11% of all ranked servers, top 45% in EA, and #146 of the quad servers (top 18%). Ranked on player hours over the last seven days.
Coming up · wipe schedule
from its schedule tag
Next wipe Friday 30 October, 08:51 UTC, in 1d 7h. Its biweekly schedule tag · low confidence
Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.
The current map
Friday 16 October 2026, 08:51 UTC
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.
The average peak across its recent wipes is 2 players. The crowd on the latest wipe peaked 5 hours in.
With too few of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's wipes recorded to confirm the schedule, the tag is used for the prediction. Expect the next wipe on Friday 30 October at 08:51 UTC. 12 days 16 hours have passed since this world was generated. A two-weekly wipe schedule appears in its tags.
These are the Rust Live Stats lists [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け fits: Live Rust community servers and Vanilla Rust servers, live. You will find it on the server list under 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.
The server browser reads gmrust (Game mode): Standard survival, in the Rust style; mp100 (Max players): The slot count is 100; ts4 (Group limit): Team cap: 4; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^b (Biweekly): Expect a wipe each two weeks; ^v (Vanilla): No changed rates, kits or rules — this is the game as Facepunch ships it; EA (East Asia): The server browser places this server under East Asia, which [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け publishes. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
0 of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's 100 slots are filled right now. The seven-day average is 2 players, with a peak of 6. Peak hour over 48 hours: 10:00 UTC, at 3 players on average.
[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is #254 in Asia on the past week's player hours, and #2,546 overall in the top 11% of ranked servers. Ranked against other quad servers, it comes in at #146.
No gather rate appears in the name [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. The limit is 4 players to a group (quad). survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser lists it under Community. Its self-description is vanilla: no changed rates, kits or rules — this is the game as Facepunch ships it. VAC is enabled: Valve's anti-cheat.
Size 3,500, seed 1029781210: that is the procedural map the game generates for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. Same size, same seed, same map: RustMaps has it, reachable from this page.
Its EA tag places [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け in Asia. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 162.43.16.74:28015.
The average server fps was 147 over the last 48 hours; the lowest was 96. Entity count reached 58,066: buildings, deployables and the rest of the world. The highest memory usage was 2,127 MB. Players experience lag when fps is low and the entity count climbs.
[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け operates on Linux with Rust network protocol 2635 and build 168909. To join, your game must use the same protocol; Steam handles the update for you.
Right now [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is online. Based on the uptime it reports, the last restart was about 33 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. On 2 October 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 162.43.16.74:28015. You can find its website at https://discord.com/invite/n4cemh8hm5.