Offline 216.39.240.33:28210 checked 30d ago
Atlas Hub US Testing
Connect
srv = rust.server("216.39.240.33:28215")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Next wipe Sunday 1 November, 12:33 UTC, in 2d 15h. # Weekly: 7 days after its last wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Hello World
- size
- –
- seed
- –
Server
srv.info()- address
- 216.39.240.33:28210
- region
- – · us1
- max players
- 100
- group limit
- 30 max
- wipe schedule
- weekly
- last wipe
- 6 Jul 2025, 12:33 UTC
- hostname
- –
- first seen
- 26 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [NA] Echo Rust - Sandbox | NA · groups of 32+ · weekly · 2 on average | 3/50 |
| 1 | [NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | NA · groups of 8+ · 91 on average | 128/999 |
| 2 | Intoxicated US Sandbox - Creative | Build | Noclip | NA · groups of 8+ · 13 on average | 22/150 |
| 3 | RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGrade | NA · groups of 100+ · monthly · 7 on average | 5/200 |
| 4 | Together We Rust | Build Server | NA · groups of 8+ · 2 on average | 3/125 |
| 5 | Builders Like Us | NA · groups of 32+ · monthly · 2 on average | 0/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Atlas Hub US Testing rank?
Player hours over seven days put Atlas Hub US Testing at #16,859, in the top 71% of the ranked set.
How many players does Atlas Hub US Testing hold at once?
The current row shows Atlas Hub US Testing offline; the last response was 30 days 1 hours ago.
Server data
What Rust version does Atlas Hub US Testing run?
Rust network protocol 2633 and build 125476 on Linux is what Atlas Hub US Testing runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Atlas Hub US Testing, and is it up?
Atlas Hub US Testing is offline at this refresh; the last response came 30 days 1 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 26 September 2026.
In which location is Atlas Hub US Testing hosted?
No region tag is published by Atlas Hub US Testing, though its name points to North America; the region code is us1. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 216.39.240.33:28210.
Map and rules
What rules and settings are recorded for Atlas Hub US Testing?
No gather rate appears in the name: Atlas Hub US Testing. The cap on a group is 30 players. Recorded as minigames & battle royale, battle royale, arenas, parkour, Bedwars. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Wipes and dates
When does Atlas Hub US Testing wipe, and how often?
Expect an estimate: Atlas Hub US Testing's next wipe is projected from weekly: 7 days after its last wipe. The schedule puts the next wipe on Sunday 1 November at 12:33 UTC. The world it runs now was generated 480 days 8 hours ago. A weekly wipe schedule is published in its tags.
Lists and tags
Which lists on Rust Data hold Atlas Hub US Testing, and which filters?
On Rust Data, Atlas Hub US Testing appears in these lists: Modded Rust servers, Rust aim training servers, Rust battlefield servers, Servers with build or creative tags, Rust creative servers, listed and North America Rust servers. It appears under these filters on the server list: Region: North America; 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.
Which meanings do the tags on Atlas Hub US Testing hold?
The game's server browser reads these tags from Atlas Hub US Testing: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts30 (Group limit): No team may exceed 30; v2633 (Protocol): To join, your game must run protocol 2633; cs125476 (Build): Recorded game build: 125476; ptrak (Networking): Standard network layer for Rust: RakNet; $rus1 (Region code): Region code in the data: us1; ^w (Weekly): The interval is one week; ^c (Creative): Creative sandbox: gathering is off, building is open; ^e (Minigames): Runs minigames such as arenas, Bedwars and parkour; ^d (Combat training): Loot is handed to you for aim and PvP practice; ^i (Battlefield): High rates and kits, for fast PvP; ^j (Battle royale): Fight as the zone closes in, after looting; ^k (Build server): A place to design and practise bases; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; US (Custom tag): A plugin or the owner added this; standard Rust does not define it; rustmaps (Custom tag): A plugin or the owner added this; standard Rust does not define it. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join Atlas Hub US Testing?
In Rust, F1 opens the console: type client.connect 216.39.240.33:28210. Launch Rust on this page does the same by opening the game through Steam and connecting.