RUST METRICSFlight deck · live data
Data live Servers11,658 Players48,164 Populated3,140 Fresh wipes 3 h112 Scan5 min
‹ All servers160.251.185.221:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_18978

Offline 160.251.185.221:28015 checked 15d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,382top 71%
Last wipe47d agono schedule published
Next wipe–no wipe 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, measured since 17 Sep. 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 Sep26 Sep2 Oct8 Oct14 Oct20 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

When does RustServer_18978 wipe?

Its rhythm cannot be told from the wipes of RustServer_18978 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. The world it runs now was made 47 days 11 hours ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from RustServer_18978. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does RustServer_18978 appear in Rust Metrics lists and filters?

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

Occupancy

Where does RustServer_18978 sit in the rankings?

Player hours over seven days put RustServer_18978 at #15,382, in the top 71% of all ranked servers.

How full does RustServer_18978 get?

Status for RustServer_18978: offline. Last seen 15 days 23 hours ago.

Operator and location

Where does RustServer_18978 sit?

No region comes from RustServer_18978. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 160.251.185.221:28015.

What Rust version is RustServer_18978 on?

Rust network protocol 2633 and build 165217 on Linux is the build RustServer_18978 runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. RustServer_18978 is offline at this moment. Last contact was 15 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

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

Check: gather rate. The name RustServer_18978 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. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on RustServer_18978?

From seed 25593, the game generates the procedural map on RustServer_18978. Its size is 3,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join RustServer_18978?

Press F1 in Rust and enter client.connect 160.251.185.221: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 mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.