RUST METRICSFlight deck · live data
Data live Servers11,841 Players73,926 Populated3,704 Fresh wipes 3 h221 Scan5 min
‹ All servers163.44.121.230:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_3537

Offline 163.44.121.230:28015 checked 27d 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#16,036top 69%
Last wipe48d 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 Sep27 Sep1 Oct4 Oct8 Oct

Top 69% 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 schedule

How often does RustServer_3537 wipe, and when?

Its rhythm cannot be told from the wipes of RustServer_3537 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 48 days 16 hours ago.

Tags

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

These are the tags RustServer_3537 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; 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. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show RustServer_3537?

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

What position does RustServer_3537 hold among Rust servers?

Player hours over seven days put RustServer_3537 at #16,036, in the top 69% of all ranked servers.

What is the population on RustServer_3537?

Status for RustServer_3537: offline. Last seen 27 days 16 hours ago.

Operator and location

Which location does RustServer_3537 run from?

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

What Rust version is RustServer_3537 on?

Reading: RustServer_3537, Rust network protocol 2633 and build 165217, Linux. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. RustServer_3537 last answered 27 days 16 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.

Map and rules

What settings and rules apply on RustServer_3537?

No gather rate appears in the name: RustServer_3537. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_3537 on?

From seed 17445, the game generates the procedural map on RustServer_3537. Its size is 3,000. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How do you connect to RustServer_3537?

Check: join. Open Rust, press F1, then enter client.connect 163.44.121.230: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,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
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.