RUST METRICSFlight deck · live data
Data live Servers11,701 Players54,561 Populated3,263 Fresh wipes 3 h144 Scan5 min
‹ All servers38.59.10.124:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Rust

Offline 38.59.10.124:28015 checked 34d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,749top 71%
Last wipe36d 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
15k10k15k20k23 Sep25 Sep26 Sep28 Sep29 Sep1 Oct

Top 71% 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
Wed 23 Sep, 00:27 UTC36d 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

Reset cycle

What should you expect from wipe day on Test Rust?

At their busiest, its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

When does Test Rust wipe?

The rhythm of Test Rust's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 36 days 11 hours ago.

Tag meanings

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

Tags published by Test Rust, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Test Rust?

On Rust Metrics, Test Rust sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

What position does Test Rust hold among Rust servers?

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

What player count does Test Rust carry?

Reading for Test Rust: offline at this moment; last seen 34 days 18 hours ago.

Server

Where does Test Rust sit?

Reading: location. Test Rust gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 38.59.10.124:28015.

What Rust version is Test Rust on?

Rust network protocol 2633 and build 165217 on Windows is the build Test Rust runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Test Rust, and is it online?

Test Rust reports offline. The last reading came 34 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 23 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Test Rust?

No gather rate appears in the name: Test Rust. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Test Rust?

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

How to join

How can you get onto Test Rust?

Press F1 in Rust and enter client.connect 38.59.10.124: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 mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Carbon handles the plugins here.

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.