RUST METRICSFlight deck · live data
Data live Servers11,657 Players49,583 Populated3,193 Fresh wipes 3 h101 Scan5 min
‹ All servers130.86.76.58:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 130.86.76.58:28015 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,670top 70%
Last wipe27d 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

Top 70% 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 peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 01:36 UTC27d ago 0 – running 0

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 should you expect from wipe day on Test Server?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does Test Server wipe, and when?

The rhythm of Test Server's wipes cannot be told yet: too few 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 in play was created 27 days 7 hours ago.

Tags

How should you read the tags on Test Server?

These are the tags Test Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166440 (Build): Game build reading: 166440; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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?

Rust Metrics lists featuring Test Server: 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

What position does Test Server hold among Rust servers?

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

How full does Test Server get?

Test Server is not responding; status offline, last seen 27 days 6 hours ago.

Server details

Where does Test Server sit?

No region comes from Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 130.86.76.58:28015.

What Rust version is Test Server on?

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

How reliable is Test Server, and is it online now?

Check: connection. Test Server is offline at this moment. Last contact was 27 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 30 September 2026.

Settings and map

What settings and rules apply on Test Server?

Check: gather rate. The name Test Server does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is Test Server on?

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

How to join

How can you get onto Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166440,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166440
Build Game build reading: 166440.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.