A quiet classroom so far: 1 of 5 on average. Plenty of space to grow.
Standingrank on player hours
52/ 100
D
Working its way up from the back of the class: #10,611 on player hours.
Uptimehours on the list, last 48
2/ 100
F
Attendance needs work: on the list only 1 of the last 48 hours.
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.
A term to build on.
Strongest in standing (D); uptime 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 48% 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
WD-41 | Imperium TEST leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 67.60.51.136:28115 is the address to use.
How dependable is WD-41 | Imperium TEST, and is it online at the moment?
You cannot join now: WD-41 | Imperium TEST is offline, last seen 46 hours ago. It was up 0% of the time over the last 1 full day, 0 of 24 hours. The first sighting by Rust Server Score was on 26 October 2026.
Which Rust version is WD-41 | Imperium TEST running?
Rust network protocol 2635 and build 168909 on Linux is what WD-41 | Imperium TEST runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does WD-41 | Imperium TEST reset?
The record holds too few of WD-41 | Imperium TEST's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 2 days 2 hours have passed since this world was made.
Population
What position does WD-41 | Imperium TEST hold in the rankings?
In the top 48% of all ranked servers, WD-41 | Imperium TEST sits at #10,611 for player hours over the last seven days.
Is WD-41 | Imperium TEST a busy server?
It has been 46 hours since WD-41 | Imperium TEST was last seen, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days. Over the last 48 hours, the peak hour was 18:00 UTC, averaging 1 players.
Tags
How should you read the tags on WD-41 | Imperium TEST?
The game's browser takes its cue from the tags WD-41 | Imperium TEST has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): The server holds 5 slots; ts128 (Group limit): No team may go above 128; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; 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; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does WD-41 | Imperium TEST appear in the Rust Server Score lists and filters?
Rust Server Score lists that include WD-41 | Imperium TEST: 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 3 days.
Server rules
What settings and rules apply on WD-41 | Imperium TEST?
The name of WD-41 | Imperium TEST gives no gather rate. A group here can reach 128 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map WD-41 | Imperium TEST uses?
The game generates a procedural map for WD-41 | Imperium TEST.
How to join
What is the way to join WD-41 | Imperium TEST?
Enter client.connect 67.60.51.136:28115 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 asmp5,ptrak,$r?,v2635,gmrust,cs168909,ts128,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max playersThe server holds 5 slots.
ts128
Group limitNo team may go above 128.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Strongest in standing (D); uptime is the one to work on (F).