RUST METRICSFlight deck · live data
Data live Servers11,892 Players103,409 Populated3,969 Fresh wipes 3 h496 Scan5 min
‹ All servers160.251.233.89:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_20281

Offline 160.251.233.89: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,437top 69%
Last wipe10d 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 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 Sep28 Sep5 Oct13 Oct20 Oct28 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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 05:13 UTC10d ago 0 – running 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 schedule

What happens on RustServer_20281 when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does RustServer_20281 wipe, and when?

The rhythm of RustServer_20281's wipes cannot be told yet: too few 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 in play was created 10 days 14 hours ago.

Tags

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

These are the tags RustServer_20281 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $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_20281 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring RustServer_20281: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does RustServer_20281 hold among Rust servers?

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

What is the population on RustServer_20281?

RustServer_20281 is not responding; status offline, last seen 8 days 3 hours ago.

Operator and location

Which location does RustServer_20281 run from?

No region comes from RustServer_20281. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 160.251.233.89:28015.

What Rust version is RustServer_20281 on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by RustServer_20281. Check: protocol. To join, your game must match; Steam handles the update.

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

RustServer_20281 reports offline. The last reading came 8 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

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

Check: gather rate. The name RustServer_20281 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is RustServer_20281 on?

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

Join

What do you do to join RustServer_20281?

Check: join. Open Rust, press F1, then enter client.connect 160.251.233.89: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?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.