Offline 102.223.56.95:28015 checked 26d ago
Atomic Rust R4 Test
Connect
srv = rust.server("102.223.56.95:28017")
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. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 21:12 UTC FW27d ago | 0 | NaN | 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 102.223.56.95:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:12 UTC
- hostname
- –
- first seen
- 30 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 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 85/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 78/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 67/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 20/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Atomic Rust R4 Test rank?
Player hours over seven days put Atomic Rust R4 Test at #15,973, in the top 70% of the ranked set.
What population does Atomic Rust R4 Test carry?
Atomic Rust R4 Test returns no live count at this refresh, having last been seen 26 days 1 hours ago.
About the server
Which Rust version is Atomic Rust R4 Test on?
The build is Rust network protocol 2634 and build 166494 on Windows, run by Atomic Rust R4 Test. Steam updates your game for you, but the protocol must match to join.
How reliable is Atomic Rust R4 Test, and is it up?
Offline now for Atomic Rust R4 Test, last seen 26 days 1 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 30 September 2026.
In which location is Atomic Rust R4 Test hosted?
No region is published by Atomic Rust R4 Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 102.223.56.95:28015 is its address.
Rules, settings, map
Which rules apply on Atomic Rust R4 Test, and what settings?
The name Atomic Rust R4 Test carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has Atomic Rust R4 Test loaded?
Atomic Rust R4 Test runs a procedural map, which the game generates.
Wipe schedule
On what schedule does Atomic Rust R4 Test wipe?
A single wipe each month, the force wipe, is all Atomic Rust R4 Test does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 27 days 1 hours ago.
On Atomic Rust R4 Test, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does Atomic Rust R4 Test appear among Rust Data lists and filters?
These Rust Data lists include Atomic Rust R4 Test: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Atomic Rust R4 Test?
The game's server browser reads these tags from Atomic Rust R4 Test: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Atomic Rust R4 Test?
In Rust, F1 opens the console: type client.connect 102.223.56.95:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.