RUST METRICSFlight deck · live data
Data live Servers11,878 Players98,796 Populated3,935 Fresh wipes 3 h404 Scan5 min
‹ All servers133.88.123.22:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_14097

Offline 133.88.123.22:28015 checked 20d 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,831top 72%
Last wipe37d 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 22 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
15k10k15k20k22 Sep27 Sep1 Oct6 Oct10 Oct15 Oct

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

Reset cycle

How often does RustServer_14097 wipe, and when?

Its rhythm cannot be told from the wipes of RustServer_14097 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 37 days 4 hours ago the current world was made.

Tag meanings

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

These are the tags RustServer_14097 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): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none 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_14097?

These Rust Metrics lists carry RustServer_14097: 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.

Occupancy

What position does RustServer_14097 hold among Rust servers?

Ranking for RustServer_14097: #15,831 on seven-day player hours, top 72% of all ranked servers.

What player count does RustServer_14097 carry?

Reading for RustServer_14097: offline at this moment; last seen 20 days 21 hours ago.

Server details

Which location does RustServer_14097 run from?

No region tag on RustServer_14097. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 133.88.123.22:28015.

What Rust version is RustServer_14097 on?

Rust network protocol 2633 and build 165217 on Linux is the build RustServer_14097 runs. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. RustServer_14097 last answered 20 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 22 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on RustServer_14097?

No gather rate appears in the name: RustServer_14097. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on RustServer_14097?

Size 3,000 and seed 27806: the game generates the procedural map on RustServer_14097 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How can you get onto RustServer_14097?

Press F1 in Rust and enter client.connect 133.88.123.22: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?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.