RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h50 Scan5 min
‹ All servers80.76.61.119:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server 31 #1

Offline 80.76.61.119:28015 checked 36d 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,249top 58%
Last wipe53d 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
15k10k15k20k22 Sep23 Sep25 Sep26 Sep28 Sep29 Sep

Top 58% 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 timing

How often does Test Server 31 #1 wipe, and when?

Its rhythm cannot be told from the wipes of Test Server 31 #1 on record: there are too few. 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 53 days ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp31 (Max players): The server holds 31 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from Test Server 31 #1. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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.

Player count

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

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

How full does Test Server 31 #1 get?

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

Server

Where does Test Server 31 #1 sit?

No region comes from Test Server 31 #1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 80.76.61.119:28015.

What Rust version is Test Server 31 #1 on?

Reading: Test Server 31 #1, Rust network protocol 2633 and build 163794, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Test Server 31 #1, and is it online?

Test Server 31 #1 reports offline. The last reading came 36 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 22 September 2026.

Map and rules

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. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. 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?

Procedural map on Test Server 31 #1, made by the game's generator.

Join

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

To join: start Rust, press F1 and type client.connect 80.76.61.119:28015. Or press Launch Rust here and Steam opens the game 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 The server holds 31 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Game build reading: 163794.
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.