RUST METRICSFlight deck · live data
Data live Servers11,605 Players35,310 Populated2,870 Fresh wipes 3 h58 Scan5 min
‹ All servers109.252.87.78:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 109.252.87.78:28015 checked 8d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,318top 70%
Last wipe52d 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
15k10k15k20k20 Sep27 Sep4 Oct12 Oct19 Oct26 Oct

Top 70% 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.

usual gap15.1 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sat 17 OctFri 2 Oct
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
Sat 17 Oct, 09:06 UTC10d ago 0 – running 0
Fri 2 Oct, 07:28 UTC25d ago 0 – 15.1 days 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

Wipe schedule

What should you expect from wipe day on Test?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Test follow?

To tell the rhythm of Test, too few of its wipes 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 52 days 11 hours ago.

Tag meanings

How should you read the tags on Test?

Tags published by Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2617 (Protocol): Protocol 2617: join only on the same game version; cs140244 (Build): The server runs game build 140244; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $reu2 (Region code): eu2 is the region code on record; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Test appear in Rust Metrics lists and filters?

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

Where does Test sit in the rankings?

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

What is the population on Test?

Status for Test: offline. Last seen 8 days 12 hours ago.

Server

Which location does Test run from?

No region tag on Test, whose region code is eu2. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 109.252.87.78:28015.

What Rust version is Test on?

Reading: Test, Rust network protocol 2617 and build 140244, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. Test last answered 8 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 20 September 2026, recorded by Rust Metrics.

Rules and settings

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

No gather rate appears in the name: Test. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is off.

What map is Test on?

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

Join

What do you do to join Test?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$reu2,v2617,gmrust,cs140244,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2617
Protocol Protocol 2617: join only on the same game version.
cs140244
Build The server runs game build 140244.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$reu2
Region code eu2 is the region code on record.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.