RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h14 Scan5 min
‹ All servers47.187.141.239:28015
Offline Full Queue Fresh wipe Wipe due No query

Managed file proof 20260918042502

Offline 47.187.141.239:28015 checked 40d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,478top 70%
Last wipe40d 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. 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

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

Wipe schedule

When does Managed file proof 20260918042502 wipe?

To tell the rhythm of Managed file proof 20260918042502, 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. 40 days 15 hours ago the current world was made.

Lists and filters

How should you read the tags on Managed file proof 20260918042502?

Tags published by Managed file proof 20260918042502, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Managed file proof 20260918042502 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Managed file proof 20260918042502: 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.

Player count

Where does Managed file proof 20260918042502 sit in the rankings?

Ranking for Managed file proof 20260918042502: #15,478 on seven-day player hours, top 70% of all ranked servers.

What player count does Managed file proof 20260918042502 carry?

Managed file proof 20260918042502 is not responding; status offline, last seen 40 days 14 hours ago.

Server details

What location is Managed file proof 20260918042502 hosted in?

No region tag on Managed file proof 20260918042502. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 47.187.141.239:28015.

What Rust version is Managed file proof 20260918042502 on?

Rust network protocol 2633 and build 164530 on Linux is the build Managed file proof 20260918042502 runs. Check: protocol. To join, your game must match; Steam handles the update.

Is Managed file proof 20260918042502 up, and how often does it stay up?

Check: connection. Managed file proof 20260918042502 is offline at this moment. Last contact was 40 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 18 September 2026.

Map and rules

What settings and rules apply on Managed file proof 20260918042502?

No gather rate appears in the name: Managed file proof 20260918042502. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is Managed file proof 20260918042502 on?

Check: map. Procedural, generated by the game, on Managed file proof 20260918042502.

Connection

What do you do to join Managed file proof 20260918042502?

Check: join. Open Rust, press F1, then enter client.connect 47.187.141.239:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Build 164530.
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.