RUST METRICSFlight deck · live data
Data live Servers11,826 Players80,135 Populated3,731 Fresh wipes 3 h265 Scan5 min
‹ All servers91.186.105.117:28015
Offline Full Queue Fresh wipe Wipe due No query

test

Offline 91.186.105.117:28015 checked 24d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% 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#14,651top 65%
Last wipe24d 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
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

Top 65% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 11:13 UTC24d ago 1 – running 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 happens on test when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does test follow?

Its rhythm cannot be told from the wipes of test on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 24 days 2 hours ago.

Tags

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

Tags published by test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show test?

On Rust Metrics, test 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 test sit in the rankings?

Ranking for test: #14,651 on seven-day player hours, top 65% of all ranked servers.

What player count does test carry?

Reading for test: offline at this moment; last seen 24 days 2 hours ago.

Operator and location

What location is test hosted in?

Reading: location. test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 91.186.105.117:28015.

What Rust version is test on?

Rust network protocol 2634 and build 166652 on Windows is the build test runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on test, and is it online?

Reading: offline. test last answered 24 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 5 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on test?

Reading the name gives no gather rate for test. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.

What map is test on?

The game generates a procedural map for test.

How to join

How do you connect to test?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Build 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.