RUST METRICSFlight deck · live data
Data live Servers11,830 Players81,821 Populated3,745 Fresh wipes 3 h270 Scan5 min
‹ All servers78.177.143.148:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 78.177.143.148:28015 checked 29d 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,427top 60%
Last wipe30d 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
15k10k15k20k20 Sep23 Sep27 Sep30 Sep4 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.

usual gap14 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 29 SepTue 15 Sep
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
Tue 29 Sep, 09:28 UTC30d ago 1 – running 1
Tue 15 Sep, 09:56 UTC44d ago 1 halved by day 1 14 days 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 should you expect from wipe day on TEST?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 1 it fell below half when it didn't.

What wipe timing does TEST follow?

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 30 days 5 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): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. 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?

Rust Metrics lists featuring 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.

Player count

Where does TEST sit in the rankings?

Ranking for TEST: #14,427 on seven-day player hours, top 60% of all ranked servers.

How full does TEST get?

Status for TEST: offline. Last seen 29 days 1 hours ago.

Operator and location

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 78.177.143.148:28015.

What Rust version is TEST on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is TEST, and is it online now?

Check: connection. TEST is offline at this moment. Last contact was 29 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on TEST?

Check: gather rate. The name TEST does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TEST?

The game generates a procedural map for TEST.

Join

What do you do to join TEST?

Check: join. Open Rust, press F1, then enter client.connect 78.177.143.148: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 Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
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.