Online 23.109.125.138:27117 checked 5m ago
high risk solo/duo only
Connect
srv = rust.server("23.109.125.138:27118")
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 22 Oct. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
4000 · seed 50000
- map
- Procedural Map
- size
- 4000
- seed
- 50000
Server
srv.info()- address
- 23.109.125.138:27117
- region
- –
- max players
- 75
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 03:20 UTC
- hostname
- –
- first seen
- 22 Oct 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 | 31/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 0/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 12/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 31/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 45/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does high risk solo/duo only rank?
Player hours over seven days put high risk solo/duo only at #15,270, in the top 69% of the ranked set.
What population does high risk solo/duo only carry?
The sample now reads 0 players for high risk solo/duo only, out of 75 slots. Over the last seven days it averaged 0 players.
Server facts
How well does high risk solo/duo only perform?
Server fps over the last 48 hours averages 176; the floor is 110. Buildings, deployables and all else in the world took the count as high as 94,363 entities. Memory peaked at 4,688 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on high risk solo/duo only?
The build is Rust network protocol 2635 and build 167781 on Linux, run by high risk solo/duo only. Joining needs the same protocol on your game; Steam handles the update.
How reliable is high risk solo/duo only, and is it up?
The current sample puts high risk solo/duo only online. The uptime it reports puts the last restart about 3 days 17 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 22 October 2026.
Which location does high risk solo/duo only run from?
For high risk solo/duo only, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 23.109.125.138:27117 is its address.
Rules, settings, map
Which rules apply on high risk solo/duo only, and what settings?
No gather rate appears in the name: high risk solo/duo only. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on high risk solo/duo only?
The game generates the map on high risk solo/duo only: procedural, size 4,000, seed 50000. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does high risk solo/duo only wipe?
Too few wipes are on record for high risk solo/duo only to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 26 days 1 hours ago.
Tags and filters
Which Rust Data filters and lists contain high risk solo/duo only?
On Rust Data, high risk solo/duo only appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on high risk solo/duo only?
These tags are published by high risk solo/duo only and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): Slot count: 75; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 high risk solo/duo only?
Enter client.connect 23.109.125.138:27117 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.