RUST METRICSFlight deck · live data
Data live Servers11,668 Players44,124 Populated3,047 Fresh wipes 3 h98 Scan5 min
‹ All servers95.105.3.37:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 95.105.3.37:28015 checked 20d ago

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#12,696top 57%
Last wipe20d 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
15k10k15k20k7 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

Top 57% 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
Wed 7 Oct, 12:10 UTC20d 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 schedule

What should you expect from wipe day on Test?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does Test follow?

The rhythm of Test'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. 20 days 13 hours ago the current world was made.

Tags

How should you read the tags on Test?

Tags published by Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167058 (Build): The server runs game build 167058; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Test appear in Rust Metrics lists and filters?

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?

Player hours over seven days put Test at #12,696, in the top 57% of all ranked servers.

How full does Test get?

Test is not responding; status offline, last seen 20 days 12 hours ago.

Server details

Where does Test sit?

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

What Rust version is Test on?

Reading: Test, Rust network protocol 2634 and build 167058, Windows. Matching protocol is required to join. Let Steam update your game.

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

Test reports offline. The last reading came 20 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 7 October 2026, recorded by Rust Metrics.

Settings and map

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

Check: gather rate. The name Test does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. 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 Test?

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

Connection

What do you do to join Test?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167058,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167058
Build The server runs game build 167058.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.