RUST METRICSFlight deck · live data
Data live Servers11,847 Players92,510 Populated3,855 Fresh wipes 3 h385 Scan5 min
‹ All servers142.93.124.180:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 142.93.124.180:28015 checked 45d 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,021no region published
Last wipe73d 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 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

Reset cycle

What wipe timing does TestServer follow?

The rhythm of TestServer's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 73 days 14 hours ago the current world was made.

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; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2632 (Protocol): Match the game version: protocol 2632 is required; cs160556 (Build): Build 160556; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does TestServer appear in Rust Metrics lists and filters?

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

Player count

What position does TestServer hold among Rust servers?

Ranking for TestServer: #15,021 on seven-day player hours, top – of all ranked servers.

What player count does TestServer carry?

Reading for TestServer: offline at this moment; last seen 45 days 1 hours ago.

Operator and location

Which location does TestServer run from?

Reading: location. TestServer gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 142.93.124.180:28015.

What Rust version is TestServer on?

Rust network protocol 2632 and build 160556 on Linux is the build TestServer runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. TestServer is offline at this moment. Last contact was 45 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What rules does TestServer enforce, and what are its settings?

Check: gather rate. The name TestServer does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. 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.

How to join

How can you get onto TestServer?

Press F1 in Rust and enter client.connect 142.93.124.180: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 Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2632
Protocol Match the game version: protocol 2632 is required.
cs160556
Build Build 160556.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.