A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
68/ 100
C+
Working its way up from the back of the class: #7,189 on player hours.
Uptimehours on the list, last 48
69/ 100
C+
Missed a few lessons: on the list 33 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
41/ 100
F
Slipped a little: down 1,365 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (C+); 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
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 32% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
WWWWW··
·WW····
···WW··
·······
·····W·
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2
The first 48 hours of its last wipes
Sat 24 OctFri 9 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 01:11 UTC4d ago
1
–
running
0
Fri 9 Oct, 14:00 UTC19d ago
1
halved by day 6
14.5 days
0
Thu 8 Oct, 22:39 UTC19d ago
1
–
0.6 days
0
Wed 30 Sep, 14:27 UTC28d ago
1
halved by day 2
8.3 days
0
Tue 29 Sep, 18:26 UTC29d ago
1
–
0.8 days
0
Fri 25 Sep, 16:56 UTC33d ago
1
halved by day 1
4.1 days
0
Thu 24 Sep, 15:08 UTC34d ago
1
–
1.1 days
1
Wed 23 Sep, 23:01 UTC34d ago
1
–
0.7 days
1
Tue 22 Sep, 19:37 UTC35d ago
1
–
1.1 days
1
Mon 21 Sep, 17:03 UTC37d ago
1
–
1.1 days
0
Sat 19 Sep, 04:17 UTC39d ago
1
✓ held half
2.5 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
You'll find no region listed by a. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 84.192.29.199:28014 is the address to use.
Is a up, and how steady is its uptime?
You can join now: a is online. It was up 76% of the time over the last 7 full days, 128 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is a running?
The server a is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does a wipe, and how often?
No next wipe can be predicted for a, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 4 days 18 hours.
What should you expect from wipe day on a?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 2.
Player count
What position does a hold in the rankings?
In the top 32% of all ranked servers, a sits at #7,189 for player hours over the last seven days.
Is a a busy server?
a is showing 0 players right now, with 100 slots in total. The seven-day average is 0 players, with a peak of 1. The highest average in the last 48 hours came at 23:00 UTC, with 1 players.
Tags and filters
How should you read the tags on a?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts100 (Group limit): No team may go above 100; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags a publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show a?
These Rust Server Score lists count a among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
Which rules does a enforce, and what are its settings?
You will find no gather rate in the name of a. A group here can reach 100 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Connecting
What is the way to join a?
To connect, start Rust, press F1, and type client.connect 84.192.29.199:28014. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts100,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts100
Group limitNo team may go above 100.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 uptime (C+); population is the one to work on (F).