RUST METRICSFlight deck · live data
Data live Servers11,805 Players82,372 Populated3,637 Fresh wipes 3 h283 Scan5 min
‹ All servers160.251.179.176:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_1633

Offline 160.251.179.176:28015 checked 25d 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,967top 71%
Last wipe49d 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 Sep24 Sep28 Sep3 Oct7 Oct11 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_1633 follow?

The rhythm of RustServer_1633'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. 49 days ago the current world was made.

Tag meanings

How should you read the tags on RustServer_1633?

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): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from RustServer_1633. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_1633 appear in Rust Metrics lists and filters?

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

Population

What position does RustServer_1633 hold among Rust servers?

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

What player count does RustServer_1633 carry?

Status for RustServer_1633: offline. Last seen 25 days 5 hours ago.

Server details

Where does RustServer_1633 sit?

No region comes from RustServer_1633. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 160.251.179.176:28015.

What Rust version is RustServer_1633 on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by RustServer_1633. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. RustServer_1633 is offline at this moment. Last contact was 25 days 5 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.

Settings and map

What rules does RustServer_1633 enforce, and what are its settings?

No gather rate appears in the name: RustServer_1633. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_1633 on?

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

How to join

How do you connect to RustServer_1633?

To join: start Rust, press F1 and type client.connect 160.251.179.176: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?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.