[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE
Offline EA 219.97.72.66:28016 checked 10h ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 10% of all ranked servers, top 45% in EA. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Friday 30 October, 08:51 UTC, in 2d 10h. Every other Friday at 08:51 UTC · medium confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 2d 10h | Fri 30 Oct, 08:51 UTC | its own |
| 8d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 16d 10h | Fri 13 Nov, 08:51 UTC | its own |
| 30d 10h | Fri 27 Nov, 08:51 UTC | its own |
| 36d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 44d 10h | Fri 11 Dec, 08:51 UTC | its own |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 18, 46 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 08:51 UTC11d ago | 18 | – | running | 0 |
| Fri 2 Oct, 08:51 UTC25d ago | 22 | halved by day 5 | 14 days | 1 |
| Fri 18 Sep, 09:14 UTC39d ago | 15 | halved by day 10 | 14 days | 0 |
| Wed 16 Sep, 08:10 UTC41d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 81 on average | 18 / 200 |
| Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 49 on average | 16 / 215 |
| Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 32 on average | 12 / 100 |
| [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 5 on average | 0 / 200 |
| JP ONLY 2WEEK SOLO/DUO/TORIO#84 | EA · groups of 8+ · biweekly · 3 on average | 2 / 60 |
| [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 0 / 100 |
Quick answers
from the figures on this pageWipe data
When does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE wipe?
The wipe rhythm of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is every other Friday at 08:51 UTC. Friday 30 October at 08:51 UTC is when its next wipe is due. The world now in play was created 11 days 13 hours ago. Its tags publish a wipe schedule of every two weeks.
Wipe day on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: what should you expect?
Recent wipes averaged a busiest count of 18 players. 46 hours after the latest wipe the crowd peaked. Above half that peak until the next wipe held in 33% of recent wipes. In the other cases the crowd dropped below half by day 7.5.
Server details
Which location hosts [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Its EA tag puts [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE in Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 219.97.72.66:28016 is its address.
What Rust build does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run?
Rust network protocol 2635 and build 168909 on Linux is the setup for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. Your game must match the protocol to join, and Steam applies that update.
Is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE up, and how steady is its uptime?
The current status is offline for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, with the last sighting 10 hours ago. Its reported uptime indicates a restart roughly 16 hours ago. 100% uptime over the last 7 full days, equal to 168 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.
Does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE perform well?
Server fps averaged 49 over the last 48 hours, with a floor of 32. At its highest the entity count was 91,099, including buildings, deployables and all else. At its highest, memory use was 3,398 MB. A climbing entity count and low fps are the lag players perceive.
Tags
How should the tags on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE be read?
gmrust (Game mode): Rust survival, standard ruleset; mp100 (Max players): Capacity of 100 slots; ts0 (Group limit): No teams here; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^b (Biweekly): Every two weeks the server wipes; ^v (Vanilla): Facepunch's game unchanged: no altered rates, kits or rules; ^o (Oxide): The Oxide (uMod) plugin framework is installed; EA (East Asia): The server browser files it under East Asia are the tags [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE publishes, and the game's server browser reads them. 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/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: Community Rust servers, live and Vanilla Rust servers. On the server list, the filters that return it are: 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.
Player numbers
What position does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE hold in the server rankings?
For player hours over the last seven days, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE places #2,318 globally and #245 in Asia, in the top 10% of all ranked servers.
What is the population of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
No response from [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE at the latest check, with a last sighting 10 hours ago. Seven-day figures: an average of 2 players and a peak of 12. The 48-hour peak window is 07:00 UTC, at an average of 5 players.
Settings
What settings and rules does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE use?
Gather rate is not mentioned in the name of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. No group limit is made public. survival is the game mode, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. Community is its listing; it is a community server. Plugins from Oxide are in use. Vanilla is its own description: facepunch's game unchanged: no altered rates, kits or rules. The server runs with VAC, Valve's anti-cheat, enabled.
The map on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: which one is it?
[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE uses a procedural map of size 3,750 with seed 1337, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here. The map is called Custom Map.
How to join
What is the way onto [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
In the Rust console (F1), enter client.connect 219.97.72.66:28016. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://superlative-sprite-2173de.netlify.app is its website.