Offline 89.105.214.146:29115 checked 4d ago
CompanionNPC local checks
Connect
srv = rust.server("89.105.214.146:29115")
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 · 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 13:36 UTC4d ago | 0 | NaN | running | 0 |
# 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
- 89.105.214.146:29115
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 13:36 UTC
- hostname
- –
- first seen
- 25 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 · 149 on average | 180/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 · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 84/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 349/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 238/700 |
Quick answers
From the figures on this page.
Population data
What position does CompanionNPC local checks take in the server rankings?
Over the last seven days CompanionNPC local checks sits at #15,344 on player hours, in the top 69% of ranked servers.
How full does CompanionNPC local checks run?
The current row shows CompanionNPC local checks offline; the last response was 4 days 1 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does CompanionNPC local checks run?
Rust network protocol 2635 and build 168909 on Windows is what CompanionNPC local checks runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is CompanionNPC local checks, and is it up?
Offline now for CompanionNPC local checks, last seen 4 days 1 hours ago. 0 of 72 hours up over the last 3 full days, or 0%. The first row Rust Data holds for it is dated 25 October 2026.
In which location is CompanionNPC local checks hosted?
No region is published by CompanionNPC local checks. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 89.105.214.146:29115 is its address.
Map and rules
Which settings and rules does CompanionNPC local checks run?
You will not find a gather rate in the string CompanionNPC local checks. 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. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has CompanionNPC local checks loaded?
A procedural map runs on CompanionNPC local checks, generated by the game.
Wipe schedule
When does CompanionNPC local checks wipe, and on what schedule?
A rhythm cannot be read from the wipes of CompanionNPC local checks on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 4 days 1 hours ago.
What is wipe day on CompanionNPC local checks like?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does CompanionNPC local checks appear among Rust Data lists and filters?
The Rust Data lists that CompanionNPC local checks 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 week.
Which meanings do the tags on CompanionNPC local checks hold?
These tags are published by CompanionNPC local checks and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): 2 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
How to join
What is the way to join CompanionNPC local checks?
In Rust, F1 opens the console: type client.connect 89.105.214.146:29115. Launch Rust on this page does the same by opening the game through Steam and connecting.