RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h83 Scan5 min
‹ All servers92.255.174.233:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 92.255.174.233:28015 checked 42d ago

monthly wipes moddedoxide
COM 1 · connect
Launch Rust and join

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,509no region published
Last wipe50d agomonthly schedule
Next wipe8d 0hThu 5 Nov, 19:00 UTC FW
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 Sep22 Sep23 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 8d 0h. The 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 schedule

What wipe timing does TEST follow?

The estimate for TEST's next wipe comes from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 50 days 6 hours ago. Its tags carry a monthly wipe schedule.

Tag meanings

How should you read the tags on TEST?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): 100 slots in total; ts20 (Group limit): Teams are capped at 20; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163407 (Build): The server runs game build 163407; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from TEST. 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?

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

Population

Where does TEST sit in the rankings?

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

What player count does TEST carry?

TEST is not responding; status offline, last seen 42 days 6 hours ago.

Server details

Which location does TEST run from?

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 92.255.174.233:28015.

What Rust version is TEST on?

Version check: Rust network protocol 2633 and build 163407 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is TEST, and is it online now?

Reading: offline. TEST last answered 42 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Map and rules

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

No gather rate appears in the name: TEST. Group size, maximum: 20 players. 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. 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

How do you connect to TEST?

Check: join. Open Rust, press F1, then enter client.connect 92.255.174.233: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,$r?,v2633,^m,gmvanilla,cs163407,ts20,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players 100 slots in total.
ts20
Group limit Teams are capped at 20.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163407
Build The server runs game build 163407.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.