RUST METRICSFlight deck · live data
Data live Servers11,620 Players40,450 Populated3,014 Fresh wipes 3 h88 Scan5 min
‹ All servers46.1.62.162:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 46.1.62.162:28015 checked 19d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 38 75 112 150 PAX 0 /150

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,843top 72%
Last wipe19d 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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

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

Reset cycle

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. The world in play was created 19 days 14 hours ago.

Tags

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; mp150 (Max players): Slots: 150; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Build 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TestServer?

These Rust Metrics lists carry 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.

Occupancy

Where does TestServer sit in the rankings?

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

What player count does TestServer carry?

Reading for TestServer: offline at this moment; last seen 19 days 13 hours ago.

Server details

Where does TestServer sit?

No region tag on TestServer. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 46.1.62.162:28015.

What Rust version is TestServer on?

Reading: TestServer, Rust network protocol 2634 and build 167231, Windows. 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 19 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 8 October 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for TestServer. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. 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.

What map is TestServer on?

Check: map. Procedural, generated by the game, on TestServer.

Join

What do you do to join TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp150,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp150
Max players Slots: 150.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build Build 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

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