Offline 94.228.213.206:28115 checked 3d ago
Combat isolated acceptance
Connect
srv = rust.server("94.228.213.206: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 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 94.228.213.206: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 · 151 on average | 17/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 6/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 20/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 112/200 |
Quick answers
From the figures on this page.
Player counts
What position does Combat isolated acceptance take in the server rankings?
Rank #15,264 on seven-day player hours for Combat isolated acceptance, within the top 69% of all ranked servers.
How full does Combat isolated acceptance run?
The current row shows Combat isolated acceptance offline; the last response was 3 days 9 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does Combat isolated acceptance run?
The build is Rust network protocol 2632 and build 161125 on Windows, run by Combat isolated acceptance. The protocol has to match before you can join, and Steam does the updating.
Is Combat isolated acceptance up, and what does its uptime show?
The latest sample has Combat isolated acceptance offline, with a last sighting 3 days 9 hours ago. Uptime of 0% across the last 3 full days: 0 hours of 72. Its earliest recorded date in Rust Data is 26 October 2026.
Which location does Combat isolated acceptance run from?
For Combat isolated acceptance, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 94.228.213.206:28115.
Map and rules
What rules and settings are recorded for Combat isolated acceptance?
No gather rate appears in the name: Combat isolated acceptance. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Combat isolated acceptance loaded?
Combat isolated acceptance runs a procedural map, which the game generates.
Wipes and dates
When does Combat isolated acceptance wipe, and on what schedule?
Too few wipes are on record for Combat isolated acceptance to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 7 days 12 hours ago.
Tags, lists
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): 1 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2632 (Protocol): The server speaks protocol 2632, so match your game version; cs161125 (Build): Recorded game build: 161125; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: 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
How can I connect to Combat isolated acceptance?
Enter client.connect 94.228.213.206:28115 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.