RUST METRICSFlight deck · live data
Data live Servers11,865 Players95,534 Populated3,881 Fresh wipes 3 h381 Scan5 min
‹ All servers160.251.253.50:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_17115

Offline 160.251.253.50:28015 checked 36d ago

COM 1 · connect

Server instruments

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

Players now

8% 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#10,009top 46%
Last wipe40d 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 18 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

Top 46% 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

How often does RustServer_17115 wipe, and when?

The rhythm of RustServer_17115's wipes cannot be told yet: too few are on record. 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 40 days 23 hours ago.

Tag meanings

How should you read the tags on RustServer_17115?

These are the tags RustServer_17115 publishes, and the server browser reads them: 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; cs164530 (Build): Build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_17115 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring RustServer_17115: 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_17115 sit in the rankings?

Ranking for RustServer_17115: #10,009 on seven-day player hours, top 46% of all ranked servers.

What is the population on RustServer_17115?

Reading for RustServer_17115: offline at this moment; last seen 36 days 1 hours ago.

Operator and location

Where does RustServer_17115 sit?

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

What Rust version is RustServer_17115 on?

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

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

RustServer_17115 reports offline. The last reading came 36 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 September 2026, recorded by Rust Metrics.

Settings and map

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

No gather rate appears in the name: RustServer_17115. The group cap is 8 players, which is the default in the game. 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.

Which map is live on RustServer_17115?

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

Join

How do you connect to RustServer_17115?

Check: join. Open Rust, press F1, then enter client.connect 160.251.253.50: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,cs164530,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.
cs164530
Build Build 164530.
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.