Rust Data

rustdata.spaceservers95.182.106.48:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 95.182.106.48:28015 checked 7d ago

Zhanibek | X3 | No Junk | AutoLoot

3x moddedoxide

Connect

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

Right now

srv.summary()
players now 0/8 # 0% full
7-day average 0 # peak –
rank #15,404 # top 69%
last wipe 7d ago # no schedule published
next wipe – # too few wipes seen yet

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
15k10k15k20k15 Oct17 Oct20 Oct22 Oct25 Oct27 Oct

Top 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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 21:46 UTC7d 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
95.182.106.48:28015
region
–
max players
8
group limit
8, the default
wipe schedule
–
last wipe
20 Oct 2026, 21:46 UTC
hostname
–
first seen
15 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Atlas - EU 3x | No BPs | MondaysEU · groups of 16+ · 3x · weekly · 386 on average732/800
1Vital Rust - EU Mondays | 3x | No BPsEU · groups of 14+ · 3x · weekly · 174 on average363/400
2HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 123 on average34/100
3HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 121 on average68/100
4FLAME RUST #1 [ NOLIMIT | x3 | MAGIC ] WIPE 27.10groups of 30+ · 3x · weekly · 110 on average259/350
5AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 105 on average34/100

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Zhanibek | X3 | No Junk | AutoLoot rank?

Rank #15,404 on seven-day player hours for Zhanibek | X3 | No Junk | AutoLoot, within the top 69% of all ranked servers.

How many players does Zhanibek | X3 | No Junk | AutoLoot hold at once?

Zhanibek | X3 | No Junk | AutoLoot returns no live count at this refresh, having last been seen 7 days 21 hours ago.

Server facts

What Rust version does Zhanibek | X3 | No Junk | AutoLoot run?

The build is Rust network protocol 2634 and build 167781 on Windows, run by Zhanibek | X3 | No Junk | AutoLoot. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Zhanibek | X3 | No Junk | AutoLoot, and is it online now?

Zhanibek | X3 | No Junk | AutoLoot is offline at this refresh; the last response came 7 days 21 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 15 October 2026.

In which location is Zhanibek | X3 | No Junk | AutoLoot hosted?

There is no region published for Zhanibek | X3 | No Junk | AutoLoot. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 95.182.106.48:28015 is its address.

Map and rules

What rules and settings are recorded for Zhanibek | X3 | No Junk | AutoLoot?

Gather sits at 3x, read from the server's own name: Zhanibek | X3 | No Junk | AutoLoot. 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. 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.

Which map has Zhanibek | X3 | No Junk | AutoLoot selected?

Zhanibek | X3 | No Junk | AutoLoot runs a procedural map, which the game generates.

Wipe data

When does Zhanibek | X3 | No Junk | AutoLoot wipe, and on what schedule?

The record for Zhanibek | X3 | No Junk | AutoLoot holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 7 days 22 hours ago.

On Zhanibek | X3 | No Junk | AutoLoot, what happens on wipe day?

Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Lists and tags

Which lists on Rust Data hold Zhanibek | X3 | No Junk | AutoLoot, and which filters?

These Rust Data lists include Zhanibek | X3 | No Junk | AutoLoot: Modded Rust servers and 3x Rust servers, filtered live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 3x.

Which meanings do the tags on Zhanibek | X3 | No Junk | AutoLoot hold?

These tags are published by Zhanibek | X3 | No Junk | AutoLoot and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp8 (Max players): 8 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join Zhanibek | X3 | No Junk | AutoLoot?

In Rust, F1 opens the console: type client.connect 95.182.106.48: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 mp8,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp8
Max players 8 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^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 89,289 players 11,829 servers online