Working its way up from the back of the class: #15,837 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
50/ 100
D
Holding steady: up 121 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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 won't see a region from KATMANRUST, whose region code is ger. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 77.90.5.53:28015.
How reliable is KATMANRUST, and is it up?
At this moment, KATMANRUST is offline; the last time it was seen was 18 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 8 October 2026.
What Rust version is KATMANRUST on?
The server KATMANRUST is on Rust network protocol 2623 and build 147776 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does KATMANRUST wipe, and how often?
The record holds too few of KATMANRUST's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 207 days 1 hours.
Player numbers
Where does KATMANRUST place in the wider field of Rust servers?
Over the last seven days, KATMANRUST has #15,837 for player hours, in the top 72% of all ranked servers.
Is KATMANRUST a busy server?
It has been 18 days 16 hours since KATMANRUST was last seen, and it is offline right now.
Lists and filters
How should you read the tags on KATMANRUST?
You'll see KATMANRUST tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp31 (Max players): The server holds 31 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2623 (Protocol): Join only if your game runs protocol 2623; cs147776 (Build): This runs on build 147776; ptrak (Networking): The network layer is RakNet, standard for the game; $rger (Region code): It is filed under the region code ger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. 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 KATMANRUST?
These Rust Server Score lists count KATMANRUST 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 KATMANRUST set up, and what rules does it keep?
Nothing in the name of KATMANRUST states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map KATMANRUST uses?
A procedural map, generated by the game, is what KATMANRUST runs.
Connecting
How do you get onto KATMANRUST?
Enter client.connect 77.90.5.53:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp31,ptrak,$rger,v2623,gmrust,cs147776,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp31
Max playersThe server holds 31 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2623
ProtocolJoin only if your game runs protocol 2623.
cs147776
BuildThis runs on build 147776.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$rger
Region codeIt is filed under the region code ger.
Mods and access
^o
OxideThe plugin framework in use is 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 momentum (D); standing is the one to work on (F).