Working its way up from the back of the class: #15,349 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: down 119 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.
No daily history yet.
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
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
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 20 Oct, 11:46 UTC8d ago
0
–
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
worker leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 151.243.93.160:28125.
How reliable is worker, and is it up?
You cannot join now: worker is offline, last seen 8 days 20 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 20 October 2026.
What Rust version is worker on?
Rust network protocol 2634 and build 167781 on Linux is what worker runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does worker wipe, and how often?
The record holds too few of worker's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 8 days 20 hours.
What happens on worker when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
What position does worker hold in the rankings?
In the top 70% of all ranked servers, worker sits at #15,349 for player hours over the last seven days.
What does the population on worker look like?
worker is offline at the moment; the last time it was seen was 8 days 20 hours ago.
Tags and filters
How should you read the tags on worker?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): Its slot count is 1; 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; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags worker publishes, and the game's server browser reads them. 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 worker?
These Rust Server Score lists count worker among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
Which rules does worker enforce, and what are its settings?
Nothing in the name of worker states a gather rate. The default of 8 players applies as the group cap. You get survival 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. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map worker uses?
worker runs a procedural map, which the game generates.
Connecting
How do you get onto worker?
Enter client.connect 151.243.93.160:28125 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 asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersIts slot count is 1.
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.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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).