RUST METRICSFlight deck · live data
Data live Servers11,644 Players39,744 Populated2,959 Fresh wipes 3 h76 Scan5 min
‹ All servers94.130.167.253:28014
Offline Full Queue Fresh wipe Wipe due No query

(Classy) Rust Testing 1

Offline 94.130.167.253:28014 checked 5d ago

moddedcarbon
COM 1 · connect

Server instruments

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

Players now

no slots published 7-day avg7-day peak 1, past the slots
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 1
Rank#15,007top 67%
Last wipe5d 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, measured since 26 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
15k10k15k20k26 Sep29 Sep2 Oct22 Oct25 Oct28 Oct

Top 67% 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 gap13 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 22 OctTue 20 OctSat 26 Sep
00.511.52+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
Thu 22 Oct, 17:13 UTC5d ago 1 – running 1
Tue 20 Oct, 02:39 UTC8d ago 2 – 2.6 days 0
Sat 26 Sep, 17:54 UTC31d ago 1 – 23.4 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

Reset cycle

What happens on (Classy) Rust Testing 1 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does (Classy) Rust Testing 1 follow?

There is no next wipe to predict: (Classy) Rust Testing 1 wipes at irregular times. 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 5 days 9 hours ago.

Tag meanings

How should you read the tags on (Classy) Rust Testing 1?

These are the tags (Classy) Rust Testing 1 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): The server holds 0 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does (Classy) Rust Testing 1 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring (Classy) Rust Testing 1: 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; Last wipe: In the last week.

Player count

What position does (Classy) Rust Testing 1 hold among Rust servers?

Player hours over seven days put (Classy) Rust Testing 1 at #15,007, in the top 67% of all ranked servers.

What is the population on (Classy) Rust Testing 1?

Reading for (Classy) Rust Testing 1: offline at this moment; last seen 5 days 4 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Server details

Where does (Classy) Rust Testing 1 sit?

No region tag on (Classy) Rust Testing 1. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 94.130.167.253:28014.

What Rust version is (Classy) Rust Testing 1 on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by (Classy) Rust Testing 1. Matching protocol is required to join. Let Steam update your game.

What is the uptime on (Classy) Rust Testing 1, and is it online?

Check: connection. (Classy) Rust Testing 1 is offline at this moment. Last contact was 5 days 4 hours ago. Uptime for the last 7 full days: 5 of 168 hours, or 3%. Reading: first seen 25 September 2026, recorded by Rust Metrics.

Settings and map

What rules does (Classy) Rust Testing 1 enforce, and what are its settings?

Check: gather rate. The name (Classy) Rust Testing 1 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. VAC is on. That is Valve's anti-cheat.

Which map is live on (Classy) Rust Testing 1?

Size 2,048 and seed 1337: the game generates the procedural map on (Classy) Rust Testing 1 from them. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.

Connection

What do you do to join (Classy) Rust Testing 1?

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

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players The server holds 0 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^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.