Rust Data

rustdata.spaceservers163.44.139.56:28033.ipynb

Run all rust-data · live

‹ All servers

Online 163.44.139.56:28032 checked 8m ago

I will ban anyone who enters!

moddedoxide

Connect

srv = rust.server("163.44.139.56:28033")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,269 # top 68%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123421:0006:0015:0000:0009:0018:00

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
15k10k15k20k22 Sep29 Sep7 Oct14 Oct22 Oct29 Oct

Top 68% 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 gap2.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 1

The first 48 hours of its last wipes

Fri 2 OctTue 29 SepSat 26 Sep
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 Fri 2 Oct, 17:19 UTC27d ago 1 NaN running 0
1 Tue 29 Sep, 15:47 UTC30d ago 1 halved by day 1 3.1 days 0
2 Sat 26 Sep, 05:13 UTC33d ago 1 held half 3.4 days 0
3 Thu 24 Sep, 14:36 UTC35d ago 1 NaN 1.6 days 0
4 Tue 22 Sep, 21:10 UTC36d ago 1 NaN 1.7 days 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
163.44.139.56:28032
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 17:19 UTC
hostname
–
first seen
22 Sep 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 · 151 on average85/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average128/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average150/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average58/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average153/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average346/350

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does I will ban anyone who enters! rank?

Player hours over seven days put I will ban anyone who enters! at #15,269, in the top 68% of the ranked set.

How full does I will ban anyone who enters! run?

Current row: 0 players on I will ban anyone who enters!, against 10 slots. Over the last seven days it averaged 0 players.

Server facts

Which Rust version is I will ban anyone who enters! on?

Version Rust network protocol 2634 and build 166586 on Linux is reported by I will ban anyone who enters!. Joining needs the same protocol on your game; Steam handles the update.

How reliable is I will ban anyone who enters!, and is it up?

The current sample puts I will ban anyone who enters! online. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 22 September 2026.

Where does I will ban anyone who enters! sit?

No region is published by I will ban anyone who enters!. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 163.44.139.56:28032 is its address.

Settings and map

What rules and settings are recorded for I will ban anyone who enters!?

No gather rate appears in the name: I will ban anyone who enters!. No custom cap; the default of 8 players per group stands. survival is the game mode here, and 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. The plugin count is Oxide. Anti-cheat status: VAC on.

What is the map on I will ban anyone who enters!?

I will ban anyone who enters! runs a procedural map, which the game generates.

Wipe schedule

When does I will ban anyone who enters! wipe, and on what schedule?

Irregular wipe times on I will ban anyone who enters! leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 27 days 2 hours ago.

What is wipe day on I will ban anyone who enters! like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. The drop under half arrived by day 1 in the other cases.

Tags, lists

Which lists on Rust Data hold I will ban anyone who enters!, and which filters?

These Rust Data lists include I will ban anyone who enters!: 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.

Which meanings do the tags on I will ban anyone who enters! hold?

The game's server browser reads these tags from I will ban anyone who enters!: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Build number: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^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.

How to join

What is the way into I will ban anyone who enters!?

Enter client.connect 163.44.139.56:28032 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players Slot count: 10.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166586
Build Build number: 166586.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 100,368 players 11,855 servers online