Not ranked yet, so there is no place in the school to report.
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,755 places this week. Nothing a good wipe can't fix.
A term to build on.
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
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
TestServer leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 180.144.66.116:28015.
Is TestServer up, and how steady is its uptime?
At this moment, TestServer is offline; the last time it was seen was 39 days 14 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
What Rust version is TestServer on?
You will find TestServer on Rust network protocol 2633 and build 162929, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does TestServer reset?
TestServer has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 56 days 4 hours have passed since this world was made.
Population
What position does TestServer hold in the rankings?
In the top – of all ranked servers, TestServer sits at #13,272 for player hours over the last seven days.
What does the population on TestServer look like?
It has been 39 days 14 hours since TestServer was last seen, and it is offline right now.
Tags
What is meant by the tags on TestServer?
You'll see TestServer tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): Its slot count is 1; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs162929 (Build): Build number: 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does TestServer appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TestServer among them: 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.
Map and rules
What settings and rules apply on TestServer?
Nothing in the name of TestServer states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on TestServer?
A procedural map, generated by the game, is what TestServer runs.
Connecting
How do you get onto TestServer?
To connect, start Rust, press F1, and type client.connect 180.144.66.116:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,gmrust,cs162929,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersIts slot count is 1.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs162929
BuildBuild number: 162929.
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.