Rust Data

rustdata.spaceservers116.202.52.49:41676.ipynb

Run all rust-data · live

‹ All servers

Online 116.202.52.49:41674 checked 9m ago

IrrenhausbyCK

moddedoxide

Connect

srv = rust.server("116.202.52.49:41676")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak 2
rank #12,821 # top 58%
last wipe 12d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123413:0022:0007:0017:0002:0011:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608013:0022:0007:0017:0002:0011:00

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, measured since 17 Sep. 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

usual gap18 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Fri 16 OctMon 28 Sep
00.511.52+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 Fri 16 Oct, 06:40 UTC12d ago 0 NaN running 0
1 Mon 28 Sep, 05:52 UTC30d ago 2 halved by day 3 18 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

5555 · seed 1824653692
Map of IrrenhausbyCK
map
Procedural Map
size
5555
seed
1824653692
Open on RustMaps

Server

srv.info()
address
116.202.52.49:41674
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 06:40 UTC
hostname
–
first seen
13 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 · 156 on average185/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average122/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average162/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average134/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average13/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average48/1000

Quick answers

From the figures on this page.

Population data

What position does IrrenhausbyCK take in the server rankings?

Rank #12,821 on seven-day player hours for IrrenhausbyCK, within the top 58% of all ranked servers.

What population does IrrenhausbyCK carry?

The sample now reads 0 players for IrrenhausbyCK, out of 40 slots. Over the last seven days it averaged 0 players and peaked at 2.

Server facts

How smoothly does IrrenhausbyCK run?

The 48-hour average is 70 server fps, with a low of 60. Entity numbers reached 187,012, and that includes buildings, deployables and the rest. Memory peaked at 4,678 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on IrrenhausbyCK?

Version Rust network protocol 2635 and build 167781 on Linux is reported by IrrenhausbyCK. Steam updates your game for you, but the protocol must match to join.

Is IrrenhausbyCK up, and what does its uptime show?

Online is the state at the latest refresh for IrrenhausbyCK. A restart about 3 days 18 hours ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 13 September 2026.

Where does IrrenhausbyCK sit?

There is no region published for IrrenhausbyCK. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 116.202.52.49:41674 is its address.

Map and rules

What rules and settings are recorded for IrrenhausbyCK?

You will not find a gather rate in the string IrrenhausbyCK. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. 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.

Which map has IrrenhausbyCK loaded?

Size 5,555, seed 1824653692: the procedural map on IrrenhausbyCK, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does IrrenhausbyCK wipe, and how often?

A rhythm cannot be read from the wipes of IrrenhausbyCK on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 12 days 6 hours ago.

What is wipe day on IrrenhausbyCK like?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 3.

Tags and filters

Which Rust Data filters and lists contain IrrenhausbyCK?

On Rust Data, IrrenhausbyCK appears in these lists: 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 2 weeks.

How should you read the server tags on IrrenhausbyCK?

The game's server browser reads these tags from IrrenhausbyCK: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to IrrenhausbyCK?

In Rust, F1 opens the console: type client.connect 116.202.52.49:41674. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://byteblitz.de/start.

Server tags · what each one means

srv.tags.decode()

Published as mp40,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players 40 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs167781
Build Recorded game build: 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

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