RUST METRICSFlight deck · live data
Data live Servers11,694 Players52,148 Populated3,104 Fresh wipes 3 h109 Scan5 min
‹ All servers138.219.94.130:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServerSolo

Offline 138.219.94.130:28015 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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,797top 60%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k30 Sep2 Oct4 Oct5 Oct7 Oct9 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctThu 1 OctThu 1 Oct
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 2 Oct, 16:07 UTC27d ago 1 – running 0
Thu 1 Oct, 18:19 UTC FW28d ago 1 – 0.9 days 1
Thu 1 Oct, 11:27 UTC28d ago 1 – 0.3 days 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

Wipe schedule

What happens on TestServerSolo when wipe day comes?

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 TestServerSolo wipe?

There is no next wipe to predict: TestServerSolo wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 27 days 9 hours ago the current world was made.

Tags

How should you read the tags on TestServerSolo?

These are the tags TestServerSolo publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): The server runs game build 166586; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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 TestServerSolo?

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

Player count

What position does TestServerSolo hold among Rust servers?

Ranking for TestServerSolo: #13,797 on seven-day player hours, top 60% of all ranked servers.

How full does TestServerSolo get?

TestServerSolo is not responding; status offline, last seen 27 days 9 hours ago.

Server

Where does TestServerSolo sit?

No region comes from TestServerSolo. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 138.219.94.130:28015.

What Rust version is TestServerSolo on?

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

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

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

Rules and settings

What settings and rules apply on TestServerSolo?

No gather rate appears in the name: TestServerSolo. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is TestServerSolo on?

The game generates a procedural map for TestServerSolo.

Connection

How can you get onto TestServerSolo?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build The server runs game build 166586.
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.