RUST METRICSFlight deck · live data
Data live Servers11,640 Players32,367 Populated2,784 Fresh wipes 3 h73 Scan5 min
‹ All servers5.186.56.195:28015
Offline Full Queue Fresh wipe Wipe due No query

Testserver

Offline 5.186.56.195:28015 checked 43d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#15,419no region published
Last wipe49d 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 Sep21 Sep22 Sep
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

How often does Testserver wipe, and when?

Its rhythm cannot be told from the wipes of Testserver 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. 49 days 8 hours ago the current world was made.

Tags

Which tags does Testserver carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 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; cs163794 (Build): The server runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Testserver. 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?

On Rust Metrics, Testserver sits in these lists: 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.

Population

Where does Testserver sit in the rankings?

Ranking for Testserver: #15,419 on seven-day player hours, top – of all ranked servers.

What player count does Testserver carry?

Testserver is not responding; status offline, last seen 43 days 9 hours ago.

Server details

What location is Testserver hosted in?

Reading: location. Testserver gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 5.186.56.195:28015.

What Rust version is Testserver on?

Rust network protocol 2633 and build 163794 on Linux is the build Testserver runs. Check: protocol. To join, your game must match; Steam handles the update.

Is Testserver up, and how often does it stay up?

Testserver reports offline. The last reading came 43 days 9 hours 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 15 September 2026.

Rules and settings

How is Testserver configured, and what rules are in force?

No gather rate appears in the name: Testserver. 8 players per group, the default value. 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. VAC is off. That is Valve's anti-cheat.

What map is Testserver on?

Check: map. Procedural, generated by the game, on Testserver.

Connection

How can you get onto Testserver?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 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.
cs163794
Build The server runs game build 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.