RUST METRICSFlight deck · live data
Data live Servers11,640 Players39,046 Populated2,948 Fresh wipes 3 h69 Scan5 min
‹ All servers178.178.89.45:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 178.178.89.45:28015 checked 31d ago

moddedoxide
COM 1 · connect

Server instruments

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

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#16,840top 72%
Last wipe31d 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
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 Oct

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

What wipe timing does TestServer follow?

The rhythm of TestServer's wipes cannot be told yet: too few 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 31 days 17 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): Survival, as standard Rust plays it; mp15 (Max players): Slots: 15; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (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?

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

Occupancy

Where does TestServer sit in the rankings?

Player hours over seven days put TestServer at #16,840, in the top 72% of all ranked servers.

What is the population on TestServer?

TestServer is not responding; status offline, last seen 31 days 8 hours ago.

Server details

Which location does TestServer run from?

No region tag on TestServer. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 178.178.89.45:28015.

What Rust version is TestServer on?

Reading: TestServer, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. TestServer is offline at this moment. Last contact was 31 days 8 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 26 September 2026.

Settings and map

What settings and rules apply on TestServer?

No gather rate appears in the name: 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. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on TestServer?

The game generates a procedural map for TestServer.

Connection

How can you get onto TestServer?

Check: join. Open Rust, press F1, then enter client.connect 178.178.89.45: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,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players Slots: 15.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (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.