RUST METRICSFlight deck · live data
Data live Servers11,635 Players30,176 Populated2,756 Fresh wipes 3 h70 Scan5 min
‹ All servers160.251.236.71:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_17958

Offline 160.251.236.71:28015 checked 23d 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,962top 71%
Last wipe25d 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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct6 Oct7 Oct9 Oct10 Oct12 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

What wipe timing does RustServer_17958 follow?

Its rhythm cannot be told from the wipes of RustServer_17958 on record: there are too few. 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 in play was created 25 days 3 hours ago.

Tag meanings

Which tags does RustServer_17958 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): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from RustServer_17958. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_17958 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustServer_17958: 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_17958 sit in the rankings?

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

What player count does RustServer_17958 carry?

Reading for RustServer_17958: offline at this moment; last seen 23 days 15 hours ago.

Server

Which location does RustServer_17958 run from?

No region tag on RustServer_17958. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 160.251.236.71:28015.

What Rust version is RustServer_17958 on?

Rust network protocol 2634 and build 166652 on Linux is the build RustServer_17958 runs. Matching protocol is required to join. Let Steam update your game.

How reliable is RustServer_17958, and is it online now?

Reading: offline. RustServer_17958 last answered 23 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 4 October 2026.

Rules and settings

What settings and rules apply on RustServer_17958?

Check: gather rate. The name RustServer_17958 does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is RustServer_17958 on?

From seed 26426, the game generates the procedural map on RustServer_17958. Its size is 3,000. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join RustServer_17958?

Press F1 in Rust and enter client.connect 160.251.236.71: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?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
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.