RUST METRICSFlight deck · live data
Data live Servers11,851 Players93,847 Populated3,878 Fresh wipes 3 h391 Scan5 min
‹ All servers51.38.155.204:23915
Offline Full Queue Fresh wipe Wipe due No query

Test server

Offline 51.38.155.204:23915 checked 38d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 19 38 56 75 PAX 1 /75

Players now

1% 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,491top 67%
Last wipe38d 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, measured since 17 Sep. 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

Top 67% 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 peak2players, 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 2, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 21 Sep, 14:43 UTC38d ago 2 – running 1

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 Test server?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 0 hours.

How often does Test server wipe, and when?

To tell the rhythm of Test server, too few of its wipes are on record. 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 38 days ago.

Tags

Which tags does Test server carry, and what do they mean?

Tags published by Test server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp75 (Max players): The server holds 75 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165081 (Build): The server runs game build 165081; 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.

Which lists and filters on Rust Metrics show Test server?

These Rust Metrics lists carry Test server: 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.

Player count

Where does Test server sit in the rankings?

Ranking for Test server: #15,491 on seven-day player hours, top 67% of all ranked servers.

What is the population on Test server?

Test server is not responding; status offline, last seen 38 days ago.

Operator and location

Where does Test server sit?

No region comes from Test server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 51.38.155.204:23915.

What Rust version is Test server on?

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

Is Test server up, and how often does it stay up?

Check: connection. Test server is offline at this moment. Last contact was 38 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Rules and settings

How is Test server configured, and what rules are in force?

No gather rate appears in the name: Test server. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Test server?

Size 3,100 and seed 50000: the game generates the procedural map on Test server from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How do you connect to Test server?

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

PLACARDS

Server tags

what each one means

Published as mp75,ptrak,$r?,v2633,gmrust,cs165081,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp75
Max players The server holds 75 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165081
Build The server runs game build 165081.
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.