RUST METRICSFlight deck · live data
Data live Servers11,772 Players62,070 Populated3,548 Fresh wipes 3 h127 Scan5 min
‹ All servers89.182.183.225:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 89.182.183.225:28015 checked 41d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 1 /15

Players now

7% 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,491top 67%
Last wipe70d 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, measured since 17 Sep. 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

Top 67% 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

Reset cycle

When does TestServer wipe?

To tell the rhythm of TestServer, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 70 days 5 hours ago.

Tags

How should you read the tags on TestServer?

Tags published by TestServer, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp15 (Max players): Slots: 15; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163493 (Build): Game build reading: 163493; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as 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.

Which lists and filters on Rust Metrics show TestServer?

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

Population

What position does TestServer hold among Rust servers?

Player hours over seven days put TestServer at #15,491, in the top 67% of all ranked servers.

How full does TestServer get?

Reading for TestServer: offline at this moment; last seen 41 days 8 hours ago.

Server

What location is TestServer hosted in?

No region comes from TestServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 89.182.183.225:28015.

What Rust version is TestServer on?

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

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

TestServer reports offline. The last reading came 41 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 17 September 2026.

Rules and settings

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

Reading the name gives no gather rate for TestServer. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TestServer?

Check: map. Procedural, size 6,000, seed 654317270, generated by the game on TestServer. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players Slots: 15.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163493
Build Game build reading: 163493.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

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