Working its way up from the back of the class: #13,894 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
47/ 100
D
Slipped a little: down 736 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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.
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 60% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W··F···
·······
·······
·······
····
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 gap3.5 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Thu 1 OctMon 28 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 20:56 UTCFW27d ago
1
–
running
0
Mon 28 Sep, 09:43 UTC31d ago
0
–
3.5 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. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 193.141.60.251:28017.
How dependable is Test Rust, and is it online at the moment?
You cannot join now: Test Rust is offline, last seen 27 days 20 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 28 September 2026, Rust Server Score saw it for the first time.
What Rust version is Test Rust on?
Rust network protocol 2633 and build 165217 on Linux is what Test Rust runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Test Rust reset?
The record holds too few of Test Rust's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 27 days 21 hours have passed since this world was made.
What happens on Test Rust when wipe day arrives?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 1 hours after it began.
Player count
Where does Test Rust sit among Rust servers?
Over the last seven days, Test Rust has #13,894 for player hours, in the top 60% of all ranked servers.
What does the population on Test Rust look like?
Test Rust is offline at the moment; the last time it was seen was 27 days 20 hours ago.
Tags
How should you read the tags on Test Rust?
The game's browser takes its cue from the tags Test Rust has set: gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): 20 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^p (PvE): This is player against world: players do not fight each other. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Test Rust?
Rust Server Score lists that include Test Rust: Best community servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Test Rust?
Nothing in the name of Test Rust states a gather rate. With no change from the game default, groups take up to 8 players. You get pve here, no PvP between players. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on Test Rust?
A procedural map, generated by the game, is what Test Rust runs.
Getting in
How do you get onto Test Rust?
Enter client.connect 193.141.60.251:28017 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 asmp20,ptrak,$r?,v2633,^p,gmrust,cs165217,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max players20 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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. Even marks across the subjects, from F to D.