RUST METRICSFlight deck · live data
Data live Servers11,732 Players72,530 Populated3,645 Fresh wipes 3 h126 Scan5 min
‹ All servers162.43.49.241:28015
Offline Full Queue Fresh wipe Wipe due No query

testserver

Offline 162.43.49.241:28015 checked 28d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 0 /20

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,853top 71%
Last wipe51d 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, measured since 17 Sep. 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 Sep23 Sep26 Sep30 Sep3 Oct6 Oct

Top 71% 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 timing

What wipe timing does testserver follow?

To tell the rhythm of testserver, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 51 days 22 hours ago the current world was made.

Tag meanings

Which tags does testserver carry, and what do they mean?

These are the tags testserver publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): 20 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): Game build reading: 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does testserver appear in Rust Metrics lists and filters?

On Rust Metrics, testserver sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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 #16,853, in the top 71% of all ranked servers.

How full does testserver get?

Status for testserver: offline. Last seen 28 days 17 hours ago.

Operator and location

Which location does testserver run from?

Reading: location. testserver gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 162.43.49.241:28015.

What Rust version is testserver on?

Version check: Rust network protocol 2633 and build 163207 on Linux, run by testserver. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. testserver is offline at this moment. Last contact was 28 days 17 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.

Settings and map

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

Check: gather rate. The name testserver does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is testserver on?

Size 5,000 and seed 2: the game generates the procedural map on testserver from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto testserver?

To join: start Rust, press F1 and type client.connect 162.43.49.241:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp20
Max players 20 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163207
Build Game build reading: 163207.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^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.