RUST METRICSFlight deck · live data
Data live Servers11,646 Players42,725 Populated3,027 Fresh wipes 3 h89 Scan5 min
‹ All servers194.147.90.128:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST | MAIN | Wipe 03.01

Offline 194.147.90.128:28015 checked 5d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 50 100 150 200 PAX 0 /200

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,338top 69%
Last wipe10d 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
15k10k15k20k18 Oct20 Oct22 Oct25 Oct27 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

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 schedule

How often does TEST | MAIN | Wipe 03.01 wipe, and when?

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

Lists and filters

How should you read the tags on TEST | MAIN | Wipe 03.01?

Tags published by TEST | MAIN | Wipe 03.01, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): Slots: 200; ts8 (Group limit): The game default applies: teams of up to 8; v2632 (Protocol): Protocol 2632: join only on the same game version; cs160556 (Build): Build 160556; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does TEST | MAIN | Wipe 03.01 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry TEST | MAIN | Wipe 03.01: Modded Rust servers, checked live. These filters bring it up on the server list: 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 | MAIN | Wipe 03.01 sit in the rankings?

Ranking for TEST | MAIN | Wipe 03.01: #15,338 on seven-day player hours, top 69% of all ranked servers.

How full does TEST | MAIN | Wipe 03.01 get?

Status for TEST | MAIN | Wipe 03.01: offline. Last seen 5 days 11 hours ago. Seven-day reading: 0 players on average.

Operator and location

Which location does TEST | MAIN | Wipe 03.01 run from?

No region tag on TEST | MAIN | Wipe 03.01. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 194.147.90.128:28015.

What Rust version is TEST | MAIN | Wipe 03.01 on?

Rust network protocol 2632 and build 160556 on Windows is the build TEST | MAIN | Wipe 03.01 runs. Check: protocol. To join, your game must match; Steam handles the update.

Is TEST | MAIN | Wipe 03.01 up, and how often does it stay up?

TEST | MAIN | Wipe 03.01 reports offline. The last reading came 5 days 11 hours ago. Reading: 27% uptime over the last 7 full days. It was up 46 of 168 hours. The first sighting on Rust Metrics was 18 October 2026.

Settings and map

How is TEST | MAIN | Wipe 03.01 configured, and what rules are in force?

No gather rate appears in the name: TEST | MAIN | Wipe 03.01. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. 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 on.

What map is TEST | MAIN | Wipe 03.01 on?

Procedural map on TEST | MAIN | Wipe 03.01, made by the game's generator.

Connection

What do you do to join TEST | MAIN | Wipe 03.01?

To join: start Rust, press F1 and type client.connect 194.147.90.128:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players Slots: 200.
ts8
Group limit The game default applies: teams of up to 8.
v2632
Protocol Protocol 2632: join only on the same game version.
cs160556
Build Build 160556.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

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