Rust Server TrendsSeismic network · station log
Recording Stations11,535 Players86,112 Active4,004 Wipes · 3 h131 48 h

Station XX-15535 · no signal

CompanionNPC local checks

Offline 89.105.214.146:29115 checked 26d ago

moddedoxide
Connect
Players now
0/ 2
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,535
top 70%
Last wipe
26d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15535 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 2 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Oct26 Oct28 Oct29 Oct31 Oct1 Nov

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 5 Nov, 19:00 UTC FW15d ago – – – – running –
Sun 25 Oct, 13:36 UTC26d ago M0.0steady 0 – – – 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
МИНИ-КАРТА 2Х | STORM | FPS+ 18.11 EU · groups of 8+ · weekly · 128 on average
133/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
298/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
187/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
60/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11 EU · groups of 16+ · monthly · 69 on average
119/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 14.11 EU · groups of 16+ · monthly · 66 on average
11/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on CompanionNPC local checks?

A procedural map runs on CompanionNPC local checks, generated by the game.

Which settings and rules apply on CompanionNPC local checks?

No gather rate appears in the name of CompanionNPC local checks. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on CompanionNPC local checks?

No players are recorded on CompanionNPC local checks at this moment; it is offline, and the last sighting was 26 days 23 hours ago.

How does CompanionNPC local checks rank against other Rust servers?

On player hours for the past week, CompanionNPC local checks sits at #15,535, which puts it inside the top 70% of every ranked server.

Operator and location

How reliably does CompanionNPC local checks stay online?

As recorded now, CompanionNPC local checks is not reachable, the last contact having been 26 days 23 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 25 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is CompanionNPC local checks hosted?

Nothing about a region comes from CompanionNPC local checks. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 89.105.214.146:29115.

What build of Rust does CompanionNPC local checks use?

On Windows, CompanionNPC local checks runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on CompanionNPC local checks?

On average, the busiest point of its recent wipes drew 0 players. 0 hours into the latest wipe, the crowd reached its peak.

How often does CompanionNPC local checks wipe, and on which days?

The rhythm of CompanionNPC local checks cannot yet be told: too few of its wipes are on record. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 26 days 23 hours.

Lists and tags

What do the server tags on CompanionNPC local checks mean?

Tags published by CompanionNPC local checks and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp2 (Max players): The server has 2 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does CompanionNPC local checks appear?

The Rust Server Trends lists that take in CompanionNPC local checks are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

How do you connect to CompanionNPC local checks?

Enter client.connect 89.105.214.146:29115 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp2,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp2
Max players The server has 2 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.