Offline 89.106.72.63:28125 checked 2d ago
LOCAL raid difficulty validation
Connect
srv = rust.server("89.106.72.63:28127")
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 bestTop 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 89.106.72.63:28125
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 21:47 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 · 157 on average | 72/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 71/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 60/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 18/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.
Player counts
What position does LOCAL raid difficulty validation take in the server rankings?
Over the last seven days LOCAL raid difficulty validation sits at #15,339 on player hours, in the top 69% of ranked servers.
How many players does LOCAL raid difficulty validation hold at once?
The current row shows LOCAL raid difficulty validation offline; the last response was 2 days ago. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on LOCAL raid difficulty validation?
Rust network protocol 2635 and build 168909 on Windows is what LOCAL raid difficulty validation runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is LOCAL raid difficulty validation, and is it up?
Offline now for LOCAL raid difficulty validation, last seen 2 days ago. Uptime of 0% across the last 1 full day: 0 hours of 24. Its earliest recorded date in Rust Data is 26 October 2026.
Where does LOCAL raid difficulty validation sit?
There is no region published for LOCAL raid difficulty validation. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 89.106.72.63:28125 is its address.
Map and rules
What rules and settings are recorded for LOCAL raid difficulty validation?
No gather rate appears in the name: LOCAL raid difficulty validation. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. 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.
Wipes and dates
When does LOCAL raid difficulty validation wipe, and on what schedule?
The record for LOCAL raid difficulty validation holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 2 days ago.
Lists and tags
Which lists on Rust Data hold LOCAL raid difficulty validation, and which filters?
The Rust Data lists that LOCAL raid difficulty validation fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on LOCAL raid difficulty validation?
The game's server browser reads these tags from LOCAL raid difficulty validation: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join LOCAL raid difficulty validation?
In Rust, F1 opens the console: type client.connect 89.106.72.63:28125. Launch Rust on this page does the same by opening the game through Steam and connecting.