Working its way up from the back of the class: #13,296 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
30/ 100
F
Lost ground: down 5,409 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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.
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.
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 17 Sep. 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
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h.
The force wipe · high confidence
usual gap13 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 4
Coming wipes
7d 6hThu 5 Nov, 19:00 UTCFW
35d 6hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Fri 2 OctSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 18:16 UTC26d ago
1
–
running
0
Sat 19 Sep, 19:25 UTC39d ago
1
halved by day 4
13 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
In what location does Detroit: Irreparable Damage|NPCs|RaidableBases sit?
You'll find no region listed by Detroit: Irreparable Damage|NPCs|RaidableBases. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 198.73.57.77:28015.
Is Detroit: Irreparable Damage|NPCs|RaidableBases up, and how steady is its uptime?
The server is down: Detroit: Irreparable Damage|NPCs|RaidableBases is offline now, with the last sighting 16 days 15 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
Which Rust version is Detroit: Irreparable Damage|NPCs|RaidableBases running?
The server Detroit: Irreparable Damage|NPCs|RaidableBases is on Rust network protocol 2634 and build 167584 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Detroit: Irreparable Damage|NPCs|RaidableBases wipe its map?
The force wipe each month is the only wipe Detroit: Irreparable Damage|NPCs|RaidableBases takes. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 26 days 18 hours. The tags show a monthly wipe schedule.
What happens on Detroit: Irreparable Damage|NPCs|RaidableBases when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 2 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 4 is when it sank below half in the wipes that did not hold.
Player numbers
Where does Detroit: Irreparable Damage|NPCs|RaidableBases sit among Rust servers?
In the top 61% of all ranked servers, Detroit: Irreparable Damage|NPCs|RaidableBases sits at #13,296 for player hours over the last seven days.
What does the population on Detroit: Irreparable Damage|NPCs|RaidableBases look like?
It has been 16 days 15 hours since Detroit: Irreparable Damage|NPCs|RaidableBases was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Detroit: Irreparable Damage|NPCs|RaidableBases?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167584 (Build): The game build is 167584; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^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 are the tags Detroit: Irreparable Damage|NPCs|RaidableBases 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.
Where does Detroit: Irreparable Damage|NPCs|RaidableBases appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Detroit: Irreparable Damage|NPCs|RaidableBases: Modded Rust servers, graded. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
Which rules does Detroit: Irreparable Damage|NPCs|RaidableBases enforce, and what are its settings?
Nothing in the name of Detroit: Irreparable Damage|NPCs|RaidableBases states a gather rate. With no change from the game default, groups take up to 8 players. You get survival 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. Plugins on it number Oxide. Vanilla is what it calls itself: facepunch's own version, with no changed rates, kits or rules. The server runs Valve's anti-cheat, VAC.
Which map is in play on Detroit: Irreparable Damage|NPCs|RaidableBases?
Detroit: Irreparable Damage|NPCs|RaidableBases runs a game-generated procedural map at size 4,000, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Connecting
How do you get onto Detroit: Irreparable Damage|NPCs|RaidableBases?
To connect, start Rust, press F1, and type client.connect 198.73.57.77:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^m,^v,gmrust,cs167584,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167584
BuildThe game build is 167584.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
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 standing (F); wipes are the one to work on (F).