Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO G SRV11,657online PAX32,896playing OCC2,828with players WIPED 3H79
VANVanilla traffic
Callsign

TTO2828

[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE

Offline EA 219.97.72.66:28016 checked 1d ago

teams off biweekly wipes vanillaoxide
Clearance · join
Players now 4/ 100 4% full
7-day average2peak 12
Rank#2,828top 13% · #269 in EA
Last wipe12d agobiweekly schedule
Next wipe1d 4hFri 30 Oct, 08:51 UTC
Track history

Players

AveragePeak
0246805:0006:0007:0009:0010:0011:00

Hourly average and peak, UTC.

Server performance

02040608005:0006:0007:0009:0010:0011: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 13% of all ranked servers, top 48% in EA. Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

Next wipe Friday 30 October, 08:51 UTC, in 1d 4h.

Every other Friday at 08:51 UTC · medium confidence

usual gap14 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak18players, last three wipes
crowd held33%else halves by day 7.5

Coming wipes

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

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctFri 18 Sep
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 18, 46 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:51 UTC12d ago 18 – running 0
Fri 2 Oct, 08:51 UTC26d ago 22 halved by day 5 14 days 1
Fri 18 Sep, 09:14 UTC40d ago 15 halved by day 10 14 days 0
Wed 16 Sep, 08:10 UTC42d ago 7 held half 2 days 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 RST015EA · groups of 16+ · biweekly · 65 on average Rustoria.co - SEA Medium
    Players 12/200
  2. 02COM
    Callsign JPN778EA · groups of 8+ · biweekly · 41 on average Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com
    Players 5/215
  3. 03COM
    Callsign RST018EA · groups of 16+ · biweekly · 27 on average Rustafied.com - SEA Medium
    Players 6/100
  4. 04COM
    Callsign SEA017EA · groups of 8+ · biweekly · 4 on average [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla
    Players 2/200
  5. 05COM
    Callsign ONL015EA · groups of 8+ · biweekly · 3 on average JP ONLY 2WEEK SOLO/DUO/TORIO#84
    Players 2/60
  6. 06COM
    Callsign SEA428EA · groups of 8+ · biweekly · 2 on average [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly
    Players 1/100
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which Rust Tracker filters and lists carry [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

On Rust Tracker, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE sits in these lists: Community servers, no tags and Vanilla Rust servers, tracked live. It comes up under these filters on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

What do the tags mean that [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is listed under?

Listed for the server browser to read, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): 100 slots on this server; ts0 (Group limit): Team play is off; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): The region code is unset; ^b (Biweekly): Two-week wipe cycle; ^v (Vanilla): As Facepunch ships it: rates, kits and rules are unchanged; ^o (Oxide): A plugin framework runs here: Oxide (uMod); EA (East Asia): Server browser: listed under East Asia. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Times

What happens on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE on wipe day?

Recent wipes averaged a peak of 18 players. 46 hours after the latest wipe, the crowd peaked. Half the peak was held until the next wipe in 33% of its recent wipes. By day 7.5 the crowd dropped below half where it did not hold.

Which wipe times are confirmed for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

At [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE the wipes follow a every other Friday at 08:51 UTC rhythm. Friday 30 October at 08:51 UTC is when the next wipe falls due. This world has been running 12 days 19 hours. A two-weekly wipe schedule is published in its tags.

Location and Status

What is the uptime on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, and is it online?

Offline now, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE was last seen 40 hours ago. The uptime it reports puts the last restart about 16 hours ago. Uptime stood at 79% for the last 7 full days, 132 of 168 hours online. First contact for Rust Tracker: 13 September 2026.

Which Rust build is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE running?

Confirmed for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: Rust network protocol 2635 and build 168909, Linux. To join, your game must be on the same protocol; Steam handles the update.

Is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE holding performance?

For the last 48 hours it averaged 41 server fps; the floor was 32. Peak entity count: 89,742, covering buildings, deployables and all else in the world. Memory peaked at 2,534 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Which location is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE in?

In Asia, under its EA tag, is where [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE lists itself. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 219.97.72.66:28016.

Player Count

How many players are on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE right now?

Offline: [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, last seen 40 hours ago. Seven-day average 2 players; peak 12. Peak traffic in the last 48 hours came at 07:00 UTC, averaging 5 players.

How does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE compare in the rankings?

Seven-day player hours: #2,828 overall for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, top 13% of ranked servers, #269 in Asia.

Map and Rules

Which settings and rules are confirmed on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

The name of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE carries no gather rate. No group limit is published. survival is the game mode, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Community, as a community server. Oxide plugins run on it. Its label is vanilla: as Facepunch ships it: rates, kits and rules are unchanged. VAC is on, Valve's anti-cheat.

What map is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE on?

A procedural map of size 3,750 runs on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, generated by the game from seed 1337. Size and seed match, so the map is the same: view it on RustMaps from this page. Its map goes by the name Custom Map.

Connect

Which steps join [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

To connect: start Rust, press F1, enter client.connect 219.97.72.66:28016 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://superlative-sprite-2173de.netlify.app.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp100
Max players 100 slots on this server.
ts0
Group limit Team play is off.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code The region code is unset.

Wipe schedule

^b
Biweekly Two-week wipe cycle.

Difficulty

^v
Vanilla As Facepunch ships it: rates, kits and rules are unchanged.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).

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.