RUST METRICSFlight deck · live data
Data live Servers11,777 Players67,749 Populated3,536 Fresh wipes 3 h194 Scan5 min
‹ All servers176.191.115.19:28015
Offline Full Queue Fresh wipe Wipe due No query

Testserver

Offline 176.191.115.19:28015 checked 32d 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#16,953top 72%
Last wipe32d 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
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 Oct

Top 72% 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 Testserver follow?

Its rhythm cannot be told from the wipes of Testserver on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 32 days 3 hours ago.

Lists and filters

How should you read the tags on Testserver?

Tags published by Testserver, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; 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.

Where does Testserver appear in Rust Metrics lists and filters?

On Rust Metrics, Testserver 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.

Player count

Where does Testserver sit in the rankings?

Player hours over seven days put Testserver at #16,953, in the top 72% of all ranked servers.

What player count does Testserver carry?

Testserver is not responding; status offline, last seen 32 days 3 hours ago.

Server

Where does Testserver sit?

No region comes from Testserver. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 176.191.115.19:28015.

What Rust version is Testserver on?

Reading: Testserver, Rust network protocol 2633 and build 165217, Linux. Matching protocol is required to join. Let Steam update your game.

How reliable is Testserver, and is it online now?

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

Map and rules

What settings and rules apply on Testserver?

Reading the name gives no gather rate for Testserver. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is Testserver on?

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

How to join

What do you do to join Testserver?

To join: start Rust, press F1 and type client.connect 176.191.115.19:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmvanilla,cs165217,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Game build reading: 165217.
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.