RUST METRICSFlight deck · live data
Data live Servers11,675 Players48,284 Populated3,207 Fresh wipes 3 h123 Scan5 min
‹ All servers80.76.61.125:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server 31 #1

Offline 80.76.61.125:28015 checked 33d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 8 16 23 31 PAX 1 /31

Players now

3% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,680top 61%
Last wipe52d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k24 Sep25 Sep27 Sep28 Sep30 Sep1 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does Test Server 31 #1 follow?

To tell the rhythm of Test Server 31 #1, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 52 days 6 hours ago.

Tags

How should you read the tags on Test Server 31 #1?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp31 (Max players): Slots: 31; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Test Server 31 #1. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Test Server 31 #1 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Test Server 31 #1: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Test Server 31 #1 hold among Rust servers?

Ranking for Test Server 31 #1: #13,680 on seven-day player hours, top 61% of all ranked servers.

How full does Test Server 31 #1 get?

Test Server 31 #1 is not responding; status offline, last seen 33 days ago.

Server details

Where does Test Server 31 #1 sit?

Reading: location. Test Server 31 #1 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 80.76.61.125:28015.

What Rust version is Test Server 31 #1 on?

Rust network protocol 2633 and build 163794 on Windows is the build Test Server 31 #1 runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Test Server 31 #1, and is it online now?

Reading: offline. Test Server 31 #1 last answered 33 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 24 September 2026.

Settings and map

How is Test Server 31 #1 configured, and what rules are in force?

Reading the name gives no gather rate for Test Server 31 #1. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Test Server 31 #1?

The game generates a procedural map for Test Server 31 #1.

Join

What do you do to join Test Server 31 #1?

Check: join. Open Rust, press F1, then enter client.connect 80.76.61.125:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp31,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp31
Max players Slots: 31.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build The server runs game build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is 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.