RUST METRICSFlight deck · live data
Data live Servers11,883 Players104,335 Populated3,951 Fresh wipes 3 h530 Scan5 min
‹ All servers194.14.193.164:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 194.14.193.164:28015 checked 28d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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,336top 60%
Last wipe28d 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
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 Oct

Top 60% 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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 30 Sep, 20:20 UTC28d ago 1 – running 1

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.

How often does Test wipe, and when?

The rhythm of Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 28 days 23 hours ago.

Tags

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

These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. 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?

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

Population

What position does Test hold among Rust servers?

Player hours over seven days put Test at #14,336, in the top 60% of all ranked servers.

What player count does Test carry?

Reading for Test: offline at this moment; last seen 28 days 22 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. Check: address. It reads 194.14.193.164:28015.

What Rust version is Test on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by Test. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Test, and is it online now?

Test reports offline. The last reading came 28 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 30 September 2026, recorded by Rust Metrics.

Rules and settings

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

No gather rate appears in the name: Test. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Connection

How do you connect to Test?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build 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.