RUST METRICSFlight deck · live data
Data live Servers11,648 Players32,263 Populated2,789 Fresh wipes 3 h72 Scan5 min
‹ All servers80.47.3.169:20012
Offline Full Queue Fresh wipe Wipe due No query

A_Rust_Server

Offline 80.47.3.169:20012 checked 21d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

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,892top 72%
Last wipe25d 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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct5 Oct7 Oct10 Oct12 Oct14 Oct

Top 72% 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 peak0players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 10:34 UTC25d ago 0 – running 0

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 timing

What happens on A_Rust_Server when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does A_Rust_Server wipe, and when?

The rhythm of A_Rust_Server's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 25 days 18 hours ago.

Tag meanings

How should you read the tags on A_Rust_Server?

These are the tags A_Rust_Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): 40 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Build 166652; 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 A_Rust_Server?

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

Occupancy

Where does A_Rust_Server sit in the rankings?

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

How full does A_Rust_Server get?

Reading for A_Rust_Server: offline at this moment; last seen 21 days 8 hours ago.

Operator and location

Which location does A_Rust_Server run from?

No region comes from A_Rust_Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 80.47.3.169:20012.

What Rust version is A_Rust_Server on?

Reading: A_Rust_Server, Rust network protocol 2634 and build 166652, Linux. Matching protocol is required to join. Let Steam update your game.

What is the uptime on A_Rust_Server, and is it online?

Reading: offline. A_Rust_Server last answered 21 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 3 October 2026.

Map and rules

What settings and rules apply on A_Rust_Server?

Check: gather rate. The name A_Rust_Server does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. 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.

What map is A_Rust_Server on?

From seed 1, the game generates the procedural map on A_Rust_Server. Its size is 3,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join A_Rust_Server?

Check: join. Open Rust, press F1, then enter client.connect 80.47.3.169:20012. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://egnetwork.ru/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players 40 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Build 166652.
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.