RUST METRICSFlight deck · live data
Data live Servers11,855 Players100,368 Populated3,884 Fresh wipes 3 h533 Scan5 min
‹ All servers160.251.235.82:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_4158

Offline 160.251.235.82:28015 checked 8d 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,400top 69%
Last wipe16d 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, measured since 19 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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 69% 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 gap18.4 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Mon 12 OctThu 24 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 20:32 UTC16d ago 1 – running 0
Thu 24 Sep, 10:00 UTC35d ago 2 halved by day 1 18.4 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 timing

What should you expect from wipe day on RustServer_4158?

The busiest point of its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 14 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.

When does RustServer_4158 wipe?

To tell the rhythm of RustServer_4158, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 16 days 23 hours ago.

Lists and filters

How should you read the tags on RustServer_4158?

These are the tags RustServer_4158 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): The server runs game build 167584; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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.

Which lists and filters on Rust Metrics show RustServer_4158?

On Rust Metrics, RustServer_4158 sits in these lists: 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.

Occupancy

Where does RustServer_4158 sit in the rankings?

Player hours over seven days put RustServer_4158 at #15,400, in the top 69% of all ranked servers.

What player count does RustServer_4158 carry?

RustServer_4158 is not responding; status offline, last seen 8 days 22 hours ago.

Server

Which location does RustServer_4158 run from?

Reading: location. RustServer_4158 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 160.251.235.82:28015.

What Rust version is RustServer_4158 on?

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

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

Reading: offline. RustServer_4158 last answered 8 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Rules and settings

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

Check: gather rate. The name RustServer_4158 does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_4158 on?

From seed 22703, the game generates the procedural map on RustServer_4158. 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

How do you connect to RustServer_4158?

To join: start Rust, press F1 and type client.connect 160.251.235.82:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167584
Build The server runs game build 167584.
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.