Working its way up from the back of the class: #15,316 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
51/ 100
D
Moving up: up 332 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 70% 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. You can connect at 104.28.250.14:28015.
Is KATMANRUST up, and how steady is its uptime?
You cannot join now: KATMANRUST is offline, last seen 11 days 7 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 9 October 2026.
On what Rust version does KATMANRUST sit?
Rust network protocol 2623 and build 147776 on Windows is what KATMANRUST runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does KATMANRUST wipe its map?
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. It has been running its current world for 208 days 22 hours.
Player count
Where does KATMANRUST place in the wider field of Rust servers?
Over the last seven days, KATMANRUST has #15,316 for player hours, in the top 70% of all ranked servers.
How many players does KATMANRUST usually have?
The last sighting of KATMANRUST was 11 days 7 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on KATMANRUST?
gmrust (Game mode): Survival in the standard Rust style; mp31 (Max players): 31 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2623 (Protocol): The game protocol is 2623, so your game must match that version to join; cs147776 (Build): Build number: 147776; ptrak (Networking): The network layer is RakNet, standard for the game; $rger (Region code): ger is the region code this server uses; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags KATMANRUST 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 KATMANRUST?
These Rust Server Score lists count KATMANRUST among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on KATMANRUST?
You will find no gather rate in the name of KATMANRUST. The group limit stays at the game's default of 8 players. You get survival here, 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. 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.
How to join
What is the way to join KATMANRUST?
To connect, start Rust, press F1, and type client.connect 104.28.250.14:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp31,ptrak,$rger,v2623,gmrust,cs147776,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp31
Max players31 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2623
ProtocolThe game protocol is 2623, so your game must match that version to join.
cs147776
BuildBuild number: 147776.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$rger
Region codeger is the region code this server uses.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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).