RUST METRICSFlight deck · live data
Data live Servers11,735 Players53,534 Populated3,365 Fresh wipes 3 h127 Scan5 min
‹ All servers82.230.152.47:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST - RustMaps 3500 Monthly

Offline 82.230.152.47:28015 checked 28d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#14,386top 60%
Last wipe30d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Sep27 Sep30 Sep2 Oct5 Oct7 Oct

Top 60% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 16:51 UTC30d ago 1 – running 1

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 happens on TEST - RustMaps 3500 Monthly when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 2 hours.

What wipe timing does TEST - RustMaps 3500 Monthly follow?

Its rhythm cannot be told from the wipes of TEST - RustMaps 3500 Monthly on record: there are too few. 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 30 days 4 hours ago.

Tag meanings

Which tags does TEST - RustMaps 3500 Monthly carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; 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): The region field is empty from TEST - RustMaps 3500 Monthly. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does TEST - RustMaps 3500 Monthly appear in Rust Metrics lists and filters?

Rust Metrics lists featuring TEST - RustMaps 3500 Monthly: 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.

Population

Where does TEST - RustMaps 3500 Monthly sit in the rankings?

Player hours over seven days put TEST - RustMaps 3500 Monthly at #14,386, in the top 60% of all ranked servers.

What player count does TEST - RustMaps 3500 Monthly carry?

Status for TEST - RustMaps 3500 Monthly: offline. Last seen 28 days 5 hours ago.

Server details

Where does TEST - RustMaps 3500 Monthly sit?

Reading: location. TEST - RustMaps 3500 Monthly gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 82.230.152.47:28015.

What Rust version is TEST - RustMaps 3500 Monthly on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by TEST - RustMaps 3500 Monthly. Matching protocol is required to join. Let Steam update your game.

How reliable is TEST - RustMaps 3500 Monthly, and is it online now?

Reading: offline. TEST - RustMaps 3500 Monthly last answered 28 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 25 September 2026, recorded by Rust Metrics.

Rules and settings

How is TEST - RustMaps 3500 Monthly configured, and what rules are in force?

No gather rate appears in the name: TEST - RustMaps 3500 Monthly. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Join

What do you do to join TEST - RustMaps 3500 Monthly?

To join: start Rust, press F1 and type client.connect 82.230.152.47:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
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 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.