Skip to main content

Independent statistics on public Rust serversNot affiliated with Facepunch Studios

Latest count: 89,289 players on 11,829 servers
Rust CensusThe census of every public Rust server, counted and refreshed.

Statistical profileOnline

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

EA 162.43.16.74:28015 checked 3h ago

quad biweekly wipes vanilla
Release date
Next release
In five minutes (17:05 UTC)
Source
Live server queries
Server address
162.43.16.74:28015
First recorded
2 October 2026

Connect to this server

Launch Rust and join Website

1. Main points

Players now

1/ 100

1% full

7-day average

2

peak 6

Rank

#2,528

top 11% · #259 in EA

Last wipe

12d ago

biweekly schedule

Next wipe

1d 12h

Fri 30 Oct, 08:51 UTC

Main points

  • There were 1 players on it, 1% of its 100 slots.
  • Over the last seven days it averaged 2 players, with a peak of 6.
  • It ranks #2,528 of all ranked servers, the top 11%, and #259 in EA, on player hours over the last seven days.
  • Its current map went up 12d ago; the next wipe is expected Friday 30 October, 08:51 UTC, its biweekly schedule tag.

2. Players

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

Players now and over time, UTC

AveragePeak
0123421:0006:0015:0023:0008:0017:00

Hourly average and peak, UTC.

Source: Live server queries, Rust Census

3. Server performance

Figure 2: Frame rate, entities and memory

From asking the server directly; low fps and a climbing entity count mean lag

010020030040021:0006:0015:0023:0008:0017:00

Note

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.

4. Rank

Figure 3: Rank among all servers, 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 #147 of the quad servers (top 18%). Ranked on player hours over the last seven days.

Source: Live server queries, Rust Census

5. Wipe schedule

Patternfrom its schedule tag

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

Wipe-day peak

2

players, last three wipes

Table 1: Coming wipes

Expected from its own rhythm and the force wipe

InDate and timeKind
1d 12hFri 30 Oct, 08:51 UTCOwn schedule
7d 22hThu 5 Nov, 19:00 UTCForce wipe FW
15d 12hFri 13 Nov, 08:51 UTCOwn schedule
29d 12hFri 27 Nov, 08:51 UTCOwn schedule
35d 22hThu 3 Dec, 19:00 UTCForce wipe FW
43d 12hFri 11 Dec, 08:51 UTCOwn schedule

Figure 4: The first 48 hours of its last wipes

Players each hour, from the hour of the wipe

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.

Source: Live server queries, Rust Census

6. Wipes

Table 2: Wipes, newest first

Every wipe seen on this server

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

Notes

  1. 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.
  2. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Source: Live server queries, Rust Census

7. Map

Figure 5: Map of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け

3500 · seed 1029781210

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

Table 3: The world

As the server publishes it

MapProcedural Map
Size3500
Seed1029781210
Open on RustMaps

8. Server characteristics

Table 4: Characteristics of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け

What the server publishes and what was recorded

Address162.43.16.74:28015
RegionEA
Max players100
Group limitquad
Wipe schedulebiweekly
Last wipe16 Oct 2026, 08:51 UTC
Hostname–
First seen2 Oct 2026

9. Similar servers

Table 5: Servers like this one

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

ServerCharacteristicsPlayers
[RU] SAHAMUREA · quad · biweekly · 3 on average4 / 100
『小宇宙』10.27号/新开/四人服/萌新服EA · quad · weekly · 21 on average0 / 200
『次空间』10.28号/14:00新开/四人服/萌新服EA · quad · weekly · 20 on average40 / 200
小虎鲸10.25号|14点新档|四人游玩EA · quad · weekly · 12 on average0 / 200
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid HoursEA · quad · weekly · 11 on average10 / 165
TheCove.GG|无权|新手村|四人|10.28号16:00清档EA · quad · weekly · 4 on average1 / 100

10. Quick answers

From the figures on this page.

Wipe details

On what schedule are wipes carried out on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

Too few wipes of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け are recorded to confirm its schedule, so its tag is followed by the prediction. On Friday 30 October at 08:51 UTC the next wipe is expected. The present world dates from 12 days 11 hours. Its tags carry a wipe schedule of every two weeks.

On [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, what happens on wipe day?

An average of 2 players attended at peak across recent wipes. On the latest wipe, 5 hours passed before the crowd peaked.

About the server

Is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け up, and how well has it held up?

At the latest check, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け was online. About 25 hours ago is when it last restarted, according to the uptime it reports. 168 of 168 hours on across the last 7 full days gives an uptime of 100%. The first sighting of it by Rust Census was on 2 October 2026.

What does the performance record of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け show?

Average server fps over the last 48 hours was 146, with a low of 96. The world carried up to 58,066 entities, including buildings, deployables and all else. The peak memory use recorded was 2,127 MB. Players feel low fps and a rising entity count as lag.

In which location is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け based?

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

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

The version in use on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is Rust network protocol 2635 and build 168909 on Linux. To join, your game has to be on the same protocol; Steam handles the update.

Player figures

What are the current player figures for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け stands at 1 players from 100 slots in this release. This release records a seven-day average of 2 players and a peak of 6. The busiest hour in the last 48 hours was 10:00 UTC, with an average of 3 players.

In the rankings of Rust servers, where is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け placed?

This release ranks [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け at #2,528 for seven-day player hours, #259 in Asia, inside the top 11% of ranked servers. The server stands at #147 among quad servers.

Tags, lists

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

The Rust Census lists that [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け fits are: Community servers and Vanilla Rust servers. It appears under these filters on the server list: 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.

Which meanings do the tags on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け carry?

gmrust (Game mode): The game mode is standard survival as Rust runs it; mp100 (Max players): Slots: 100; ts4 (Group limit): The limit is 4 players per team; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): The server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): A wipe is run once a fortnight; ^v (Vanilla): Rates, kits and rules are unchanged from the Facepunch release; EA (East Asia): East Asia is the region under which the browser lists it are the tags [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け publishes, and the game's server browser reads them. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.

Settings and map

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

The procedural map on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is generated by the game, measures 3,500 and carries seed 1029781210. The same size and seed produce the same map; RustMaps shows it from this page.

How is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け configured, and what rules does it keep?

No gather rate is recorded for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け in its name. 4 players is the cap for a group (quad). It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Community. Its own label is vanilla: rates, kits and rules are unchanged from the Facepunch release. Anti-cheat is active: VAC, Valve's system, is on.

Join details

What steps are needed to join [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

Enter client.connect 162.43.16.74:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you. The website recorded for it is https://discord.com/invite/n4cemh8hm5.

11. Server tags

What each tag this server publishes means: a glossary.

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

Game

gmrustGame mode The game mode is standard survival as Rust runs it.
mp100Max players Slots: 100.
ts4Group limit The limit is 4 players per team.
v2635Protocol To connect, your game version must match protocol 2635.
cs168909Build The server runs game build 168909.
ptrakNetworking The network layer is RakNet, the game's standard.
$r?Region code No region code is set.

Wipe schedule

^bBiweekly A wipe is run once a fortnight.

Difficulty

^vVanilla Rates, kits and rules are unchanged from the Facepunch release.

Region

EAEast Asia East Asia is the region under which 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.