RUST METRICSFlight deck · live data
Data live Servers11,633 Players55,123 Populated3,183 Fresh wipes 3 h136 Scan5 min
‹ All servers82.67.108.110:28025
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER

Offline 82.67.108.110:28025 checked 21d ago

moddedcarbon
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#14,865top 67%
Last wipe25d 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. 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 Sep25 Sep30 Sep5 Oct10 Oct15 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 gap2.2 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Sun 4 OctFri 2 OctThu 1 Oct
00.250.50.751+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
Sun 4 Oct, 17:14 UTC25d ago 1 – running 0
Fri 2 Oct, 08:55 UTC28d ago 1 – 2.3 days 0
Thu 1 Oct, 18:25 UTC FW28d ago 1 – 0.6 days 1
Thu 24 Sep, 14:07 UTC35d ago 1 – 7.2 days 0
Tue 22 Sep, 11:10 UTC37d ago 1 – 2.1 days 0
Tue 15 Sep, 16:39 UTC44d ago 1 halved by day 3 6.8 days 0
Sun 13 Sep, 18:15 UTC46d ago 1 – 1.9 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

Wipe timing

What should you expect from wipe day on TEST SERVER?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 3 it fell below half when it didn't.

What wipe timing does TEST SERVER follow?

No next wipe can be predicted for TEST SERVER, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 25 days 16 hours ago the current world was made.

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): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167231 (Build): Game build reading: 167231; 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): Plugin framework in use: Carbon. 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 SERVER?

These Rust Metrics lists carry TEST SERVER: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Player count

Where does TEST SERVER sit in the rankings?

Player hours over seven days put TEST SERVER at #14,865, in the top 67% of all ranked servers.

How full does TEST SERVER get?

Reading for TEST SERVER: offline at this moment; last seen 21 days 11 hours ago.

Operator and location

What location is TEST SERVER hosted in?

No region comes from TEST SERVER. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 82.67.108.110:28025.

What Rust version is TEST SERVER on?

Rust network protocol 2634 and build 167231 on Linux is the build TEST SERVER runs. Matching protocol is required to join. Let Steam update your game.

How reliable is TEST SERVER, and is it online now?

Reading: offline. TEST SERVER last answered 21 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What settings and rules apply on TEST SERVER?

No gather rate appears in the name: TEST SERVER. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. 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 SERVER?

The game generates a procedural map for TEST SERVER.

How to join

How can you get onto TEST SERVER?

Check: join. Open Rust, press F1, then enter client.connect 82.67.108.110:28025. 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,cs167231,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167231
Build Game build reading: 167231.
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 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.