On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak 1
Rank#12,236top 55%
Last wipe12d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
45/ 100
D
Working its way up from the back of the class: #12,236 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
49/ 100
D
Needs to work on its frame rate: 29 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
37/ 100
F
Slipped a little: down 3,299 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (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
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 16 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 55% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 04:45 UTC12d ago
1
–
running
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
A Rust Server leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 104.129.132.91:28017.
How reliable is A Rust Server, and is it up?
Right now, A Rust Server is online. According to its reported uptime, the last restart was about 4 days 8 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 16 October 2026, Rust Server Score saw it for the first time.
Does A Rust Server perform well?
The average over the last 48 hours was 29 server fps, and it never went below 9. Up to 49,319 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 2,610 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is A Rust Server on?
Rust network protocol 2635 and build 168909 on Linux is what A Rust Server runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does A Rust Server wipe its map?
The record holds too few of A Rust Server's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 12 days 11 hours have passed since this world was made.
What happens on A Rust Server when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 1 hours into the latest wipe.
Player count
Where does A Rust Server sit among Rust servers?
Over the last seven days, A Rust Server has #12,236 for player hours, in the top 55% of all ranked servers.
Is A Rust Server a busy server?
A Rust Server is showing 0 players right now, with 40 slots in total. Averaging 0 players over seven days, it peaked at 1.
Lists and filters
What is meant by the tags on A Rust Server?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags A Rust Server publishes, and the game's server browser reads them. 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 A Rust Server?
These Rust Server Score lists count A Rust Server among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
How is A Rust Server set up, and what rules does it keep?
Nothing in the name of A Rust Server states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
A Rust Server runs which map?
The game generates the procedural map on A Rust Server at size 3,000 with seed 48293. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to A Rust Server?
To connect, start Rust, press F1, and type client.connect 104.129.132.91:28017. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 (A+); population is the one to work on (F).