RUST METRICSFlight deck · live data
Data live Servers11,620 Players35,442 Populated2,860 Fresh wipes 3 h74 Scan5 min
‹ All servers61.8.128.15:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 61.8.128.15:28015 checked 8d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,366top 70%
Last wipe20d 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 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

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

When does TestServer wipe?

Its rhythm cannot be told from the wipes of TestServer 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. 20 days 23 hours ago the current world was made.

Tag meanings

How should you read the tags on TestServer?

These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167058 (Build): Game build reading: 167058; 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): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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.

Player count

Where does TestServer sit in the rankings?

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

How full does TestServer get?

TestServer is not responding; status offline, last seen 8 days 13 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. The endpoint you need is 61.8.128.15:28015.

What Rust version is TestServer on?

Rust network protocol 2634 and build 167058 on Windows is the build TestServer runs. 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 8 days 13 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 20 October 2026.

Rules and settings

What settings and rules apply on TestServer?

Check: gather rate. The name TestServer does not state one. 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. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TestServer?

The game generates a procedural map for TestServer.

Connection

How can you get onto TestServer?

Press F1 in Rust and enter client.connect 61.8.128.15: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 mp5,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167058
Build Game build reading: 167058.
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 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.