RUST METRICSFlight deck · live data
Data live Servers11,753 Players84,590 Populated3,868 Fresh wipes 3 h169 Scan5 min
‹ All servers138.229.18.147:28021
Offline Full Queue Fresh wipe Wipe due No query

tester

Offline 138.229.18.147:28021 checked 6d 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,437top 69%
Last wipe23d agono schedule published
Next wipe–too few wipes 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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 19:42 UTC23d ago 0 – running 0

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 should you expect from wipe day on tester?

The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does tester follow?

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

Lists and filters

How should you read the tags on tester?

Tags published by tester, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does tester appear in Rust Metrics lists and filters?

On Rust Metrics, tester sits in these lists: 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.

Population

Where does tester sit in the rankings?

Ranking for tester: #15,437 on seven-day player hours, top 69% of all ranked servers.

What is the population on tester?

Reading for tester: offline at this moment; last seen 6 days 2 hours ago. Seven-day reading: 0 players on average.

Operator and location

What location is tester hosted in?

No region tag on tester. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 138.229.18.147:28021.

What Rust version is tester on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by tester. Matching protocol is required to join. Let Steam update your game.

How reliable is tester, and is it online now?

Check: connection. tester is offline at this moment. Last contact was 6 days 2 hours ago. Reading: 23% uptime over the last 7 full days. It was up 38 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for tester. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

What map is tester on?

The game generates a procedural map for tester.

Join

How can you get onto tester?

Press F1 in Rust and enter client.connect 138.229.18.147:28021. 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?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.