On the class lists: D (45), with population over 48 hours and no performance mark.
Players now4/ 1004% full
7-day average2peak 12
Rank#2,338top 11% · #245 in EA
Last wipe11d agobiweekly schedule
Next wipe2d 7hFri 30 Oct, 08:51 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 2 of 100 on average. Plenty of space to grow.
Standingrank on player hours
89/ 100
A−
Holds a respectable place: #2,338 on player hours.
Uptimehours on the list, last 48
71/ 100
B−
Missed a few lessons: on the list 34 of the last 48 hours.
Performanceserver fps, last 48 hours
80/ 100
B+
Mostly smooth: 48 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
30/ 100
F
Lost ground: down 944 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (A−); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 11% of all ranked servers, top 45% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W·W··
·······
····W··
·······
····W··
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 08:51 UTC, in 2d 7h.
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
2d 7hFri 30 Oct, 08:51 UTC
8d 17hThu 5 Nov, 19:00 UTCFW
16d 7hFri 13 Nov, 08:51 UTC
30d 7hFri 27 Nov, 08:51 UTC
36d 17hThu 3 Dec, 19:00 UTCFW
44d 7hFri 11 Dec, 08:51 UTC
The first 48 hours of its last wipes
Fri 16 OctFri 2 OctFri 18 Sep
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
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE based in?
You'll see [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE listed in Asia, tagged EA. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 219.97.72.66:28016.
Is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE up, and how steady is its uptime?
You cannot join now: [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE is offline, last seen 13 hours ago. The uptime it reports puts the last restart at about 16 hours ago. It was up 156 of 168 hours over the last 7 full days, which is 93% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE run?
It never fell below 32 server fps in the last 48 hours, averaging 48. Buildings, deployables and everything else in the world added up to as many as 91,099 entities. Up to 3,398 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE running?
Rust network protocol 2635 and build 168909 on Linux is what [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE wipe its map?
Wipes come every other Friday at 08:51 UTC on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE. It is due to wipe next on Friday 30 October at 08:51 UTC. 11 days 16 hours have passed since this world was made. Its tags say it wipes every two weeks.
What happens on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE when wipe day arrives?
Recent wipes have peaked at 18 players on average. Peak numbers came 46 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 33% of its recent wipes. Day 7.5 is when it sank below half in the wipes that did not hold.
Player count
What position does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE hold in the rankings?
Over the last seven days, [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE has #2,338 for player hours, in the top 11% of all ranked servers and #245 in Asia.
How many players does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE usually have?
The last sighting of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE was 13 hours ago, and it is offline right now. The seven-day average is 2 players, with a peak of 12. Over the last 48 hours, the peak hour was 07:00 UTC, averaging 5 players.
Tags and filters
How should you read the tags on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
You'll see [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts0 (Group limit): You cannot form teams here; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): You will find it under East Asia in the browser in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
Rust Server Score lists that include [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE: Best community servers, graded and Vanilla Rust servers, graded. 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.
Server rules
Which rules does [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE enforce, and what are its settings?
Nothing in the name of [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE states a gather rate. You will find no published group limit. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. Plugins on it number Oxide. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
The game generates the procedural map on [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE at size 3,750 with seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
How to join
How do you get onto [JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE?
To connect, start Rust, press F1, and type client.connect 219.97.72.66:28016. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://superlative-sprite-2173de.netlify.app.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,^v,EA,gmrust,cs168909,ts0,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts0
Group limitYou cannot form teams here.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
Region
EA
East AsiaYou will find it under East Asia in the browser.
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.
A term to build on. Strongest in standing (A−); population is the one to work on (F).