Working its way up from the back of the class: #15,285 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
49/ 100
D
Slipped a little: down 195 places this week. Nothing a good wipe can't fix.
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.
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 12 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····WW
·······
···
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.
usual gap1.2 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sun 18 OctSat 17 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 18 Oct, 23:57 UTC9d ago
0
–
running
0
Sat 17 Oct, 19:32 UTC11d ago
1
–
1.2 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
You'll find no region listed by test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 45.45.239.214:27115.
Is test up, and how steady is its uptime?
The server is down: test is offline now, with the last sighting 9 days 19 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 12 October 2026, Rust Server Score saw it for the first time.
Which Rust version is test running?
Rust network protocol 2634 and build 167781 on Linux is what test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does test wipe, and how often?
The record holds too few of test'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 9 days 21 hours.
What should you expect from wipe day on test?
Recent wipes have peaked at 0 players on average. Peak numbers came 1 hours into the latest wipe.
Player count
Where does test place in the wider field of Rust servers?
Over the last seven days, test has #15,285 for player hours, in the top 69% of all ranked servers.
How many players does test usually have?
It has been 9 days 19 hours since test was last seen, and it is offline right now.
Tags
How should you read the tags on test?
gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^d (Combat training): You are given the loot; the point is aim and PvP practice; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon are the tags test 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 Rust Server Score filters and lists feature test?
Rust Server Score lists that include test: Modded Rust servers, graded and Rust combat training servers, graded. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Combat training ^d, Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
How is test set up, and what rules does it keep?
The name of test gives no gather rate. With no change from the game default, groups take up to 8 players. You get combat training here, loot is handed out for aim and PvP practice. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. Vanilla is what it calls itself: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
test runs which map?
A procedural map of size 6,000 and seed 1337, generated by the game, is what test runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Connecting
How should you connect to test?
Enter client.connect 45.45.239.214:27115 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://rustlands.net.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^z,^y,^v,^d,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Gameplay
^d
Combat trainingYou are given the loot; the point is aim and PvP practice.
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 momentum (D); standing is the one to work on (F).