DWG RG-S0027Server sheetchecked 11m ago
Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip
Online NA · us1 168.100.163.122:28010 checked 11m ago
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
Top 0.1% of all ranked servers, top 0.2% in NA, and #2 of the quad servers (top 0.2%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. The force wipe · high confidence
Coming wipes
- 6d 22hThu 5 Nov, 19:00 UTCFW
- 21d 0hThu 19 Nov, 20:58 UTC
- 34d 22hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 533, 4 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 20:58 UTC6d ago | 533 | – | running | 67 |
| Thu 1 Oct, 17:58 UTC FW28d ago | 791+26 queue | halved by day 12 | 21.1 days | 68 |
| Thu 24 Sep, 21:00 UTC34d ago | 425 | held half | 6.9 days | 35 |
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
Quick answers
Server data
What uptime is recorded for Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip, and is it up?
Right now, Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip is recorded as online. The uptime it reports puts the last restart at about 33 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
How does Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip perform, as measured?
30 server fps on average over the last 48 hours, and never under 30. Counted at its highest: 539,330 entities, buildings, deployables and the rest of the world included. Memory use peaked at 13,735 MB. What players feel as lag is low fps together with a climbing entity count.
What location is recorded for Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
The NA tag places Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip in North America, and its region code is us1. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 168.100.163.122:28010.
On which Rust version is Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip running?
The platform is Linux and the version is Rust network protocol 2635 and build 168909 on Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip. The same protocol is required for joining, and Steam updates your game to it.
Population
What does the population history show for Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
Current player count on Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip: 174, of 200 slots. The seven-day mean is 260 players; the peak over the same period is 533. Averaged over the last 48 hours, the player count is highest at 00:00 UTC: 300 players.
What rank has been recorded for Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip also measures #4 in North America on the same seven-day player-hour count, at #27 globally and in the top 0.1% of ranked servers. Ranked #2 among quad servers.
Wipe times
On Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip, what does the data show for wipe day?
The recent wipes averaged a busiest count of 583 players. 4 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 50% of its recent wipes. In the other cases the crowd was below half by day 12.
Which times and days are wipes plotted at on Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
every 4 weeks on Thursday at 20:58 UTC is how Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 6 days 23 hours ago. A wipe every month is the schedule its tags set out.
Map and rules
Which rules and settings are recorded for Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
2x gather is stated in the name of Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip. A group tops out at 4 players (quad). survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. Vanilla is the label it uses: facepunch's game, unaltered: rates, kits and rules are as shipped. VAC is on: that is Valve's anti-cheat.
What is the map for Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip runs a procedural map of size 4,500 with seed 1337, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The map is named as follows: discord.gg/atlasrust.
Tags
On Rust Graphs, which lists and filters contain Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
The Rust Graphs lists that carry Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip are: Servers with a 2x gather rate, Modded Rust servers and Rust server list: North America. It is returned by these filters on the server list: Region: North America; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Monthly; Last wipe: In the last week; Gather rate: 2x; Players now: At least 100; Average players: 200+ on average.
On Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip, what is meant by each tag?
The game's server browser reads these tags from Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip: gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): Slots: 200; ts4 (Group limit): The team limit is 4; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $rus1 (Region code): Region code: us1; ^m (Monthly): Facepunch's force wipe brings a monthly wipe; ^v (Vanilla): Facepunch's game, unaltered: rates, kits and rules are as shipped; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; modded (Modded): Plugins or settings change the game, so it is listed under Modded; NA (North America): The server browser lists it under North America. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Which operator runs Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip?
A atlasrust.us hostname is published by Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip, as it is by 5 other servers we track; the same operator most likely runs them.
Joining the server
How is Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip joined?
Connect with client.connect 168.100.163.122:28010: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://store.atlasrust.com/store/.
Server tags
Published as mp200,ptrak,$rus1,v2635,^m,^v,NA,gmvanilla,cs168909,ts4,^o^z,modded
Game
gmvanilla
mp200
ts4
v2635
cs168909
ptrak
$rus1
Wipe schedule
^m
Difficulty
^v
Mods and access
^o
^z
modded
Region
NA
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.
