RUST METRICSFlight deck · live data
Data live Servers11,727 Players59,874 Populated3,366 Fresh wipes 3 h179 Scan5 min
‹ All servers61.105.188.199:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER

Offline 61.105.188.199:28015 checked 44d ago

biweekly wipes moddedoxidepve
COM 1 · connect
Launch Rust and join

Server instruments

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

Players now

50% 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#12,835no region published
Last wipe45d agobiweekly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
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 Sep21 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The 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 TEST SERVER follow?

An estimate from the force wipe gives TEST SERVER's next wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 45 days 21 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Tags

How should you read the tags on TEST SERVER?

These are the tags TEST SERVER publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): The server runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Two-week wipe schedule; ^r (Roleplay): Roleplay is the purpose of this server; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Plugin framework in use: Oxide (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.

Where does TEST SERVER appear in Rust Metrics lists and filters?

Rust Metrics lists featuring TEST SERVER: Modded Rust servers, checked live, Rust PvE servers and Rust roleplay servers. Check: filters. On the server list it appears under these: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Roleplay ^r, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Population

What position does TEST SERVER hold among Rust servers?

Player hours over seven days put TEST SERVER at #12,835, in the top – of all ranked servers.

What player count does TEST SERVER carry?

TEST SERVER is not responding; status offline, last seen 44 days 18 hours ago.

Server

Where does TEST SERVER sit?

No region tag on TEST SERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 61.105.188.199:28015.

What Rust version is TEST SERVER on?

Reading: TEST SERVER, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is TEST SERVER up, and how often does it stay up?

TEST SERVER reports offline. The last reading came 44 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 14 September 2026.

Rules and settings

How is TEST SERVER configured, and what rules are in force?

No gather rate appears in the name: TEST SERVER. 8 players per group, the default value. Mode check gives roleplay; roleplay rules, jobs and towns. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is TEST SERVER on?

Check: map. Procedural, generated by the game, on TEST SERVER.

How to join

How do you connect to TEST SERVER?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,^b,^r,^p,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players The server holds 2 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build The server runs game build 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Gameplay

^r
Roleplay Roleplay is the purpose of this server.
^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide Plugin framework in use: Oxide (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.