Rust PopulationField survey · Rust servers
Observing 51,299 players 11,732 servers 3,302 with someone on 118 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 2,545EAfirst seen 2 Oct 2026

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

Online EA 162.43.16.74:28015 checked 12m ago

quad biweekly wipes vanilla

Measurements

Players now
0/ 100
0% full
7-day average
2
peak 6
Rank
#2,545
top 11% · #258 in EA
Last wipe
12d ago
biweekly schedule
Next wipe
1d 8h
Fri 30 Oct, 08:51 UTC
Obs. 1 · sightings

Players

AveragePeak
0123400:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

010020030040000:0009:0018:0003:0012:0022: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.

Obs. 3 · standing

Rank

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

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

Obs. 4 · the wipe cycle

Wipe schedule

from its schedule tag

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

2
wipe-day peak
players, last three wipes

Coming wipes

1d 8h
Fri 30 Oct, 08:51 UTC
7d 19h
Thu 5 Nov, 19:00 UTC
FW
15d 8h
Fri 13 Nov, 08:51 UTC
29d 8h
Fri 27 Nov, 08:51 UTC
35d 19h
Thu 3 Dec, 19:00 UTC
FW
43d 8h
Fri 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.

Log · wipes seen

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.

Field questions

Quick answers

from the figures on this page

Player counts

How does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け rank against other Rust servers?

On player hours over the last seven days [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is #2,545, #258 in Asia, placing it in the top 11% of ranked servers. It places #146 among servers of the quad kind.

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

Of its 100 slots, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is using 0 right now. We counted an average of 2 players in the past week, with 6 at the busiest. Look at the last 48 hours and 10:00 UTC stands out: it averaged 3 players.

Tags

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

The game's server browser reads the tags [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け publishes: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): You can join up to 100 slots; ts4 (Group limit): You may team with up to 4 players; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks the server wipes; ^v (Vanilla): No kits, no rate changes, no rules added: the game as Facepunch ships it; EA (East Asia): Its place in the server browser is under East Asia. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

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

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け appears among the Rust Population lists that follow: Community servers, field-listed and Vanilla Rust servers, counted. Filter the server list by 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 and it will show up.

Wipe schedule

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

The busiest point of its recent wipes averaged 2 players. Peak came 5 hours into the latest wipe.

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

The prediction follows its tag, since too few of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's wipes are on record to confirm the schedule. A wipe is due on Friday 30 October at 08:51 UTC, the next one. Counted from 12 days 15 hours ago, that is how long the current world has stood. The tags carry an every-two-weeks wipe schedule.

Settings

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

A procedural map of size 3,500 from seed 1029781210, generated by the game, is in use on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. Size and seed together fix the map, so you can view it on RustMaps from this page.

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

Nothing in [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's name says how gather works. 4 is the most a group can hold (quad). This server runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players is allowed. A community server, it appears in the Community section of the browser. The server describes itself as vanilla: no kits, no rate changes, no rules added: the game as Facepunch ships it. The anti-cheat VAC from Valve is enabled.

About the server

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

On Linux, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam updates it for you.

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

In the last 48 hours, it averaged 147 server fps, with a low of 96. The entity count reached 58,066: buildings, deployables and all other objects. The highest memory usage was 2,127 MB. Lag, as players feel it, is low fps combined with a climbing entity count.

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

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is up and running at the moment. Judging by the uptime it reports, the last restart was about 31 hours ago. Over the last 7 full days, 168 of 168 hours were online, or 100%. The first sighting by Rust Population was on 2 October 2026.

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

With its EA tag, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け places itself in Asia. The location a server claims is what Rust Population shows, not the place where the machine stands. 162.43.16.74:28015 is where it lives.

How to join

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

Either enter client.connect 162.43.16.74:28015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected. You can find its website at https://discord.com/invite/n4cemh8hm5.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp100
Max players You can join up to 100 slots.
ts4
Group limit You may team with up to 4 players.
v2635
Protocol The protocol is 2635; a different version will not connect.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Difficulty

^v
Vanilla No kits, no rate changes, no rules added: the game as Facepunch ships it.

Region

EA
East Asia Its place in the server browser is 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.