RUST METRICSFlight deck · live data
Data live Servers11,737 Players52,204 Populated3,347 Fresh wipes 3 h125 Scan5 min
‹ All servers91.235.15.164:28015
Offline Full Queue Fresh wipe Wipe due No query

atomdev001

Offline 91.235.15.164:28015 checked 5d 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 avg7-day peak
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 average1peak 1
Rank#11,550top 52%
Last wipe5d 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
15k10k15k20k19 Oct21 Oct23 Oct24 Oct26 Oct28 Oct

Top 52% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 19:34 UTC5d ago 1 – 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

Reset cycle

What should you expect from wipe day on atomdev001?

The busiest point of its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

How often does atomdev001 wipe, and when?

To tell the rhythm of atomdev001, 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. 5 days 3 hours ago the current world was made.

Tags

How should you read the tags on atomdev001?

These are the tags atomdev001 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is 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 atomdev001?

On Rust Metrics, atomdev001 sits in these lists: 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; Last wipe: In the last week.

Population

Where does atomdev001 sit in the rankings?

Ranking for atomdev001: #11,550 on seven-day player hours, top 52% of all ranked servers.

What player count does atomdev001 carry?

atomdev001 is not responding; status offline, last seen 5 days 2 hours ago. Check: players over seven days. Average 1, peak 1.

Operator and location

What location is atomdev001 hosted in?

No region tag on atomdev001. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 91.235.15.164:28015.

What Rust version is atomdev001 on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by atomdev001. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. atomdev001 is offline at this moment. Last contact was 5 days 2 hours ago. Uptime for the last 7 full days: 3 of 168 hours, or 2%. Reading: first seen 19 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on atomdev001?

No gather rate appears in the name: atomdev001. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is atomdev001 on?

The game generates a procedural map for atomdev001.

How to join

How do you connect to atomdev001?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.