RUST METRICSFlight deck · live data
Data live Servers11,853 Players81,845 Populated3,922 Fresh wipes 3 h171 Scan5 min
‹ All servers91.83.37.40:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER

Offline 91.83.37.40:28015 checked 38d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#13,747no region published
Last wipe54d 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
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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

How often does TEST SERVER wipe, and when?

The rhythm of TEST SERVER's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 54 days 2 hours ago the current world was made.

Tags

Which tags does TEST SERVER carry, and what do they mean?

These are the tags TEST SERVER publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): Build 162929; 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): 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?

On Rust Metrics, TEST SERVER 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

What position does TEST SERVER hold among Rust servers?

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

What player count does TEST SERVER carry?

Reading for TEST SERVER: offline at this moment; last seen 38 days 6 hours ago.

Operator and location

Where does TEST SERVER sit?

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

What Rust version is TEST SERVER on?

Version check: Rust network protocol 2633 and build 162929 on Windows, run by TEST SERVER. Matching protocol is required to join. Let Steam update your game.

What is the uptime on TEST SERVER, and is it online?

Check: connection. TEST SERVER is offline at this moment. Last contact was 38 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 19 September 2026.

Settings and map

What rules does TEST SERVER enforce, and what are its settings?

Reading the name gives no gather rate for TEST SERVER. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is off. That is Valve's anti-cheat.

What map is TEST SERVER on?

Procedural map on TEST SERVER, made by the game's generator.

How to join

What do you do to join TEST SERVER?

Check: join. Open Rust, press F1, then enter client.connect 91.83.37.40:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmvanilla,cs162929,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs162929
Build Build 162929.
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 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.