On the class lists: D (52), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average1peak 1
Rank#12,070top 54%
Last wipe4d agono schedule published
Next wipe2d 9hFri 30 Oct, 12:10 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
9/ 100
F
A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
46/ 100
D
Working its way up from the back of the class: #12,070 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
57/ 100
C−
Moving up: up 1,751 places this week.
A term to build on.
Strongest in momentum (C−); population 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.
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 54% 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··
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 12:10 UTC, in 2d 9h.
Every Friday at 12:10 UTC · low confidence
usual gap7 daysbetween real wipes
wipe-day peak1players, last three wipes
Coming wipes
2d 9hFri 30 Oct, 12:10 UTC
8d 15hThu 5 Nov, 19:00 UTCFW
9d 9hFri 6 Nov, 12:10 UTC
16d 9hFri 13 Nov, 12:10 UTC
23d 9hFri 20 Nov, 12:10 UTC
30d 9hFri 27 Nov, 12:10 UTC
36d 15hThu 3 Dec, 19:00 UTCFW
37d 9hFri 4 Dec, 12:10 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 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
Fri 23 Oct, 12:10 UTC4d ago
1
–
running
0
Fri 16 Oct, 13:13 UTC11d ago
1
–
7 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
TestServer leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 95.83.11.41:28015 is the address to use.
Is TestServer up, and how steady is its uptime?
The server is down: TestServer is offline now, with the last sighting 4 days 13 hours ago. It was up 2 of 168 hours over the last 7 full days, which is 1% of the time. It was first seen by Rust Server Score on 9 October 2026.
What Rust version is TestServer on?
You will find TestServer on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does TestServer wipe its map?
Wipes come every Friday at 12:10 UTC on TestServer. Expect the next wipe on Friday 30 October at 12:10 UTC. The world it runs now was created 4 days 14 hours.
What should you expect from wipe day on TestServer?
Recent wipes have peaked at 1 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does TestServer place in the wider field of Rust servers?
In the top 54% of all ranked servers, TestServer sits at #12,070 for player hours over the last seven days.
How many players does TestServer usually have?
It has been 4 days 13 hours since TestServer was last seen, and it is offline right now. The seven-day average is 1 players, with a peak of 1.
Lists and filters
How should you read the tags on TestServer?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set are the tags TestServer publishes, and the game's server browser reads them. 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.
Where does TestServer appear in the Rust Server Score lists and filters?
Rust Server Score lists that include TestServer: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
How is TestServer set up, and what rules does it keep?
Nothing in the name of TestServer states a gather rate. 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. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Connecting
How should you connect to TestServer?
To connect, start Rust, press F1, and type client.connect 95.83.11.41:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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 (C−); population is the one to work on (F).