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

Test Server 31 #1

Offline 45.135.166.210:28015 checked 35d 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,243top 58%
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
15k10k15k20k20 Sep22 Sep24 Sep25 Sep27 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

Reset cycle

What wipe timing does Test Server 31 #1 follow?

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 it runs now was made 52 days 6 hours ago.

Tags

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): Slots: 31; 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): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Test Server 31 #1?

On Rust Metrics, Test Server 31 #1 sits in these lists: 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,243 on seven-day player hours, top 58% of all ranked servers.

What player count does Test Server 31 #1 carry?

Status for Test Server 31 #1: offline. Last seen 35 days 23 hours ago.

Operator and location

What location is Test Server 31 #1 hosted in?

Reading: location. Test Server 31 #1 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 45.135.166.210: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. Matching protocol is required to join. Let Steam update your game.

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

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

Settings and map

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

Reading the name gives no gather rate for Test Server 31 #1. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is Test Server 31 #1 on?

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

Join

How can you get onto Test Server 31 #1?

Press F1 in Rust and enter client.connect 45.135.166.210:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp31
Max players Slots: 31.
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 Build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.