RUST METRICSFlight deck · live data
Data live Servers11,801 Players78,222 Populated3,772 Fresh wipes 3 h109 Scan5 min
‹ All servers133.117.72.86:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_20948

Offline 133.117.72.86:28015 checked 26d 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,948top 70%
Last wipe46d 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 Sep1 Oct5 Oct9 Oct

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

What wipe timing does RustServer_20948 follow?

To tell the rhythm of RustServer_20948, too few of its wipes are on record. 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 46 days 22 hours ago.

Tags

How should you read the tags on RustServer_20948?

These are the tags RustServer_20948 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RustServer_20948 appear in Rust Metrics lists and filters?

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

Where does RustServer_20948 sit in the rankings?

Ranking for RustServer_20948: #15,948 on seven-day player hours, top 70% of all ranked servers.

How full does RustServer_20948 get?

Reading for RustServer_20948: offline at this moment; last seen 26 days ago.

Server

Where does RustServer_20948 sit?

Reading: location. RustServer_20948 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 133.117.72.86:28015.

What Rust version is RustServer_20948 on?

Rust network protocol 2633 and build 165217 on Linux is the build RustServer_20948 runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. RustServer_20948 last answered 26 days 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.

Rules and settings

What settings and rules apply on RustServer_20948?

Check: gather rate. The name RustServer_20948 does not state one. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on RustServer_20948?

Check: map. Procedural, size 3,000, seed 17848, generated by the game on RustServer_20948. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

What do you do to join RustServer_20948?

Check: join. Open Rust, press F1, then enter client.connect 133.117.72.86: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 Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Game build reading: 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.