Rust Data

rustdata.spaceservers51.79.46.206:20001.ipynb

Run all rust-data · live

‹ All servers

Online 51.79.46.206:20000 checked 14m ago

Blazingcoder2's House of Rust

moddedoxide

Connect

srv = rust.server("51.79.46.206:20001")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040023:0008:0017:0003:0012:0021: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 9 Oct. 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
15k10k15k20k9 Oct13 Oct17 Oct21 Oct25 Oct29 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 peak3players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 9 Oct, 14:51 UTC20d ago 3 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

3500 · seed 471471404
Map of Blazingcoder2's House of Rust
map
Procedural Map
size
3500
seed
471471404
Open on RustMaps

Server

srv.info()
address
51.79.46.206:20000
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
9 Oct 2026, 17:48 UTC
hostname
–
first seen
9 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 · 150 on average40/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 · 120 on average84/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average34/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average87/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average301/310

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Blazingcoder2's House of Rust rank?

Rank #15,276 on seven-day player hours for Blazingcoder2's House of Rust, within the top 69% of all ranked servers.

What population does Blazingcoder2's House of Rust carry?

The sample now reads 0 players for Blazingcoder2's House of Rust, out of 40 slots. Over the last seven days it averaged 0 players.

Server data

How well does Blazingcoder2's House of Rust perform?

The 48-hour average is 209 server fps, with a low of 121. The entity count peaked at 65,392, covering buildings, deployables and the rest of the world. Memory peaked at 3,825 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on Blazingcoder2's House of Rust?

Rust network protocol 2635 and build 168909 on Linux is what Blazingcoder2's House of Rust runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Blazingcoder2's House of Rust, and is it up?

Online is the state at the latest refresh for Blazingcoder2's House of Rust. A restart about 6 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 9 October 2026.

Where does Blazingcoder2's House of Rust sit?

There is no region published for Blazingcoder2's House of Rust. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 51.79.46.206:20000 is its address.

Settings and map

What rules and settings are recorded for Blazingcoder2's House of Rust?

No gather rate appears in the name: Blazingcoder2's House of Rust. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on Blazingcoder2's House of Rust?

Blazingcoder2's House of Rust runs a procedural map of size 3,500 with seed 471471404, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Blazingcoder2's House of Rust wipe, and on what schedule?

A rhythm cannot be read from the wipes of Blazingcoder2's House of Rust on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 20 days 4 hours ago.

On Blazingcoder2's House of Rust, what happens on wipe day?

Recent wipes averaged 3 players at their peak. 15 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Where does Blazingcoder2's House of Rust appear among Rust Data lists and filters?

These Rust Data lists include Blazingcoder2's House of Rust: 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 Blazingcoder2's House of Rust?

The game's server browser reads these tags from Blazingcoder2's House of Rust: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^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.

How to join

How can I connect to Blazingcoder2's House of Rust?

The manual route: launch Rust, F1, then client.connect 51.79.46.206:20000. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players Slot count: 40.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

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 78,914 players 11,790 servers online