Skip to the page
Network live 11,829 servers online 89,289 players aboard 0 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Offline EA 219.97.72.66:28016 checked 1d ago

teams off biweekly wipes vanillaoxide
Tracking number · connect
Wipe progress · wiped 12d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Fri 30 Oct, 08:51 UK Fri 30 Oct, 08:51 UTC in 1d 12h · medium confidence
4/ 100 players now 4% full
27-day averagepeak 12
#2,735ranktop 12% · #274 in EA
12d agolast wipebiweekly schedule
1d 12hnext wipeFri 30 Oct, 08:51 UTC
Delivery history

Players, performance and rank

Players

AveragePeak
0246821:0000:0003:0005:0008:0011:00

Hourly average and peak, UTC.

Server performance

02040608021:0000:0003:0005:0008: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 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule

fixed weekdays
Next delivery expected

Next wipe Friday 30 October, 08:51 UTC · 08:51 UK, in 1d 12h.

Every other Friday at 08:51 UTC · medium confidence
14 daysusual gapbetween real wipes
75%on rhythmof its recent wipes
18wipe-day peakplayers, last three wipes
33%crowd heldelse halves by day 7.5

Coming wipes

  1. 1d 12hFri 30 Oct, 08:51 UTC08:51 UK
  2. 7d 22hThu 5 Nov, 19:00 UTC19:00 UKFW
  3. 15d 12hFri 13 Nov, 08:51 UTC08:51 UK
  4. 29d 12hFri 27 Nov, 08:51 UTC08:51 UK
  5. 35d 22hThu 3 Dec, 19:00 UTC19:00 UKFW
  6. 43d 12hFri 11 Dec, 08:51 UTC08:51 UK

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

every wipe as a delivery, newest first
  1. Fri 30 Oct, 08:51 UTC08:51 UK · in 1d 12h
    Next wipe expected · every other Friday at 08:51 UTC
  2. Fri 16 Oct, 08:51 UTC 09:51 UK · 12d ago
    Wipe delivered
    Peak
    18
    Crowd
    –
    Lasted
    running
    Players before
    0
  3. Fri 2 Oct, 08:51 UTC 09:51 UK · 26d ago
    Wipe delivered
    Peak
    22
    Crowd
    halved by day 5
    Lasted
    14 days
    Players before
    1
  4. Fri 18 Sep, 09:14 UTC 10:14 UK · 40d ago
    Wipe delivered
    Peak
    15
    Crowd
    halved by day 10
    Lasted
    14 days
    Players before
    0
  5. Wed 16 Sep, 08:10 UTC 09:10 UK · 42d ago
    Wipe delivered
    Peak
    7
    Crowd
    held half
    Lasted
    2 days
    Players before
    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 parcels

Similar servers

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

  1. Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 68 on average 39 / 200
  2. Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 42 on average 44 / 215
  3. Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 27 on average 18 / 100
  4. [SEA/KR/JP] Rusty Malaysia | Biweekly | VanillaEA · groups of 8+ · biweekly · 4 on average 1 / 200
  5. JP ONLY 2WEEK SOLO/DUO/TORIO#84EA · groups of 8+ · biweekly · 3 on average 2 / 60
  6. [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 2 on average 2 / 100
Help desk

Quick answers

From the figures on this page.

Player count

What is the ranking of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE against other Rust servers?

On player hours over the last seven days, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE ranks #2,735 overall and #274 in Asia, in the top 12% of all ranked servers.

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

The last sighting of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE was 32 hours ago; it is offline right now. Averaged over the past week: 2 players, peaking at 12. The busiest hour over the last 48 hours was 07:00 UTC, averaging 5 players.

Rules and settings

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

Size 3,750 and seed 1337 define the procedural map [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page. You will see this map name: Custom Map.

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

The name of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE gives no gather rate. No group limit is published. It runs survival, the usual game: build, gather, raid. You can raid and fight other players. You will find it listed under Community in the server browser: it is a community server. The plugins run on Oxide. By its own description it is vanilla: played as Facepunch ships it, with rates, kits and rules unchanged. VAC, Valve's anti-cheat, is switched on.

Server details

What location does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run from?

The EA tag is how [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE lists its location: Asia. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 219.97.72.66:28016 is its address.

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

The 48-hour average for server fps stands at 49, never dipping below 32. The world held as many as 90,400 entities: buildings, deployables and the rest. Memory use peaked at 2,534 MB. Players feel a rising entity count and low fps as lag.

Is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE up, and how good is its uptime?

[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is offline at the moment, with the last sighting 32 hours ago. Its reported uptime suggests a restart roughly 16 hours ago. 93% is the uptime for the last 7 full days, up for 156 of 168 hours. It was first seen by Rust Wipe Tracker on 13 September 2026.

What Rust version is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE using?

Rust network protocol 2635 and build 168909 on Linux is what [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE runs. The same protocol is required to join, and Steam takes care of updating it.

Wipe times

How does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE handle its wipe days?

18 players is the average peak across its recent wipes. 46 hours after the latest wipe, the crowd reached its peak. Until the next wipe, the crowd stayed over half the peak in 33% of recent cases. In the other cases it sank under half by day 7.5.

On what schedule does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE reset its map?

Wipes at [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE come every other Friday at 08:51 UTC. You can expect its next wipe on Friday 30 October at 08:51 UTC. 12 days 11 hours have passed since this world was made. In its tags it posts a wipe every two weeks.

Server tags

Where does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE appear in Rust Wipe Tracker lists and filters?

You will find [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE on the following Rust Wipe Tracker lists: Rust community servers, unmodded and Vanilla Rust servers. You will find it 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 is the meaning of the server tags on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

Read off the game's server browser, the tags for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE are: gmrust (Game mode): Standard Rust survival is the game mode here; mp100 (Max players): It holds 100 slots; ts0 (Group limit): Team feature: disabled; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set; ^b (Biweekly): A wipe comes every fortnight; ^v (Vanilla): Played as Facepunch ships it, with rates, kits and rules unchanged; ^o (Oxide): The plugin framework here is Oxide (uMod); EA (East Asia): The server browser files it under East Asia. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Connecting

What steps do you take to join [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

Enter client.connect 219.97.72.66:28016 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you. You will find its website at https://superlative-sprite-2173de.netlify.app.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game mode here.
mp100
Max players It holds 100 slots.
ts0
Group limit Team feature: disabled.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code A region code isn't set.

Wipe schedule

^b
Biweekly A wipe comes every fortnight.

Difficulty

^v
Vanilla Played as Facepunch ships it, with rates, kits and rules unchanged.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).

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.