RUST METRICSFlight deck · live data
Data live Servers11,890 Players103,852 Populated4,020 Fresh wipes 3 h420 Scan5 min
‹ All servers188.244.248.224:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 188.244.248.224:28015 checked 9d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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,094top 59%
Last wipe9d 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 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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
Tue 20 Oct, 09:33 UTC9d ago 1 – running 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?

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

What wipe timing does TEST follow?

The rhythm of TEST's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 9 days 9 hours ago.

Tag meanings

How should you read the tags on TEST?

These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. 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. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does TEST sit in the rankings?

Player hours over seven days put TEST at #13,094, in the top 59% of all ranked servers.

What player count does TEST carry?

Reading for TEST: offline at this moment; last seen 9 days 3 hours ago.

Operator and location

Where does TEST sit?

Reading: location. TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 188.244.248.224:28015.

What Rust version is TEST on?

Rust network protocol 2634 and build 167781 on Windows is the build TEST runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. TEST is offline at this moment. Last contact was 9 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 20 October 2026.

Map and rules

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

Reading the name gives no gather rate for TEST. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. 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 Oxide of them. VAC is on. That is Valve's anti-cheat.

What map is TEST on?

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

Connection

What do you do to join TEST?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^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.