Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO O SRV11,643online PAX37,948playing OCC2,905with players WIPED 3H66
VANVanilla traffic
Callsign

TKO2479=

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

Online EA 162.43.16.74:28015 checked 9m ago

quad biweekly wipes vanilla
Clearance · join
Players now 1/ 100 1% full
7-day average2peak 6
Rank#2,479top 11% · #258 in EA
Last wipe11d agobiweekly schedule
Next wipe2d 5hFri 30 Oct, 08:51 UTC
Track history

Players

AveragePeak
0123404:0013:0022:0007:0016:0001:00

Hourly average and peak, UTC.

Server performance

010020030040004:0013:0022:0007:0016:0001: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 Oct12 Oct18 Oct23 Oct28 Oct

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

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Friday 30 October, 08:51 UTC, in 2d 5h.

Its biweekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

  1. 2d 5hFri 30 Oct, 08:51 UTC
  2. 8d 15hThu 5 Nov, 19:00 UTCFW
  3. 16d 5hFri 13 Nov, 08:51 UTC
  4. 30d 5hFri 27 Nov, 08:51 UTC
  5. 36d 15hThu 3 Dec, 19:00 UTCFW
  6. 44d 5hFri 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:51 UTC11d 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.

Nearby traffic

Similar servers

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

  1. 01COM
    Callsign SHM016EA · quad · biweekly · 3 on average [RU] SAHAMUR
    Players 1/100
  2. 02COM
    Callsign SRV017EA · quad · weekly · 21 on average 『小宇宙』10.27号/新开/四人服/萌新服
    Players 3/200
  3. 03COM
    Callsign SRV017EA · quad · weekly · 20 on average 『次空间』10.26号/新开/四人服/萌新服
    Players 0/200
  4. 04COM
    Callsign SRV017EA · quad · weekly · 15 on average 小虎鲸10.25号|14点新档|四人游玩
    Players 0/200
  5. 05COM
    Callsign JPN017EA · quad · weekly · 11 on average [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours
    Players 4/165
  6. 06COM
    Callsign SRV022EA · quad · monthly · 4 on average 【拾破烂】10.16新开丨4人队丨萌新养老原生态
    Players 3/100
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

Community servers, no tags and Vanilla Rust servers, tracked live — the Rust Tracker lists that include [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. It comes up 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.

What do the tags mean that [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is listed under?

Listed for the server browser to read, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): 100 slots on this server; ts4 (Group limit): Team limit: 4; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): A wipe every fortnight; ^v (Vanilla): No changed rates, kits or rules — the game as Facepunch ships it; EA (East Asia): Server browser: listed under East Asia. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

What should you expect on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け when wipe day lands?

At their busiest, recent wipes averaged 2 players. The peak on the latest wipe came 5 hours after it.

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

The prediction for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け follows its tag, as too few wipes are on record to confirm the schedule. Friday 30 October at 08:51 UTC is when the next wipe falls due. 11 days 18 hours since this world was made. A two-weekly wipe schedule is published in its tags.

Server Details

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

Tracking shows [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け online as of now. By its own uptime figure, the last restart was roughly 10 hours ago. 168 of 168 hours up over the last 7 full days: 100% uptime. The first sighting by Rust Tracker was 2 October 2026.

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

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

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

For the last 48 hours it averaged 145 server fps; the floor was 88. Buildings, deployables and the rest of the world took it to a maximum of 58,066 entities. It drew as much as 3,264 MB of memory. Players feel lag when fps drops and the entity count climbs.

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

Listed in Asia under EA: that is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け by its own tags. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 162.43.16.74:28015.

Player Count

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

Tracking [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け: 1 of 100 slots filled. Peak of 6 in the last seven days, average 2 players. At 17:00 UTC it drew its highest average of the last 48 hours: 3 players.

What rank does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け carry among Rust servers?

Top 11% of all ranked servers and #258 in Asia: [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け ranks #2,479 on player hours over the last seven days. Position #142 among quad servers.

Map and Rules

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

Nothing in [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's name states a gather rate. The cap sits at 4 players for a group (quad). survival is the game mode, gather, build and raid: the standard game. Fighting and raiding between players are on. A community server: the server browser lists it under Community. Its label is vanilla: no changed rates, kits or rules — the game as Facepunch ships it. On: VAC, Valve's anti-cheat.

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

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

Connect

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

To connect: start Rust, press F1, enter client.connect 162.43.16.74:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. For the website, go to https://discord.com/invite/hZYNS9UNHS.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp100
Max players 100 slots on this server.
ts4
Group limit Team limit: 4.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Difficulty

^v
Vanilla No changed rates, kits or rules — the game as Facepunch ships it.

Region

EA
East Asia Server browser: listed 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.