Rust Server Analytics 32,278 players11,650 servers
All servers
Drill-through Server detail

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

Online EA 162.43.16.74:28015 checked 9m ago

Drill-through
FilterServeris [JP] Tokyo Vanilla Server | Quad/Bi-Weekl…
Attributes
quad biweekly wipes vanilla
Last refreshed
Players now 0/ 100
7-day average 1 peak 6
Rank #2,559 top 11% · #248 in EA
Last wipe 12d ago biweekly schedule
Next wipe 1d 4h Fri 30 Oct, 08:51 UTC
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123405:0014:0023:0007:0016:0002:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
010020030040005:0014:0023:0007:0016:0002: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.

Rank

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

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

Wipe schedule

from its schedule tag

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

wipe-day peak2players, last three wipes

Coming wipes

InWhen, UTCKind
1d 4hFri 30 Oct, 08:51 UTCits own
7d 14hThu 5 Nov, 19:00 UTCFW force wipe
15d 4hFri 13 Nov, 08:51 UTCits own
29d 4hFri 27 Nov, 08:51 UTCits own
35d 14hThu 3 Dec, 19:00 UTCFW force wipe
43d 4hFri 11 Dec, 08:51 UTCits own

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.

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
[RU] SAHAMUR EA · quad · biweekly · 3 on average 3 / 100
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours EA · quad · weekly · 44 on average 0 / 165
『小宇宙』10.27号/新开/四人服/萌新服 EA · quad · weekly · 21 on average 0 / 200
『次空间』10.29号/新开/四人服/萌新服 EA · quad · weekly · 19 on average 32 / 200
小虎鲸10.25号|14点新档|四人游玩 EA · quad · weekly · 12 on average 0 / 200
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours EA · quad · weekly · 7 on average 2 / 165

Quick answers

from the figures on this page

Wipe cycle

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

The tag sets the prediction: too few of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's wipes are on record to confirm its schedule. A wipe is scheduled for Friday 30 October at 08:51 UTC, according to this server's cycle. The world now in play was created 12 days 19 hours ago. A wipe every two weeks is stated in its tags.

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

Across recent wipes the busiest point averaged 2 players. The highest player count on the latest wipe arrived 5 hours in.

Server details

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

In Asia, according to its EA tag, sits [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. 162.43.16.74:28015 is its address.

What Rust build 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. Joining requires the same protocol on your game; Steam handles the update.

Is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け up, and how steady is its uptime?

The current status of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is online. The uptime it reports puts the last restart at about 35 hours ago. 99% uptime over the last 7 full days, equal to 167 of 168 hours. 2 October 2026 is when Rust Server Analytics first recorded it.

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

The 48-hour average was 149 server fps; the low was 96. Entity count reached 58,066, covering buildings, deployables and the rest of the world. At its highest, memory use was 2,176 MB. Players experience lag as low fps combined with a rising entity count.

Lists and tags

How should the tags on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け be read?

The game's server browser reads the tags [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け publishes: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): 100 slots in total; ts4 (Group limit): Teams hold no more than 4; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^b (Biweekly): A two-week wipe cycle; ^v (Vanilla): Stock Facepunch settings, with no rate changes, kits or extra rules; EA (East Asia): The server browser files it under East Asia. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け appear across Rust Server Analytics's lists and filters?

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

Player numbers

Against other Rust servers, how does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け compare?

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け holds #2,559 on seven-day player hours and #248 in Asia, inside the top 11% of the ranked field. In the quad peer group, the rank is #158.

How many players does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け carry?

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け holds 0 players of its 100 slots as of the latest update. Averaging 1 players across seven days, the server reached a peak of 6. Averaged over 48 hours, activity is highest at 10:00 UTC with 3 players.

Map and rules

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

Gather rate is not mentioned in the name of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. Up to 4 players can form a group (quad). survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. The Community category in the server browser lists it. Its self-description is vanilla: stock Facepunch settings, with no rate changes, kits or extra rules. VAC, Valve's anti-cheat, is enabled.

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

A procedural map of size 3,500 with seed 1029781210, generated by the game, runs on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. Because size and seed determine the map, it can be viewed on RustMaps via this page.

How to join

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

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 162.43.16.74:28015. Find it online at https://discord.com/invite/n4cemh8hm5.

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 format.
mp100
Max players 100 slots in total.
ts4
Group limit Teams hold no more than 4.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly A two-week wipe cycle.

Difficulty

^v
Vanilla Stock Facepunch settings, with no rate changes, kits or extra rules.

Region

EA
East Asia The server browser files 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.