RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h95 Scan5 min
‹ All servers94.243.8.222:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 94.243.8.222:28015 checked 4d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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#15,426top 69%
Last wipe4d 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
15k10k15k20k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

Top 69% 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 gap0.9 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sat 24 OctFri 23 Oct
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
Sat 24 Oct, 10:23 UTC4d ago 0 – running 0
Fri 23 Oct, 12:35 UTC5d ago 0 – 0.9 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 schedule

What happens on Test when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does Test wipe?

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. 4 days 8 hours ago the current world was made.

Lists and filters

How should you read the tags on Test?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Test: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

Where does Test sit in the rankings?

Player hours over seven days put Test at #15,426, in the top 69% of all ranked servers.

What player count does Test carry?

Test is not responding; status offline, last seen 4 days 7 hours ago. A seven-day average of 0 players is the reading.

Operator and location

Which location does Test run from?

No region tag on Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 94.243.8.222:28015.

What Rust version is Test on?

Rust network protocol 2635 and build 168909 on Windows is the build Test runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. Test last answered 4 days 7 hours ago. Reading: 2% uptime over the last 5 full days. It was up 3 of 120 hours. Reading: first seen 22 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does Test enforce, and what are its settings?

Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

What map is Test on?

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

Join

How do you connect to Test?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.