RUST METRICSFlight deck · live data
Data live Servers11,898 Players103,740 Populated4,020 Fresh wipes 3 h406 Scan5 min
‹ All servers73.188.59.142:28505
Offline Full Queue Fresh wipe Wipe due No query

Testing

Offline 73.188.59.142:28505 checked 8d ago

carbon
COM 1 · connect

Server instruments

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

Players now

2% 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,093top 59%
Last wipe8d agono schedule published
Next wipe–no wipe 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
15k10k15k20k20 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

How often does Testing wipe, and when?

Its rhythm cannot be told from the wipes of Testing on record: there are too few. 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 8 days 21 hours ago.

Tag meanings

How should you read the tags on Testing?

Tags published by Testing, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Testing appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Testing: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

Where does Testing sit in the rankings?

Ranking for Testing: #13,093 on seven-day player hours, top 59% of all ranked servers.

How full does Testing get?

Reading for Testing: offline at this moment; last seen 8 days 19 hours ago.

Server

Which location does Testing run from?

No region tag on Testing. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 73.188.59.142:28505.

What Rust version is Testing on?

Reading: Testing, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. Testing last answered 8 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 October 2026.

Rules and settings

What rules does Testing enforce, and what are its settings?

Check: gather rate. The name Testing does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

What map is Testing on?

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

Connection

How can you get onto Testing?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^y
Carbon Plugin framework in use: Carbon.

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.