Working its way up from the back of the class: #13,772 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
34/ 100
F
Lost ground: down 4,316 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
No hourly history yet.
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 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
10 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·W··WW·
WWW··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 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Mon 5 OctSun 4 OctSat 3 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 6 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 5 Oct, 09:51 UTC22d ago
1
–
running
0
Sun 4 Oct, 08:37 UTC23d ago
1
–
1.1 days
0
Sat 3 Oct, 03:32 UTC24d ago
1
–
1.2 days
0
Wed 30 Sep, 04:29 UTC27d ago
0
–
3 days
0
Tue 29 Sep, 07:15 UTC28d ago
1
–
0.9 days
0
Mon 28 Sep, 06:42 UTC29d ago
1
–
1 days
1
Mon 28 Sep, 00:17 UTC29d ago
1
–
0.3 days
1
Sat 26 Sep, 04:27 UTC31d ago
1
–
1.8 days
1
Fri 25 Sep, 06:57 UTC32d ago
1
–
0.9 days
1
Tue 22 Sep, 03:26 UTC35d ago
1
✓ held half
3.1 days
1
Sun 20 Sep, 03:42 UTC37d ago
1
–
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
No region is published for .. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 45.144.52.87:28015 is the address to use.
Is . up, and how steady is its uptime?
At this moment, . is offline; the last time it was seen was 21 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does . sit?
You will find . on Rust network protocol 2634 and build 166494, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does . wipe, and how often?
. wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 22 days 13 hours.
What happens on . when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 6 hours after it began.
Player numbers
Where does . place in the wider field of Rust servers?
In the top 61% of all ranked servers, . sits at #13,772 for player hours over the last seven days.
What does the population on . look like?
It has been 21 days 16 hours since . was last seen, and it is offline right now.
Tags
How should you read the tags on .?
gmrust (Game mode): Rust survival, played by the standard rules; mp500 (Max players): The server holds 500 slots; ts20 (Group limit): No team may go above 20; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags . 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 Rust Server Score filters and lists feature .?
These Rust Server Score lists count . 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.
Rules and settings
How is . set up, and what rules does it keep?
Nothing in the name of . states a gather rate. You can play in groups of up to 20 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
How to join
How do you get onto .?
To connect, start Rust, press F1, and type client.connect 45.144.52.87:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2634,gmrust,cs166494,ts20,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp500
Max playersThe server holds 500 slots.
ts20
Group limitNo team may go above 20.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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. Even marks across the subjects, from F to F.