RUST METRICSFlight deck · live data
Data live Servers11,623 Players37,934 Populated2,921 Fresh wipes 3 h81 Scan5 min
‹ All servers185.52.29.79:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 185.52.29.79:28015 checked 27d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.5 3 4.5 6 PAX 0 /6

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,084top 69%
Last wipe33d 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 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

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

The first 48 hours of its last wipes

Fri 25 SepThu 24 SepWed 23 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 25 Sep, 09:50 UTC33d ago 1 – running 0
Thu 24 Sep, 18:15 UTC34d ago 1 – 0.6 days 0
Wed 23 Sep, 14:51 UTC35d ago 2 – 1.1 days 2

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 happens on TEST when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

How often does TEST wipe, and when?

No next wipe can be predicted for TEST, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 33 days 19 hours ago.

Tag meanings

Which tags does TEST carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp6 (Max players): Slots: 6; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163493 (Build): Game build reading: 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from TEST. 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?

On Rust Metrics, TEST sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does TEST hold among Rust servers?

Player hours over seven days put TEST at #16,084, in the top 69% of all ranked servers.

What player count does TEST carry?

TEST is not responding; status offline, last seen 27 days 12 hours ago.

Server details

What location is TEST hosted in?

No region tag on TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 185.52.29.79:28015.

What Rust version is TEST on?

Rust network protocol 2633 and build 163493 on Windows is the build TEST runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is TEST, and is it online now?

TEST reports offline. The last reading came 27 days 12 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

How is TEST configured, and what rules are in force?

Check: gather rate. The name TEST does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

How to join

What do you do to join TEST?

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

PLACARDS

Server tags

what each one means

Published as mp6,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp6
Max players Slots: 6.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163493
Build Game build reading: 163493.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.