Rust Data

rustdata.spaceservers149.115.45.155:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 149.115.45.155:28015 checked 15d ago

Viper Rust | Kamloops BC Interior

moddedoxide

Connect

srv = rust.server("149.115.45.155:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/50 # 2% full
7-day average 0 # peak –
rank #13,943 # top 64%
last wipe 15d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k11 Oct13 Oct15 Oct16 Oct18 Oct20 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.7 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Mon 12 OctMon 12 OctSun 11 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 12 Oct, 20:48 UTC15d ago 1 NaN running 1
1 Mon 12 Oct, 03:51 UTC16d ago 1 NaN 0.7 days 1
2 Sun 11 Oct, 21:25 UTC16d ago 1 NaN 0.3 days 1
3 Sun 11 Oct, 04:49 UTC17d ago 1 NaN 0.7 days 1

# 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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
149.115.45.155:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
13 Oct 2026, 02:08 UTC
hostname
–
first seen
11 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 155 on average180/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 127 on average127/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average112/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average146/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average15/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average48/1000

Quick answers

From the figures on this page.

Population data

How does Viper Rust | Kamloops BC Interior compare in the rankings?

Player hours over seven days put Viper Rust | Kamloops BC Interior at #13,943, in the top 64% of the ranked set.

How full does Viper Rust | Kamloops BC Interior run?

Viper Rust | Kamloops BC Interior returns no live count at this refresh, having last been seen 15 days 9 hours ago.

About the server

What is the Rust version on Viper Rust | Kamloops BC Interior?

Rust network protocol 2634 and build 167398 on Linux is what Viper Rust | Kamloops BC Interior runs. The protocol has to match before you can join, and Steam does the updating.

Is Viper Rust | Kamloops BC Interior up, and what does its uptime show?

Offline now for Viper Rust | Kamloops BC Interior, last seen 15 days 9 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 11 October 2026.

Which location does Viper Rust | Kamloops BC Interior run from?

No region is published by Viper Rust | Kamloops BC Interior. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 149.115.45.155:28015.

Map and rules

Which settings and rules does Viper Rust | Kamloops BC Interior run?

You will not find a gather rate in the string Viper Rust | Kamloops BC Interior. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.

Wipe data

On what schedule does Viper Rust | Kamloops BC Interior wipe?

Irregular wipe times on Viper Rust | Kamloops BC Interior leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 15 days 10 hours ago, and that is the one in play.

On Viper Rust | Kamloops BC Interior, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which lists on Rust Data hold Viper Rust | Kamloops BC Interior, and which filters?

These Rust Data lists include Viper Rust | Kamloops BC Interior: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on Viper Rust | Kamloops BC Interior?

These tags are published by Viper Rust | Kamloops BC Interior and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way into Viper Rust | Kamloops BC Interior?

In Rust, F1 opens the console: type client.connect 149.115.45.155:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167398
Build Recorded game build: 167398.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits 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.

Rust Data 70,266 players 11,730 servers online