Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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
Next wipe Thursday 5 November, 19:00 UTC, in 6d 15h.
The 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
Which region is RustyLabourers #3 TESTING GROUNDS based in?
You'll find no region listed by RustyLabourers #3 TESTING GROUNDS. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 69.10.49.122:28025.
How reliable is RustyLabourers #3 TESTING GROUNDS, and is it up?
At this moment, RustyLabourers #3 TESTING GROUNDS is offline; the last time it was seen was 45 days 10 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does RustyLabourers #3 TESTING GROUNDS sit?
You will find RustyLabourers #3 TESTING GROUNDS on Rust network protocol 2633 and build 163794, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does RustyLabourers #3 TESTING GROUNDS wipe its map?
The estimate for RustyLabourers #3 TESTING GROUNDS's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 53 days 21 hours. The tags show a monthly wipe schedule.
Population
Where does RustyLabourers #3 TESTING GROUNDS place in the wider field of Rust servers?
Over the last seven days, RustyLabourers #3 TESTING GROUNDS has #15,025 for player hours, in the top – of all ranked servers.
Is RustyLabourers #3 TESTING GROUNDS a busy server?
It has been 45 days 10 hours since RustyLabourers #3 TESTING GROUNDS was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on RustyLabourers #3 TESTING GROUNDS?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): 5 slots are available; ts6 (Group limit): Teams cap out at 6; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon are the tags RustyLabourers #3 TESTING GROUNDS publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does RustyLabourers #3 TESTING GROUNDS appear in the Rust Server Score lists and filters?
Rust Server Score lists that include RustyLabourers #3 TESTING GROUNDS: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
Which rules does RustyLabourers #3 TESTING GROUNDS enforce, and what are its settings?
Nothing in the name of RustyLabourers #3 TESTING GROUNDS states a gather rate. A group here can reach 6 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RustyLabourers #3 TESTING GROUNDS uses?
RustyLabourers #3 TESTING GROUNDS runs a procedural map, which the game generates.
Connecting
How should you connect to RustyLabourers #3 TESTING GROUNDS?
To connect, start Rust, press F1, and type client.connect 69.10.49.122:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,^z,^y,^m,gmrust,cs163794,ts6
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max players5 slots are available.
ts6
Group limitTeams cap out at 6.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: 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.
Not enough figures yet to write a report. Check back after a few days on the list.