Station EA-2735 · no signal
[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE
Offline EA 219.97.72.66:28016 checked 1d ago
- Players now
- 4/ 100
- 4% full
- Motion · 24 h
- M0.6▲rising
- +4 players on the day
- 7-day average
- 2
- peak 12
- Rank
- #2,735
- top 12% · #274 in EA
- Last wipe
- 12d ago
- biweekly schedule
- Next wipe
- 1d 12h
- Fri 30 Oct, 08:51 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 4of 100 slots
- Motion · 24 h
- M0.6▲rising+4 players
- Sharpest hour
- +3into Tue 05:00 UTC
- Peak · 48 h
- 5most players in any hour
Players
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 12% of all ranked servers, top 49% in EA. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Friday 30 October, 08:51 UTC, in 1d 12h. Every other Friday at 08:51 UTC · medium confidence
- usual gap
- 14 daysbetween real wipes
- on rhythm
- 75%of its recent wipes
- wipe-day peak
- 18players, last three wipes
- crowd held
- 33%else halves by day 7.5
Coming wipes
- 1d 12hFri 30 Oct, 08:51 UTC
- 7d 22hThu 5 Nov, 19:00 UTCFW
- 15d 12hFri 13 Nov, 08:51 UTC
- 29d 12hFri 27 Nov, 08:51 UTC
- 35d 22hThu 3 Dec, 19:00 UTCFW
- 43d 12hFri 11 Dec, 08:51 UTC
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 08:51 UTC12d ago | M1.3▲rising | 18 | – | running | 0 | |
| Fri 2 Oct, 08:51 UTC26d ago | M1.3▲rising | 22 | halved by day 5 | 14 days | 1 | |
| Fri 18 Sep, 09:14 UTC40d ago | M1.2▲rising | 15 | halved by day 10 | 14 days | 0 | |
| Wed 16 Sep, 08:10 UTC42d ago | M0.8▲rising | 7 | held half | 2 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Generated by the game, the map on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is procedural, size 3,750 with seed 1337. You can view it on RustMaps from this page: the same size and seed produce the same map. The name of its map is Custom Map.
Which settings and rules apply on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
You will find no gather rate in the name of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. No group limit is published. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Community, as a community server. Oxide is the plugin framework it runs. It describes itself as vanilla, which means no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE right now?
A reading taken now finds [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE offline; the most recent activity was 32 hours ago. Across seven days this server recorded an average of 2 players and a peak of 12. The last 48 hours show their highest activity at 07:00 UTC, averaging 5 players.
How does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE rank against other Rust servers?
[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is #274 in Asia and #2,735 worldwide on the past week's player hours, within the top 12% of ranked servers.
Server details
How reliably does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE stay online?
As recorded now, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is not reachable, the last contact having been 32 hours ago. Going by the uptime figure it reports, it restarted about 16 hours ago. It was up 93% of the time across the last 7 full days: 156 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE hold a steady tick rate?
The 48-hour average is 49 server fps; 32 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 90,400. Memory use peaked at 2,534 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE hosted?
The EA tag is how [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE lists itself in Asia. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 219.97.72.66:28016.
What build of Rust does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE use?
On Linux, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
18 players, on average, was the busiest crowd at its recent wipes. 46 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. By day 7.5 it fell below half in the wipes where it didn't hold.
On what timetable does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run its wipes?
every other Friday at 08:51 UTC is how [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE wipes. The date of its next wipe is Friday 30 October at 08:51 UTC. The present world dates from 12 days 11 hours. In its tags it sets out a wipe schedule of every two weeks.
Lists and tags
What do the server tags on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE mean?
The game's server browser reads the tags [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE publishes: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts0 (Group limit): Teams are disabled; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^b (Biweekly): A wipe comes every second week; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; EA (East Asia): In the server browser it appears under East Asia. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE appear?
The Rust Server Trends lists that take in [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. These filters bring it up 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.
How to join
What steps get you onto [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
To join, enter client.connect 219.97.72.66:28016 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://superlative-sprite-2173de.netlify.app.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.