StatusLive Servers online11,874 Players88,657 Populated4,001 Wiped · 3 h163 Interval5 min Date27 OCT 2026

DWG RG-S2291Server sheetchecked 8h ago

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

Offline EA 219.97.72.66:28016 checked 8h ago

teams off biweekly wipes vanillaoxide
Connect
Players now 4/ 100 4% full
7-day average2peak 12
Rank#2,291top 10% · #240 in EA
Last wipe11d agobiweekly schedule
Next wipe2d 12hFri 30 Oct, 08:51 UTC
Fig. 1

Players

AveragePeak
0246821:0005:0012:0020:0003:0011:00

Hourly average and peak, UTC.

Fig. 1Players on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE
Fig. 2

Server performance

02040608021:0005:0012:0020:0003: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

fixed weekdays

Next wipe Friday 30 October, 08:51 UTC, in 2d 12h. Every other Friday at 08:51 UTC · medium confidence

usual gap14 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak18players, last three wipes
crowd held33%else halves by day 7.5

Coming wipes

  1. 2d 12hFri 30 Oct, 08:51 UTC
  2. 8d 22hThu 5 Nov, 19:00 UTCFW
  3. 16d 12hFri 13 Nov, 08:51 UTC
  4. 30d 12hFri 27 Nov, 08:51 UTC
  5. 36d 22hThu 3 Dec, 19:00 UTCFW
  6. 44d 12hFri 11 Dec, 08:51 UTC

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctFri 18 Sep
010203040+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 18, 46 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 82 on average
28 / 200
02
Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 50 on average
19 / 215
03
Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 33 on average
16 / 100
04
[SEA/KR/JP] Rusty Malaysia | Biweekly | VanillaEA · groups of 8+ · biweekly · 5 on average
0 / 200
05
JP ONLY 2WEEK SOLO/DUO/TORIO#84EA · groups of 8+ · biweekly · 3 on average
0 / 60
06
[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 2 on average
1 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

What uptime is recorded for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, and is it up?

The current state of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is offline, with the last sighting 8 hours ago. The uptime it reports puts the last restart at about 16 hours ago. 168 of 168 hours up over the last 7 full days, which is 100% of the time. On 13 September 2026 is when Rust Graphs first saw it.

What does the recorded performance of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE show?

Average server fps over the last 48 hours is 50; the lowest was 32. Counted at its highest: 91,099 entities, buildings, deployables and the rest of the world included. 3,398 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

The EA tag is how [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE lists itself in Asia. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 219.97.72.66:28016.

On which Rust version is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE running?

On Linux, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Population

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

[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is not responding at the latest refresh; the last record of it online is 8 hours ago. The seven-day mean is 2 players; the peak over the same period is 12. Averaged over the last 48 hours, the player count is highest at 07:00 UTC: 5 players.

What rank has been recorded for [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

Across seven days, player hours give [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE #2,291 globally and #240 in Asia, a top 10% position among ranked servers.

Wipe times

What happens on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE on the day of a wipe?

At their busiest, its recent wipes drew 18 players on average. 46 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 33% of its recent wipes stayed above half that peak. By day 7.5 the crowd had fallen below half on the wipes where it did not hold.

Which times and days are wipes plotted at on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

The wipe rhythm at [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is every other Friday at 08:51 UTC. On Friday 30 October at 08:51 UTC its next wipe is due. The current world has been in use since 11 days 11 hours ago. The tags state a wipe schedule at two-week intervals.

Rules and settings

Which settings does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run, and what rules?

No gather rate is stated in the name of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. No group limit is published. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. It appears under Community in the server browser. Plugins run: Oxide. Its own label is vanilla, meaning no changed rates, kits or rules: the game as Facepunch ships it. VAC is on: that is Valve's anti-cheat.

Which map has [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE loaded?

Size 3,750 with seed 1337: that is the procedural map [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: Custom Map.

Lists and filters

Where does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE appear among the Rust Graphs lists and filters?

These Rust Graphs lists include [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: Rust community servers, plotted and Vanilla Rust servers. These filters on the server list return it: 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.

On [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): The slot count is 100; ts0 (Group limit): Teams are disabled; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework is Oxide (uMod); EA (East Asia): In the server browser it appears under East Asia are the tags [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Connect

What is the way to connect to [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

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

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp100
Max players The slot count is 100.
ts0
Group limit Teams are disabled.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

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

Region

EA
East Asia In the server browser it appears 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.

KeyTag string decoded