RUST METRICSFlight deck · live data
Data live Servers11,895 Players92,684 Populated4,089 Fresh wipes 3 h167 Scan5 min
‹ All servers80.76.61.129:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server 31 #1

Offline 80.76.61.129:28015 checked 24d 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,836top 61%
Last wipe25d 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 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

Wipe schedule

When does Test Server 31 #1 wipe?

Its rhythm cannot be told from the wipes of Test Server 31 #1 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 25 days 19 hours ago.

Tag meanings

Which tags does Test Server 31 #1 carry, and what do they mean?

These are the tags Test Server 31 #1 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp31 (Max players): The server holds 31 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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?

On Rust Metrics, Test Server 31 #1 sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does Test Server 31 #1 sit in the rankings?

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

What player count does Test Server 31 #1 carry?

Reading for Test Server 31 #1: offline at this moment; last seen 24 days 19 hours ago.

Server

Which location does Test Server 31 #1 run from?

No region comes from Test Server 31 #1. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 80.76.61.129:28015.

What Rust version is Test Server 31 #1 on?

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

Is Test Server 31 #1 up, and how often does it stay up?

Test Server 31 #1 reports offline. The last reading came 24 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 1 October 2026.

Rules and settings

What rules does Test Server 31 #1 enforce, and what are its settings?

Check: gather rate. The name Test Server 31 #1 does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. 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.

How to join

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

Check: join. Open Rust, press F1, then enter client.connect 80.76.61.129: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?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp31
Max players The server holds 31 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166494
Build Game build reading: 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.