Offline EA 219.97.72.66:28016 checked 16h ago
[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE
Connect
srv = rust.server("219.97.72.66:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 11% of all ranked servers, top 44% in EA. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()
Next wipe Friday 30 October, 08:51 UTC, in 2d 5h. # Every other Friday at 08:51 UTC · medium confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 2d 5h | Fri 30 Oct, 08:51 UTC | wipe |
| 1 | 8d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 16d 5h | Fri 13 Nov, 08:51 UTC | wipe |
| 3 | 30d 5h | Fri 27 Nov, 08:51 UTC | wipe |
| 4 | 36d 15h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 44d 5h | Fri 11 Dec, 08:51 UTC | wipe |
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 08:51 UTC11d ago | 18 | NaN | running | 0 |
| 1 | Fri 2 Oct, 08:51 UTC25d ago | 22 | halved by day 5 | 14 days | 1 |
| 2 | Fri 18 Sep, 09:14 UTC39d ago | 15 | halved by day 10 | 14 days | 0 |
| 3 | 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.
display(srv.map, srv.info())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 79 on average | 15/200 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 49 on average | 11/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 32 on average | 5/100 |
| 3 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 5 on average | 1/200 |
| 4 | JP ONLY 2WEEK SOLO/DUO/TORIO#84 | EA · groups of 8+ · biweekly · 3 on average | 0/60 |
| 5 | [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 1/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE rank?
Ranked #2,344 on seven-day player hours, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is #243 in Asia and in the top 11% of all ranked servers.
How many players does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE hold at once?
The current row shows [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE offline; the last response was 16 hours ago. Over the last seven days it averaged 2 players and peaked at 12. Averaged by hour over 48 hours, 07:00 UTC is the busiest, at 5 players.
Server data
How smoothly does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run?
Server fps over the last 48 hours averages 48; the floor is 32. The entity count peaked at 91,099, covering buildings, deployables and the rest of the world. A high of 3,398 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Version Rust network protocol 2635 and build 168909 on Linux is reported by [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. Joining needs the same protocol on your game; Steam handles the update.
Is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE up, and what does its uptime show?
The latest sample has [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE offline, with a last sighting 16 hours ago. A restart about 16 hours ago is what its reported uptime implies. 156 of 168 hours up over the last 7 full days, or 93%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE hosted?
In Asia, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE lists itself, using the EA tag. Rust Data does not look up where the machine stands; it shows where a server says it is. 219.97.72.66:28016 is its address.
Map and rules
Which settings and rules does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run?
No gather rate appears in the name: [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. Group limits do not appear in its data. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. The plugin count is Oxide. Vanilla, by its own description: untouched settings: rates, kits and rules as shipped. VAC, Valve's anti-cheat, is enabled.
Which map has [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE selected?
[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE runs a procedural map of size 3,750 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.
Wipes and dates
When does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE wipe, and on what schedule?
Wipes on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run every other Friday at 08:51 UTC. On Friday 30 October at 08:51 UTC the next wipe is due. The world it runs now was generated 11 days 18 hours ago. Its tags carry a wipe schedule of every two weeks.
What is wipe day on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE like?
The average peak over recent wipes is 18 players. 46 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 33% of recent wipes. Otherwise the crowd fell below half by day 7.5.
Tags, lists
Which lists on Rust Data hold [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, and which filters?
The Rust Data lists that [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE fits are: Rust community servers, unfiltered and Vanilla Rust servers. Under these filters on the server list, it is listed: 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.
How should you read the server tags on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Read by the game's server browser, the tags [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts0 (Group limit): The team system is off; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): The cycle is fourteen days; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): The plugin framework in use is Oxide (uMod); EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
In Rust, F1 opens the console: type client.connect 219.97.72.66:28016. Launch Rust on this page does the same by opening the game through Steam and connecting. https://superlative-sprite-2173de.netlify.app is the website recorded for it.
