StatusLive Servers online11,701 Players40,419 Populated3,002 Wiped · 3 h95 Interval5 min Date29 OCT 2026

DWG RG-S2546Server sheetchecked 10m ago

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

Online EA 162.43.16.74:28015 checked 10m ago

quad biweekly wipes vanilla
Connect
Players now 0/ 100 0% full
7-day average2peak 6
Rank#2,546top 11% · #254 in EA
Last wipe12d agobiweekly schedule
Next wipe1d 6hFri 30 Oct, 08:51 UTC
Fig. 1

Players

AveragePeak
0123402:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

Fig. 1Players on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け
Fig. 2

Server performance

010020030040002:0011:0020:0005:0014:0000: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k2 Oct7 Oct13 Oct18 Oct24 Oct29 Oct

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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 08:51 UTC, in 1d 6h. Its biweekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

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

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[RU] SAHAMUREA · quad · biweekly · 3 on average
2 / 100
02 0 / 165
03
『小宇宙』10.27号/新开/四人服/萌新服EA · quad · weekly · 21 on average
1 / 200
04
『次空间』10.29号/新开/四人服/萌新服EA · quad · weekly · 19 on average
32 / 200
05
小虎鲸10.25号|14点新档|四人游玩EA · quad · weekly · 12 on average
0 / 200
06 1 / 165
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

Is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け online, and what uptime has been recorded?

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is up at this moment. Counted from its reported uptime, the last restart was about 33 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. On 2 October 2026 is when Rust Graphs first saw it.

Is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け stable in the figures recorded?

Average server fps over the last 48 hours is 147; the lowest was 96. Counted at its highest: 58,066 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 2,127 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

With its EA tag, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け lists itself in Asia. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 162.43.16.74:28015.

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

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

Counts

What player count is recorded on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

0 of 100 slots on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け are taken at the latest refresh. The seven-day mean is 2 players; the peak over the same period is 6. Averaged over the last 48 hours, the player count is highest at 10:00 UTC: 3 players.

What rank has been recorded for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

Across seven days, player hours give [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け #2,546 globally and #254 in Asia, a top 11% position among ranked servers. Within the quad group it places #146.

Schedules

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

The recent wipes averaged a busiest count of 2 players. At 5 hours after the latest wipe the crowd was at its peak.

What wipe schedule has been recorded for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

The prediction follows its tag, because too few wipes of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け are on record to confirm the schedule. On Friday 30 October at 08:51 UTC its next wipe is due. The current world has been in use since 12 days 17 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Map and rules

Which rules and settings are recorded for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

No gather rate is stated in the name of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. 4 players per group at most (quad). survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. It appears under Community in the server browser. Vanilla is the label it uses: facepunch's game, unaltered: rates, kits and rules are as shipped. Anti-cheat: VAC, from Valve, is on.

On which map is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け played?

Seed 1029781210 and size 3,500 define the procedural map [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

Where does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け appear among the Rust Graphs lists and filters?

These Rust Graphs lists include [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け: Rust community servers, plotted and Vanilla Rust servers. On the server list, these filters bring it up: 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.

On [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, what is meant by each tag?

Tags published by [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): 100 player slots; ts4 (Group limit): Team size is capped at 4; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Facepunch's game, unaltered: rates, kits and rules are as shipped; EA (East Asia): The browser's listing places it under East Asia. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

What is the way to connect to [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

Connect with client.connect 162.43.16.74:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://discord.com/invite/n4cemh8hm5.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp100
Max players 100 player slots.
ts4
Group limit Team size is capped at 4.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla Facepunch's game, unaltered: rates, kits and rules are as shipped.

Region

EA
East Asia The browser's listing places it under East Asia.

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.

KeyTag string decoded