RUST METRICSFlight deck · live data
Data live Servers11,789 Players63,543 Populated3,532 Fresh wipes 3 h121 Scan5 min
‹ All servers91.1.111.20:28045
Offline Full Queue Fresh wipe Wipe due No query

rmtest

Offline 91.1.111.20:28045 checked 30d ago

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 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,963top 71%
Last wipe30d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k26 Sep28 Sep30 Sep1 Oct3 Oct5 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap1.2 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Mon 28 SepSat 26 Sep
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 01:00 UTC30d ago 0 – running 0
Sat 26 Sep, 19:51 UTC32d ago 0 – 1.2 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 timing

What should you expect from wipe day on rmtest?

An average of 0 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does rmtest follow?

To tell the rhythm of rmtest, too few of its wipes 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. The world it runs now was made 30 days 21 hours ago.

Tags

How should you read the tags on rmtest?

Tags published by rmtest, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does rmtest appear in Rust Metrics lists and filters?

On Rust Metrics, rmtest sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does rmtest sit in the rankings?

Ranking for rmtest: #16,963 on seven-day player hours, top 71% of all ranked servers.

What player count does rmtest carry?

Reading for rmtest: offline at this moment; last seen 30 days 21 hours ago.

Server details

Where does rmtest sit?

Reading: location. rmtest gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 91.1.111.20:28045.

What Rust version is rmtest on?

Rust network protocol 2633 and build 165217 on Windows is the build rmtest runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. rmtest last answered 30 days 21 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 26 September 2026.

Settings and map

What settings and rules apply on rmtest?

Check: gather rate. The name rmtest does not state one. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on rmtest?

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

Connection

What do you do to join rmtest?

To join: start Rust, press F1 and type client.connect 91.1.111.20:28045. 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,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players 2 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.