RUST METRICSFlight deck · live data
Data live Servers11,696 Players39,834 Populated3,002 Fresh wipes 3 h90 Scan5 min
‹ All servers5.140.233.21:28015
Offline Full Queue Fresh wipe Wipe due No query

My Solo Test Server

Offline 5.140.233.21:28015 checked 12d ago

COM 1 · connect

Server instruments

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

Players now

20% 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#14,428top 67%
Last wipe12d 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
15k10k15k20k9 Oct12 Oct15 Oct17 Oct20 Oct23 Oct

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 peak1players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 10:03 UTC12d ago 1 – 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 My Solo Test Server?

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

What wipe timing does My Solo Test Server follow?

The rhythm of My Solo Test Server'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. 12 days 16 hours ago the current world was made.

Tag meanings

How should you read the tags on My Solo Test Server?

Tags published by My Solo Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): The server runs game build 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does My Solo Test Server appear in Rust Metrics lists and filters?

Rust Metrics lists featuring My Solo 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; Last wipe: In the last 2 weeks.

Population

Where does My Solo Test Server sit in the rankings?

Player hours over seven days put My Solo Test Server at #14,428, in the top 67% of all ranked servers.

What is the population on My Solo Test Server?

My Solo Test Server is not responding; status offline, last seen 12 days 15 hours ago.

Operator and location

Which location does My Solo Test Server run from?

No region comes from My Solo Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 5.140.233.21:28015.

What Rust version is My Solo Test Server on?

Reading: My Solo Test Server, Rust network protocol 2634 and build 167231, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on My Solo Test Server, and is it online?

Check: connection. My Solo Test Server is offline at this moment. Last contact was 12 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 9 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on My Solo Test Server?

Check: gather rate. The name My Solo Test Server does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join My Solo Test Server?

Check: join. Open Rust, press F1, then enter client.connect 5.140.233.21:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build The server runs game build 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.