Offline 125.236.230.198:28115 checked 33d ago
Local AUX1 Test Server
Connect
srv = rust.server("125.236.230.198:28117")
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 25 Sep, 05:33 UTC34d ago | 1 | NaN | running | 1 |
| 1 | Tue 22 Sep, 05:56 UTC37d ago | 1 | held half | 3 days | 1 |
# 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
- 125.236.230.198:28115
- region
- – · au1
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Sep 2026, 05:33 UTC
- hostname
- –
- first seen
- 19 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 · 151 on average | 103/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 155/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 63/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 195/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
What position does Local AUX1 Test Server take in the server rankings?
Player hours over seven days put Local AUX1 Test Server at #16,546, in the top 71% of the ranked set.
What population does Local AUX1 Test Server carry?
Offline now for Local AUX1 Test Server, with the last sample 33 days 18 hours ago.
About the server
What Rust version does Local AUX1 Test Server run?
The build is Rust network protocol 2633 and build 165211 on Windows, run by Local AUX1 Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local AUX1 Test Server, and is it up?
The latest sample has Local AUX1 Test Server offline, with a last sighting 33 days 18 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 19 September 2026.
Which location does Local AUX1 Test Server run from?
There is no region published for Local AUX1 Test Server, and the region code is au1. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 125.236.230.198:28115.
Rules, settings, map
Which settings and rules does Local AUX1 Test Server run?
The name Local AUX1 Test Server carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
Which map has Local AUX1 Test Server loaded?
The game generates its map: procedural, on Local AUX1 Test Server.
Wipe schedule
When does Local AUX1 Test Server wipe, and on what schedule?
Too few wipes are on record for Local AUX1 Test Server to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 34 days 14 hours ago.
On Local AUX1 Test Server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.
Lists and tags
Which Rust Data filters and lists contain Local AUX1 Test Server?
These Rust Data lists include Local AUX1 Test Server: 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.
Which meanings do the tags on Local AUX1 Test Server hold?
The game's server browser reads these tags from Local AUX1 Test Server: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165211 (Build): Build number: 165211; ptrak (Networking): The network layer is RakNet, standard for the game; $rau1 (Region code): au1 is the region code recorded; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Local AUX1 Test Server?
Enter client.connect 125.236.230.198:28115 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.