Skip to the page
RUST ANALYTICS
LIVE37,697PLY11,506SRV
QUOTE 219.97.72.66:28016 Online EA checked 9m ago

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

teams off biweekly wipes vanillaoxide
Players · last
0/ 100
−3−100.0%24h
0% full
Day range 0 4
7-day avg 3 peak 11
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
0/ 100
0% full
Change · 24h
−3
−100.0% from 3
7-day average
3
peak 11
Rank
#1,921
top 9% · #203 in EA
Rank · 7d ago
#1,433
488 places down
Last wipe
11d ago
biweekly schedule
Next wipe
2d 5h
Fri 16 Oct, 08:51 UTC
Group limit
teams off
players per team
Gather rate
–
no rate in the name
Score
499
player hours, last seven days
Map
3500
Custom Map · seed 1337
First seen
13 Sep 2026
no hostname published

Players

AveragePeak
0246804:0013:0022:0008:0017:0002:00

Hourly average and peak, UTC. Busiest hour of the two days: 6 players.

Server performance

025507510004:0013:0022:0008:0017:0002: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.

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

from its schedule tag
Next wipeFriday 16 October, 08:51 UTCin 2d 5h

Its biweekly schedule tag · low confidence

usual gap
8 days
between real wipes
on rhythm
0%
of its recent wipes
wipe-day peak
15
players, last three wipes
crowd held
50%
else halves by day 10

Coming wipes

  1. 2d 5hFri 16 Oct, 08:51 UTC
  2. 16d 5hFri 30 Oct, 08:51 UTC
  3. 22d 15hThu 5 Nov, 19:00 UTCFW
  4. 30d 5hFri 13 Nov, 08:51 UTC
  5. 44d 5hFri 27 Nov, 08:51 UTC

The first 48 hours of its last wipes

Fri 2 OctFri 18 SepWed 16 Sep
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 22, 2 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 08:51 UTC11d ago 22 – running 1
Fri 18 Sep, 09:14 UTC25d ago 15 halved by day 10 14 days 0
Wed 16 Sep, 08:10 UTC27d 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 53 on average23/200+3+15.5%
2Japan Tokyo - Mondays|10/05|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 38 on average4/215−4−50.0%
3Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 27 on average5/100+0−9.1%
4JP ONLY 2WEEK SOLO/DUO/TORIO#83EA · groups of 8+ · biweekly · 10 on average0/60−2−100.0%
5[SEA/KR/JP] Rusty Malaysia | Biweekly | VanillaEA · groups of 8+ · biweekly · 9 on average5/200+1+17.6%
6[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 3 on average1/100+0−14.3%

Quick answers

from the figures on this page

Server Rules

How is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE configured in terms of rules and settings?

The name of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE carries no gather rate. A group limit is not published. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. Community is its listing in the server browser. Plugin count: Oxide. It uses the term vanilla for itself: no altered rates, kits or rules: the game as Facepunch ships it. The server has VAC, Valve's anti-cheat, switched on.

What is the current map on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE uses a procedural map of size 3,500 with seed 1337, generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page. The map in use is Custom Map.

Population

What is the rank of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

On seven-day player hours, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE sits at #1,921, in the top 9% across ranked servers and #203 in Asia.

What is the population on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

0 of 100 slots on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE are filled right now. Average players over seven days: 3; peak: 11. At 11:00 UTC in the last 48 hours, it averaged 5 players, the busiest hour.

Wipe Schedule

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

An average of 15 players marked the busiest point of its recent wipes. 2 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. The crowd fell below half by day 10 when it did not hold.

How often does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE wipe?

The schedule at [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE cannot be confirmed from the few wipes on record, so the prediction follows its tag. The date of its next wipe is Friday 16 October at 08:51 UTC. This world has been running for 11 days 18 hours. A fortnightly wipe is published in its tags.

Server Details

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

The EA tag and Asia are what [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE lists for itself. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 219.97.72.66:28016.

How is the performance on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

The last 48 hours average 55 server fps, the low being 31. 76,651 entities is the maximum carried: buildings, deployables and everything else. Memory use peaked at 3,160 MB. Low fps and growing entities are the source of felt lag.

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

The build is Rust network protocol 2634 and build 166494 on Linux, running on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. The protocol has to match for you to join, and Steam applies that update.

How reliable is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE and is it currently online?

The server is live: [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is online. The reported uptime puts its last restart at about 7 hours ago. 100% is its uptime for the last 7 full days, 168 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.

Server Tags

How should you interpret the tags on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

Published by [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Capacity: 100 slots; ts0 (Group limit): Team play is disabled; v2634 (Protocol): To join, your game needs protocol 2634; cs166494 (Build): It runs build 166494; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^b (Biweekly): A fortnight between wipes; ^v (Vanilla): No altered rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework Oxide (uMod) is in use; EA (East Asia): East Asia is its browser listing. The tags also carry its current players, queue and world creation time; this page shows them at the top.

[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE appears in which of the lists and filters on Rust Analytics?

These Rust Analytics lists include [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: Rust community servers and Vanilla Rust servers. 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

How can I connect to [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?

The console route: start Rust, press F1, enter client.connect 219.97.72.66:28016. The page's Launch Rust button opens Rust through Steam and connects you instead. You can visit its website at https://superlative-sprite-2173de.netlify.app.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,^b,^v,EA,gmrust,cs166494,ts0,^o

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players Capacity: 100 slots.
ts0
Group limit Team play is disabled.
v2634
Protocol To join, your game needs protocol 2634.
cs166494
Build It runs build 166494.
ptrak
Networking The standard network layer, RakNet.
$r?
Region code The region code is absent.

Wipe schedule

^b
Biweekly A fortnight between wipes.

Difficulty

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

Mods and access

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

Region

EA
East Asia East Asia is its browser listing.

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.