Offline 109.235.49.132:28115 checked 3d ago
Combat isolated acceptance
Connect
srv = rust.server("109.235.49.132: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 68% 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 109.235.49.132:28115
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 15:10 UTC
- hostname
- –
- first seen
- 26 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 · 150 on average | 61/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 · 119 on average | 107/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 36/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 114/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Population data
How does Combat isolated acceptance compare in the rankings?
Player hours over seven days put Combat isolated acceptance at #15,268, in the top 68% of the ranked set.
What population does Combat isolated acceptance carry?
Offline now for Combat isolated acceptance, with the last sample 3 days 2 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is Combat isolated acceptance on?
Version Rust network protocol 2632 and build 161125 on Windows is reported by Combat isolated acceptance. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Combat isolated acceptance, and is it up?
The latest sample has Combat isolated acceptance offline, with a last sighting 3 days 2 hours ago. 0 of 48 hours up over the last 2 full days, or 0%. Its earliest recorded date in Rust Data is 26 October 2026.
In which location is Combat isolated acceptance hosted?
There is no region published for Combat isolated acceptance. 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 109.235.49.132:28115.
Settings and map
Which rules apply on Combat isolated acceptance, and what settings?
No gather rate appears in the name: Combat isolated acceptance. Eight players per group: that is the game's default, and it applies here. Recorded as survival, 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. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Combat isolated acceptance selected?
The game generates its map: procedural, on Combat isolated acceptance.
Wipes and dates
When does Combat isolated acceptance wipe, and on what schedule?
A rhythm cannot be read from the wipes of Combat isolated acceptance on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 7 days 6 hours ago.
Tags and filters
Where does Combat isolated acceptance appear among Rust Data lists and filters?
On Rust Data, Combat isolated acceptance 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; Last wipe: In the last 2 weeks.
How should you read the server tags on Combat isolated acceptance?
Read by the game's server browser, the tags Combat isolated acceptance publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2632 (Protocol): The server speaks protocol 2632, so match your game version; cs161125 (Build): The server runs build 161125; 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. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into Combat isolated acceptance?
In Rust, F1 opens the console: type client.connect 109.235.49.132:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.