RUST METRICSFlight deck · live data
Data live Servers11,750 Players60,289 Populated3,494 Fresh wipes 3 h126 Scan5 min
‹ All servers178.178.94.57:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 178.178.94.57:28015 checked 37d ago

moddedoxide
COM 1 · connect

Server instruments

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

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,467no region published
Last wipe37d 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 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
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 timing

What wipe timing does TEST follow?

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

Lists and filters

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

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): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2632 (Protocol): Your game must run protocol 2632 to get in; cs160556 (Build): Build 160556; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^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?

These Rust Metrics lists carry TEST: 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.

Player count

What position does TEST hold among Rust servers?

Player hours over seven days put TEST at #15,467, in the top – of all ranked servers.

What player count does TEST carry?

TEST is not responding; status offline, last seen 37 days 14 hours ago.

Server details

Which location does TEST run from?

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

What Rust version is TEST on?

Version check: Rust network protocol 2632 and build 160556 on Windows, run by TEST. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. TEST last answered 37 days 14 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 20 September 2026.

Settings and map

What settings and rules apply on TEST?

Check: gather rate. The name TEST does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on TEST?

Check: map. Procedural, generated by the game, on TEST.

How to join

How do you connect to TEST?

Press F1 in Rust and enter client.connect 178.178.94.57:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2632,gmrust,cs160556,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2632
Protocol Your game must run protocol 2632 to get in.
cs160556
Build Build 160556.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.