RUST METRICSFlight deck · live data
Data live Servers11,768 Players60,085 Populated3,517 Fresh wipes 3 h135 Scan5 min
‹ All servers79.233.81.191:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 79.233.81.191:28015 checked 25d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,000top 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

Wipe timing

What wipe timing does TestServer follow?

The rhythm of TestServer's wipes cannot be told yet: too few 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 12 hours ago.

Lists and filters

How should you read the tags on TestServer?

Tags published by TestServer, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is 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.

Occupancy

Where does TestServer sit in the rankings?

Player hours over seven days put TestServer at #16,000, in the top 70% of all ranked servers.

What is the population on TestServer?

Status for TestServer: offline. Last seen 25 days 9 hours ago.

Server details

Where does TestServer sit?

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 79.233.81.191:28015.

What Rust version is TestServer on?

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

How reliable is TestServer, and is it online now?

Check: connection. TestServer is offline at this moment. Last contact was 25 days 9 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.

Settings and map

What settings and rules apply on TestServer?

Reading the name gives no gather rate for TestServer. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is TestServer on?

The game generates a procedural map for TestServer.

How to join

What do you do to join TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build The server runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.