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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
·······
·······
·······
·······
·······
··
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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
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
Tue 15 Sep, 13:43 UTC42d ago
1
–
running
1
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 TestServer. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 79.244.83.142:28015.
How dependable is TestServer, and is it online at the moment?
The server is down: TestServer is offline now, with the last sighting 42 days 3 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 14 September 2026, Rust Server Score saw it for the first time.
What Rust version is TestServer on?
Rust network protocol 2633 and build 163493 on Windows is what TestServer runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does TestServer wipe, and how often?
TestServer has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 42 days 6 hours.
What should you expect from wipe day on TestServer?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Player numbers
Where does TestServer sit among Rust servers?
In the top – of all ranked servers, TestServer sits at #13,258 for player hours over the last seven days.
What does the population on TestServer look like?
It has been 42 days 3 hours since TestServer was last seen, and it is offline right now.
Tags
What do TestServer's tags stand for?
The game's browser takes its cue from the tags TestServer has set: gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): Its slot count is 1; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163493 (Build): Build number: 163493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server. 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 TestServer?
These Rust Server Score lists count TestServer 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.
Server rules
What settings and rules apply on TestServer?
Nothing in the name of TestServer states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map TestServer uses?
A procedural map, generated by the game, is what TestServer runs.
How to join
How should you connect to TestServer?
To connect, start Rust, press F1, and type client.connect 79.244.83.142: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,cs163493,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersIts slot count is 1.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163493
BuildBuild number: 163493.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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.
Not enough figures yet to write a report. Check back after a few days on the list.