On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now1/ 2000% full
7-day average0peak 3
Rank#5,908top 27%
Last wipe27d agomonthly schedule
Next wipe6d 21hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 200 on average. Plenty of space to grow.
Standingrank on player hours
73/ 100
B−
Holds a respectable place: #5,908 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
17/ 100
F
Needs to work on its frame rate: 10 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
57/ 100
C−
Moving up: up 770 places this week.
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 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 27% 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
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
6d 21hThu 5 Nov, 19:00 UTCFW
34d 21hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 06:09 UTC27d 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
No region is published for HURT LOCKER. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 104.143.3.247:28159.
Is HURT LOCKER up, and how steady is its uptime?
You can join now: HURT LOCKER is online. According to its reported uptime, the last restart was about 13 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Does HURT LOCKER perform well?
It never fell below 5 server fps in the last 48 hours, averaging 10. Up to 94,131 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 2,999 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does HURT LOCKER sit?
The server HURT LOCKER is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does HURT LOCKER reset?
The force wipe each month is the only wipe HURT LOCKER 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 27 days 15 hours. Its tags record that it wipes monthly.
What happens on HURT LOCKER when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 3 hours after it began.
Player numbers
Where does HURT LOCKER sit among Rust servers?
Over the last seven days, HURT LOCKER has #5,908 for player hours, in the top 27% of all ranked servers.
What does the population on HURT LOCKER look like?
With 200 slots available, HURT LOCKER currently has 1 players. It peaked at 3 and averaged 0 players over the last seven days. The highest average in the last 48 hours came at 12:00 UTC, with 1 players.
Tags
How should you read the tags on HURT LOCKER?
The game's browser takes its cue from the tags HURT LOCKER has set: gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): 200 slots are available; ts12 (Group limit): A team can hold 12 players at most; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^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. 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 HURT LOCKER appear in the Rust Server Score lists and filters?
Rust Server Score lists that include HURT LOCKER: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What settings and rules apply on HURT LOCKER?
The name of HURT LOCKER gives no gather rate. A group here can reach 12 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map HURT LOCKER uses?
A procedural map of size 4,000 and seed 225798380, generated by the game, is what HURT LOCKER runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to HURT LOCKER?
Enter client.connect 104.143.3.247:28159 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 asmp200,ptrak,$r?,v2635,^m,gmrust,cs168909,ts12,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max players200 slots are available.
ts12
Group limitA team can hold 12 players at most.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
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 uptime (A+); population is the one to work on (F).