auto-dump
Offline 34.72.24.78:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
50% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 262/300
- 22/250
- 16/250
- 169/200
- 81/200
- 20/100
Quick answers
from the figures on this pageWipe timing
How often does auto-dump wipe, and when?
Its rhythm cannot be told from the wipes of auto-dump on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 45 days 1 hours ago.
Tag meanings
How should you read the tags on auto-dump?
Tags published by auto-dump, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): The server runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does auto-dump appear in Rust Metrics lists and filters?
Rust Metrics lists featuring auto-dump: 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
What is the population on auto-dump?
auto-dump is not responding; status offline, last seen 44 days 16 hours ago.
Operator and location
What location is auto-dump hosted in?
No region tag on auto-dump. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 34.72.24.78:28015.
What Rust version is auto-dump on?
Version check: Rust network protocol 2633 and build 163794 on Windows, run by auto-dump. To get in, your game needs the same protocol; Steam applies the update.
How reliable is auto-dump, and is it online now?
Reading: offline. auto-dump last answered 44 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
How is auto-dump configured, and what rules are in force?
Check: gather rate. The name auto-dump does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.
Which map is live on auto-dump?
Check: map. Procedural, generated by the game, on auto-dump.
How to join
How do you connect to auto-dump?
Check: join. Open Rust, press F1, then enter client.connect 34.72.24.78:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.