Rust StatisticsWorking papers on every public Rust server · 60,549 players now

Blazingcoder2's House of Rust

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 12m ago · 51.79.46.206:20000

Abstract

We describe the public Rust server Blazingcoder2's House of Rust, reached at 51.79.46.206:20000. At the last check it held 0 of 40 places, against a seven-day mean of 01. It ranks #15,323 of all servers, the top 69%. It last wiped 19d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ 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 –
Rank2#15,323top 69%
Last wipe19d 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
0123412:0021:0006:0014:0000:0009: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
010020030040012:0021:0006:0014:0000:0009: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 9 Oct.

4Rank

The server stands in the top 69% 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
15k10k15k20k9 Oct13 Oct17 Oct21 Oct25 Oct29 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
Wipe-day peak3players, last three wipes
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 3, 15 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 9 Oct, 14:5119d ago 3 – 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. 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 Blazingcoder2's House of Rust
Figure 5: The map: Procedural Map, size 3500, seed 471471404. Open on RustMaps.
Table 4: The server's published settings.
Address51.79.46.206:20000
Region–
Max players40
Group limit8, the default
Wipe schedule–
Last wipe9 Oct 2026, 17:48 UTC
Hostname–
First seen9 Oct 2026
MapProcedural Map
Size3500
Seed471471404

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and Rust wipe forecast [3].

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

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of Blazingcoder2's House of Rust smooth?

Its average server fps over the last 48 hours was 209, with a minimum of 121. Buildings, deployables and all other world objects counted together reached a maximum of 65,385 entities. The peak memory usage was 3,785 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What location does Blazingcoder2's House of Rust have?

There is no region published for Blazingcoder2's House of Rust. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 51.79.46.206:20000 is its address.

A.3What is the reliability of Blazingcoder2's House of Rust, and is it online?

At the present moment, Blazingcoder2's House of Rust is online. Based on the uptime it reports, the last restart occurred about 15 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. The first record of it by Rust Statistics dates to 9 October 2026.

A.4What is the Rust version for Blazingcoder2's House of Rust?

The version of Rust on Blazingcoder2's House of Rust is network protocol 2635 and build 168909, and the operating system is Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.5On what cycle does Blazingcoder2's House of Rust wipe?

Too few wipes by Blazingcoder2's House of Rust have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 19 days 17 hours.

A.6What happens on Blazingcoder2's House of Rust when wipe day arrives?

Across its recent wipes, the average peak population was 3 players. The peak on the latest wipe came 15 hours after it began.

Player count

A.7How does Blazingcoder2's House of Rust compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Blazingcoder2's House of Rust at #15,323, within the top 69% of ranked servers.

A.8At what level does Blazingcoder2's House of Rust operate in terms of players?

The current population of Blazingcoder2's House of Rust is 0, drawn from 40 slots. The mean population for the last seven days is 0.

Tags and filters

A.9What is the meaning of the tags on Blazingcoder2's House of Rust?

Tags from Blazingcoder2's House of Rust, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp40 (Max players): It offers 40 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.10Where can Blazingcoder2's House of Rust be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Blazingcoder2's House of Rust: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.11Under what rules and settings does Blazingcoder2's House of Rust operate?

Its name carries no gather rate for Blazingcoder2's House of Rust. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

A.12What is the map for Blazingcoder2's House of Rust?

The game generates Blazingcoder2's House of Rust's procedural map at size 3,500, from seed 471471404. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

Connection

A.13What is the process for joining Blazingcoder2's House of Rust?

Enter client.connect 51.79.46.206:20000 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.

Appendix BServer tags

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

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp40Max players. It offers 40 slots.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. This server runs game build 168909.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^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. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.