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

RustServer_3991

Offline 160.251.170.78:28015 checked 27d 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#16,728top 70%
Last wipe53d 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 Sep23 Sep27 Sep30 Sep4 Oct7 Oct

Top 70% 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 schedule

How often does RustServer_3991 wipe, and when?

The rhythm of RustServer_3991'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 it runs now was made 53 days ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 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): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from RustServer_3991. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_3991 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring RustServer_3991: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does RustServer_3991 sit in the rankings?

Player hours over seven days put RustServer_3991 at #16,728, in the top 70% of all ranked servers.

How full does RustServer_3991 get?

RustServer_3991 is not responding; status offline, last seen 27 days 23 hours ago.

Operator and location

What location is RustServer_3991 hosted in?

No region tag on RustServer_3991. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 160.251.170.78:28015.

What Rust version is RustServer_3991 on?

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

Is RustServer_3991 up, and how often does it stay up?

Reading: offline. RustServer_3991 last answered 27 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

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

No gather rate appears in the name: RustServer_3991. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on RustServer_3991?

Check: map. Procedural, size 3,500, seed 1746005783, generated by the game on RustServer_3991. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to RustServer_3991?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 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 Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.