Working its way up from the back of the class: #13,836 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
32/ 100
F
Lost ground: down 4,863 places this week. A strong wipe could turn it round.
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 61% of all ranked servers. Ranked on player hours over the last seven days.
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
Test Server 31 #1 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 80.76.61.129:28015.
Is Test Server 31 #1 up, and how steady is its uptime?
At this moment, Test Server 31 #1 is offline; the last time it was seen was 25 days 11 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 1 October 2026.
On what Rust version does Test Server 31 #1 sit?
Rust network protocol 2634 and build 166494 on Windows is what Test Server 31 #1 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Test Server 31 #1 wipe its map?
Test Server 31 #1 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 26 days 11 hours.
Population
Where does Test Server 31 #1 place in the wider field of Rust servers?
In the top 61% of all ranked servers, Test Server 31 #1 sits at #13,836 for player hours over the last seven days.
How many players does Test Server 31 #1 usually have?
It has been 25 days 11 hours since Test Server 31 #1 was last seen, and it is offline right now.
Lists and filters
What do Test Server 31 #1's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp31 (Max players): Its slot count is 31; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): This runs on build 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server are the tags Test Server 31 #1 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Test Server 31 #1 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Test Server 31 #1: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on Test Server 31 #1?
You will find no gather rate in the name of Test Server 31 #1. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
Test Server 31 #1 runs which map?
Test Server 31 #1 runs a procedural map, which the game generates.
Getting in
How do you get onto Test Server 31 #1?
Enter client.connect 80.76.61.129:28015 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 asmp31,ptrak,$r?,v2634,gmrust,cs166494,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp31
Max playersIts slot count is 31.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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.