RUST METRICSFlight deck · live data
Data live Servers11,789 Players63,543 Populated3,532 Fresh wipes 3 h121 Scan5 min
‹ All servers85.95.189.133:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 85.95.189.133:28015 checked 33d ago

COM 1 · connect

Server instruments

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

Players now

10% 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,903top 61%
Last wipe33d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 25 Sep, 12:28 UTC33d ago 1 – running 0

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 should you expect from wipe day on TestServer?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does TestServer wipe?

Its rhythm cannot be told from the wipes of TestServer 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. 33 days 9 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): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from TestServer. 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?

Rust Metrics lists featuring TestServer: 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.

Population

Where does TestServer sit in the rankings?

Ranking for TestServer: #13,903 on seven-day player hours, top 61% of all ranked servers.

What is the population on TestServer?

Reading for TestServer: offline at this moment; last seen 33 days 9 hours ago.

Server details

What location is TestServer hosted in?

Reading: location. TestServer gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 85.95.189.133:28015.

What Rust version is TestServer on?

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

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

Reading: offline. TestServer last answered 33 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 25 September 2026.

Settings and map

What settings and rules apply on TestServer?

No gather rate appears in the name: TestServer. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

How to join

What do you do to join TestServer?

Press F1 in Rust and enter client.connect 85.95.189.133: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 mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
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.