Rust StatisticsWorking papers on every public Rust server · 67,519 players now

IrrenhausbyCK

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 116.202.52.49:41674

Abstract

We describe the public Rust server IrrenhausbyCK, reached at 116.202.52.49:41674. At the last check it held 0 of 40 places, against a seven-day mean of 0 and a peak of 21. It ranks #12,803 of all servers, the top 58%. It last wiped 12d ago.

Keywordsmodded oxide

Access. Launch Rust and join Website ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/400% full
In the queue0no queue
Seven-day mean0peak 2
Rank2#12,803top 58%
Last wipe12d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123413:0022:0007:0016:0001:0010:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
02040608013:0022:0007:0016:0001:0010:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 58% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap18 daysbetween real wipes
Wipe-day peak1players, last three wipes
Crowd held0%else halves by day 3
Fri 16 OctMon 28 Sep
00.511.52+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 16 Oct, 06:4012d ago 0 – running 0
Mon 28 Sep, 05:5230d ago 2 halved by day 3 18 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of IrrenhausbyCK
Figure 5: The map: Procedural Map, size 5555, seed 1824653692. Open on RustMaps.
Table 4: The server's published settings.
Address116.202.52.49:41674
Region–
Max players40
Group limit8, the default
Wipe schedule–
Last wipe16 Oct 2026, 06:40 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size5555
Seed1824653692

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 155 on average170/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 127 on average132/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average177/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average138/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average14/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average50/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Does IrrenhausbyCK perform well?

Over the past 48 hours, it ran at an average of 70 server fps, with a low of 60. Buildings, deployables and all other world objects counted together reached a maximum of 187,012 entities. The peak memory usage was 4,678 MB. Players experience lag when fps is low and the entity count is rising.

A.2What is the location of IrrenhausbyCK?

There is no region published for IrrenhausbyCK. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 116.202.52.49:41674.

A.3What is the reliability of IrrenhausbyCK, and is it online?

IrrenhausbyCK is online at this time. The uptime it reports indicates a restart about 3 days 17 hours ago. Of the 168 hours in the last 7 full days, 168 were served, an availability of 100%. It was first observed on 13 September 2026 by Rust Statistics.

A.4What version of Rust is run on IrrenhausbyCK?

IrrenhausbyCK is running Rust network protocol 2635 and build 167781 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.5What schedule does IrrenhausbyCK follow for wipes?

There are not yet enough recorded wipes for IrrenhausbyCK to reveal its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 12 days 5 hours ago.

A.6What characterises wipe day on IrrenhausbyCK?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 0 hours after the latest wipe. The crowd stayed above half its peak until the next wipe in 0% of recent wipes. Otherwise, a fall below half took place by day 3.

Population

A.7How does IrrenhausbyCK compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts IrrenhausbyCK at #12,803, within the top 58% of ranked servers.

A.8At what level does IrrenhausbyCK operate in terms of players?

On IrrenhausbyCK, 0 of the 40 slots are occupied at present. The peak over seven days is 2, against an average of 0.

Tags and filters

A.9What do the tags associated with IrrenhausbyCK signify?

Tags from IrrenhausbyCK, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp40 (Max players): The slot count is 40; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can IrrenhausbyCK be found among the Rust Statistics lists and filters?

The Rust Statistics lists that IrrenhausbyCK fits are: Modded Rust servers. It appears under the following filters 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.

Rules, settings, map

A.11Under what rules and settings does IrrenhausbyCK operate?

No gather rate appears in the name of IrrenhausbyCK. The group cap is 8 players, which is the default in the game. The mode is survival, which means gather, build and raid: the standard game. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. The server has VAC on, Valve's anti-cheat.

A.12On which map does IrrenhausbyCK take place?

Size 5,555 and seed 1824653692 define the procedural, game-generated map on IrrenhausbyCK. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What is the process for joining IrrenhausbyCK?

Enter client.connect 116.202.52.49:41674 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you. The website for this server is https://byteblitz.de/start.

Appendix BServer tags

What each of the server's tags means. Published as mp40,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp40Max players. The slot count is 40.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs167781Build. The game build is 167781.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. The region code is unset.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. Modded listing: plugins or settings modify the game.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.