Station US-15977 · no signal
Atlas Hub Testing
Offline EU · us1 168.100.161.3:28210 checked 22d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,977
- top 71% · #2523 in EU
- Last wipe
- 479d ago
- weekly schedule
- Next wipe
- 3d 6h
- Sun 1 Nov, 12:33 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
Players
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers, top 88% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Sunday 1 November, 12:33 UTC, in 3d 6h. Weekly: 7 days after its last wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which settings and rules apply on Atlas Hub Testing?
The name of Atlas Hub Testing gives no gather rate. 30 players is the most a group can hold. It plays in minigames & battle royale mode, battle royale, arenas, parkour and Bedwars. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on Atlas Hub Testing right now?
No players are recorded on Atlas Hub Testing at this moment; it is offline, and the last sighting was 22 days 8 hours ago.
How does Atlas Hub Testing rank against other Rust servers?
The last seven days of player hours place Atlas Hub Testing at #15,977, in the top 71% of all ranked servers and #2,523 in Europe.
Server details
How reliably does Atlas Hub Testing stay online?
Atlas Hub Testing is down at the moment; the last recorded contact was 22 days 8 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Where in the world is Atlas Hub Testing hosted?
Its region code is us1, and Atlas Hub Testing lists itself in Europe with the EU tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 168.100.161.3:28210.
Which Rust version is Atlas Hub Testing running?
Rust network protocol 2633 and build 125476 on Linux is what Atlas Hub Testing runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
How often does Atlas Hub Testing wipe, and on which days?
From weekly: 7 days after its last wipe the next wipe of Atlas Hub Testing is estimated. Sunday 1 November at 12:33 UTC is when its next wipe is due. The present world dates from 479 days 17 hours. Its tags state a weekly wipe schedule.
Lists and tags
What do the server tags on Atlas Hub Testing mean?
These are the tags Atlas Hub Testing publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts30 (Group limit): The team limit is 30; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs125476 (Build): Game build: 125476; ptrak (Networking): Network layer: RakNet, the standard for Rust; $rus1 (Region code): The region code for this server is us1; ^w (Weekly): The server wipes every week; ^c (Creative): Build freely in sandbox mode, with no gathering; ^e (Minigames): This server hosts minigames: arenas, Bedwars, parkour and more; ^d (Combat training): You get loot handed to you to practise aim and PvP; ^i (Battlefield): Kits and high rates drive fast PvP; ^j (Battle royale): The zone closes in while you loot and fight; ^k (Build server): You can design and practise bases; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; modded (Modded): The game is changed by plugins or settings, placing it under Modded; EU (Europe): Europe is the region it's listed under in the browser; rustmaps (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Atlas Hub Testing appear?
The Rust Server Trends lists that take in Atlas Hub Testing are: EU Rust servers, Modded Rust servers, tracked live, Rust aim training servers, live, Rust battlefield servers, Rust build and creative servers, live and Rust creative servers. You will find it under these filters on the server list: Region: Europe; Type: Modded; Server tag: Weekly ^w, Creative ^c, Minigames ^e, Combat training ^d, Battlefield ^i, Battle royale ^j, Build server ^k, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
How to join
How do you connect to Atlas Hub Testing?
You can connect by pressing F1 in Rust and typing client.connect 168.100.161.3:28210 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.