RUST METRICSFlight deck · live data
Data live Servers11,693 Players37,293 Populated2,927 Fresh wipes 3 h93 Scan5 min
‹ All servers95.27.214.81:28015
Offline Full Queue Fresh wipe Wipe due No query

testserver

Offline 95.27.214.81:28015 checked 25d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

Players now

0% 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#16,013top 70%
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
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 Oct

Top 70% 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

When does testserver wipe?

To tell the rhythm of testserver, 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 it runs now was made 25 days 11 hours ago.

Lists and filters

How should you read the tags on testserver?

These are the tags testserver publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163207 (Build): Build 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does testserver appear in Rust Metrics lists and filters?

These Rust Metrics lists carry testserver: Rust community servers: live readings. 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.

Player count

Where does testserver sit in the rankings?

Ranking for testserver: #16,013 on seven-day player hours, top 70% of all ranked servers.

What is the population on testserver?

testserver is not responding; status offline, last seen 25 days 8 hours ago.

Server details

Which location does testserver run from?

No region tag on testserver. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 95.27.214.81:28015.

What Rust version is testserver on?

Rust network protocol 2633 and build 163207 on Windows is the build testserver runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on testserver, and is it online?

testserver reports offline. The last reading came 25 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 3 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does testserver enforce, and what are its settings?

Check: gather rate. The name testserver does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. 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 testserver?

Procedural map on testserver, made by the game's generator.

Join

How can you get onto testserver?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs163207,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players 2 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163207
Build Build 163207.
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.