Offline 80.47.13.166:29115 checked 2d ago
CompanionNPC local checks
Connect
srv = rust.server("80.47.13.166: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 70% 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
- 80.47.13.166:29115
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 07:00 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 · 163 on average | 179/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 147/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 33/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 85 on average | 145/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 50/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does CompanionNPC local checks rank?
Over the last seven days CompanionNPC local checks sits at #15,388 on player hours, in the top 70% of ranked servers.
How full does CompanionNPC local checks run?
Offline now for CompanionNPC local checks, with the last sample 2 days 7 hours ago. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on CompanionNPC local checks?
Rust network protocol 2634 and build 167781 on Windows is what CompanionNPC local checks runs. Joining needs the same protocol on your game; Steam handles the update.
Is CompanionNPC local checks up, and what does its uptime show?
CompanionNPC local checks is offline at this refresh; the last response came 2 days 7 hours ago. Uptime of 0% across the last 1 full day: 0 hours of 24. The first row Rust Data holds for it is dated 25 October 2026.
Where does CompanionNPC local checks sit?
There is no region published for CompanionNPC local checks. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 80.47.13.166:29115 is its address.
Map and rules
Which rules apply on CompanionNPC local checks, and what settings?
No gather rate appears in the name: CompanionNPC local checks. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has CompanionNPC local checks loaded?
The game generates its map: procedural, on CompanionNPC local checks.
Wipes and dates
When does CompanionNPC local checks wipe, and on what schedule?
Too few wipes are on record for CompanionNPC local checks 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 2 days 13 hours ago.
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. 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 3 days.
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): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into CompanionNPC local checks?
In Rust, F1 opens the console: type client.connect 80.47.13.166:29115. Launch Rust on this page does the same by opening the game through Steam and connecting.