RUST METRICSFlight deck · live data
Data live Servers11,601 Players32,197 Populated2,849 Fresh wipes 3 h67 Scan5 min
‹ All servers178.66.0.10:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 178.66.0.10:28015 checked 26d 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#13,894top 60%
Last wipe26d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k21 Sep24 Sep28 Sep1 Oct5 Oct8 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.1 daysbetween real wipes
on rhythm60%of its recent wipes
wipe-day peak5players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctWed 30 SepTue 29 Sep
02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 17:09 UTC FW26d ago 5 – running 4
Wed 30 Sep, 19:24 UTC27d ago 5 – 0.9 days 3
Tue 29 Sep, 16:50 UTC28d ago 5 – 1.1 days 0
Mon 28 Sep, 14:23 UTC29d ago 4 – 1.1 days 1
Sun 27 Sep, 13:22 UTC30d ago 5 – 1 days 2
Sat 26 Sep, 05:34 UTC31d ago 5 – 1.3 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 5 players on average. After the latest wipe, numbers topped out at 3 hours.

What wipe timing does TEST follow?

There is no next wipe to predict: TEST wipes at irregular times. 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 26 days 9 hours ago.

Lists and filters

How should you read the tags on TEST?

These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): The server runs game build 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TEST?

These Rust Metrics lists carry TEST: 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.

Occupancy

What position does TEST hold among Rust servers?

Player hours over seven days put TEST at #13,894, in the top 60% of all ranked servers.

How full does TEST get?

Status for TEST: offline. Last seen 26 days 7 hours ago.

Server

Which location does TEST run from?

No region comes from TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 178.66.0.10:28015.

What Rust version is TEST on?

Rust network protocol 2634 and build 166494 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.

How reliable is TEST, and is it online now?

Check: connection. TEST is offline at this moment. Last contact was 26 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 21 September 2026.

Settings and map

What settings and rules apply on TEST?

Reading the name gives no gather rate for TEST. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TEST?

The game generates a procedural map for TEST.

Join

How can you get onto TEST?

Press F1 in Rust and enter client.connect 178.66.0.10:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build The server runs game build 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.