Working its way up from the back of the class: #12,868 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
43/ 100
F
Slipped a little: down 1,715 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··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 peak1players, last three wipes
The first 48 hours of its last wipes
Thu 15 OctWed 14 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 14:29 UTC13d ago
1
–
running
0
Wed 14 Oct, 10:49 UTC15d 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
No region is published for Test. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 37.203.15.108:28015.
How dependable is Test, and is it online at the moment?
You cannot join now: Test is offline, last seen 13 days 19 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Test running?
You will find Test on Rust network protocol 2634 and build 166652, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Test wipe its map?
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. It has been running its current world for 13 days 20 hours.
What happens on Test when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does Test place in the wider field of Rust servers?
In the top 60% of all ranked servers, Test sits at #12,868 for player hours over the last seven days.
Is Test a busy server?
The last sighting of Test was 13 days 19 hours ago, and it is offline right now.
Tags
How should you read the tags on Test?
The game's browser takes its cue from the tags Test has set: gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): Its slot count is 2; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Test?
These Rust Server Score lists count Test among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which rules does Test enforce, and what are its settings?
You will find no gather rate in the name of Test. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. You are not covered by VAC, Valve's anti-cheat.
How to join
How should you connect to Test?
To connect, start Rust, press F1, and type client.connect 37.203.15.108:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max playersIts slot count is 2.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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 F.