RUST METRICSFlight deck · live data
Data live Servers11,642 Players49,122 Populated3,215 Fresh wipes 3 h106 Scan5 min
‹ All servers9.246.41.58:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 9.246.41.58:28015 checked 23d 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#15,940top 71%
Last wipe24d 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
15k10k15k20k4 Oct5 Oct7 Oct8 Oct10 Oct11 Oct

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

When does TestServer wipe?

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. The world in play was created 24 days ago.

Tag meanings

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

These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does TestServer appear in Rust Metrics lists and filters?

On Rust Metrics, TestServer sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does TestServer hold among Rust servers?

Player hours over seven days put TestServer at #15,940, in the top 71% of all ranked servers.

What player count does TestServer carry?

Status for TestServer: offline. Last seen 23 days 13 hours ago.

Server details

Where does TestServer sit?

Reading: location. TestServer gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 9.246.41.58:28015.

What Rust version is TestServer on?

Reading: TestServer, Rust network protocol 2634 and build 166652, Windows. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is TestServer, and is it online now?

TestServer reports offline. The last reading came 23 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 4 October 2026.

Map and rules

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

Reading the name gives no gather rate for TestServer. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is TestServer on?

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

Connection

How do you connect to TestServer?

Press F1 in Rust and enter client.connect 9.246.41.58: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 mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players The server holds 5 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build The server runs game build 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.