[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE
Offline EA 219.97.72.66:28016 checked 13h ago
Server instruments
last reading Tue 11:00 UTCPlayers now
4% full 7-day avg7-day peakServer fps
48 h low 32 · below 20 is lag, below 10 is badEntities
48 h range 75,310–91,099 · memory 2,288 MBUptime
16 h 4 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 11% 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 8h. Every other Friday at 08:51 UTC · medium confidence
Coming wipes
- WPT 1Fri 30 Oct, 08:51 UTC2d 8h
- WPT 2Thu 5 Nov, 19:00 UTC8d 18hFW
- WPT 3Fri 13 Nov, 08:51 UTC16d 8h
- WPT 4Fri 27 Nov, 08:51 UTC30d 8h
- WPT 5Thu 3 Dec, 19:00 UTC36d 18hFW
- WPT 6Fri 11 Dec, 08:51 UTC44d 8h
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- 9/200
- 11/215
- 9/100
- 1/200
- 1/60
- 1/100
Quick answers
from the figures on this pageWipe timing
What happens on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE when wipe day comes?
An average of 18 players came at the busiest on its recent wipes. 46 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 33% of recent wipes. It fell below half by day 7.5 when it didn't.
What wipe timing does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE follow?
Wipes on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE come every other Friday at 08:51 UTC. Due on Friday 30 October at 08:51 UTC is its next wipe. 11 days 15 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.
Lists and filters
How should you read the tags on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts0 (Group limit): No teams here: the setting is switched off; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): It runs Oxide, also known as uMod; EA (East Asia): Its browser listing: East Asia from [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE appear in Rust Metrics lists and filters?
These Rust Metrics lists carry [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: Rust community servers: live readings and Vanilla Rust servers, live. Reading: server list filters. It comes up under 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.
Occupancy
Where does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE sit in the rankings?
Ranked by seven-day player hours, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE sits at #2,335 and #245 in Asia, inside the top 11%.
What player count does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE carry?
[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is not responding; status offline, last seen 13 hours ago. Seven-day check: 2 players on average. Peak reading: 12. The last 48 hours peaked at 07:00 UTC, averaging 5 players at that hour.
Operator and location
Where does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE sit?
Reading: location. The EA tag puts [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE in Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 219.97.72.66:28016.
What Rust version is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE on?
Reading: [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Over the last 48 hours the average was 48 server fps; the floor was 32. Peak entity count: 91,099. Buildings, deployables and all else included. Memory peak: 3,398 MB. What players call lag comes from low fps and an entity count on the rise.
What is the uptime on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, and is it online?
Check: connection. [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is offline at this moment. Last contact was 13 hours ago. Reading: uptime. About 16 hours ago it restarted, on its own count. Uptime for the last 7 full days: 144 of 168 hours, or 86%. The first sighting on Rust Metrics was 13 September 2026.
Map and rules
What settings and rules apply on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
No gather rate appears in the name: [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. The group limit is not published. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Plugin count: Oxide. The server calls itself vanilla, with this meaning: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. VAC is on. That is Valve's anti-cheat.
What map is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE on?
Size 3,750 and seed 1337: the game generates the procedural map on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name Custom Map.
Join
How do you connect to [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Press F1 in Rust and enter client.connect 219.97.72.66:28016. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://superlative-sprite-2173de.netlify.app.