RUST METRICSFlight deck · live data
Data live Servers11,751 Players55,890 Populated3,402 Fresh wipes 3 h132 Scan5 min
‹ All servers73.34.19.41:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 73.34.19.41:28015 checked 1d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

Players now

0% full 7-day avg7-day peak
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 average1peak 1
Rank#9,174top 41%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75101:0003:0004:0006:0007:0009:00

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
15k10k15k20k28 Sep3 Oct7 Oct12 Oct16 Oct28 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap4 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 8 OctSun 4 OctWed 30 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 00:55 UTC1d ago – – running 0
Thu 8 Oct, 05:39 UTC20d ago 1 held half 18.8 days 1
Sun 4 Oct, 02:36 UTC24d ago 1 held half 4.1 days 0
Wed 30 Sep, 04:10 UTC28d ago 0 – 3.9 days 0
Mon 28 Sep, 20:21 UTC30d ago 1 – 1.3 days 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

Wipe schedule

What happens on TestServer when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does TestServer follow?

There is no next wipe to predict: TestServer wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 44 hours ago the current world was made.

Tags

How should you read the tags on TestServer?

These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): Slots: 2; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^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.

Which lists and filters on Rust Metrics show TestServer?

These Rust Metrics lists carry 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; Last wipe: In the last 3 days.

Player count

What position does TestServer hold among Rust servers?

Ranking for TestServer: #9,174 on seven-day player hours, top 41% of all ranked servers.

What is the population on TestServer?

TestServer is not responding; status offline, last seen 37 hours ago. Check: players over seven days. Average 1, peak 1. Check: 48-hour peak. 06:00 UTC, 1 players on average.

Server

Which location does TestServer run from?

No region tag on TestServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 73.34.19.41:28015.

What Rust version is TestServer on?

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

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

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

Rules and settings

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

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: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. 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, generated by the game, on TestServer.

Connection

How can you get onto TestServer?

Press F1 in Rust and enter client.connect 73.34.19.41: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 mp2,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players Slots: 2.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.