Blazingcoder2's House of Rust
51.79.46.206:20000 checked 7m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 30% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 3 players, last three wipes
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.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 9 Oct, 14:51 UTC 5d 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
Quick answers
Population
Where does Blazingcoder2's House of Rust sit in the rankings?
Rank #6,732 over the last seven days in player hours: Blazingcoder2's House of Rust, inside the top 30% of ranked servers.
What is the player count on Blazingcoder2's House of Rust?
Blazingcoder2's House of Rust: 0 players now, with 40 slots available. The seven-day average player count stands at 0, and the highest point was 3. Over the last 48 hours, the peak hour was 09:00 UTC, averaging 2 players.
Server Tags
How should the tags on Blazingcoder2's House of Rust be interpreted?
Read by the game's server browser, the tags Blazingcoder2's House of Rust publishes are: gmrust (Game mode): Rust survival, standard; mp40 (Max players): Slot count is 40; ts8 (Group limit): The game default is 8 per team; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167781 (Build): Game build number: 167781; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): Region code not set; ^o (Oxide): Uses Oxide (uMod) for plugins; ^z (Modded): The Modded category applies; plugins or settings alter gameplay. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
Where does Blazingcoder2's House of Rust appear in BestRustServers.xyz lists and filters?
These BestRustServers.xyz lists include Blazingcoder2's House of Rust: Best modded Rust servers. These filters on the server list display it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Server Overview
What Rust version is Blazingcoder2's House of Rust on?
The combination is Rust network protocol 2634 and build 167781 on Linux for Blazingcoder2's House of Rust. Steam updates your game automatically, but it needs to match the protocol to join.
How smooth is the performance on Blazingcoder2's House of Rust?
Its average server fps over the last 48 hours was 209, with a low of 93. It held up to 64,664 entities: everything from buildings to deployables in the world. The maximum memory used was 3,880 MB. A climbing entity count and low fps are felt by players as lag.
What is the uptime and reliability of Blazingcoder2's House of Rust?
The server is online: Blazingcoder2's House of Rust. According to its reported uptime, the last restart was about 17 hours ago. It was up 100% of the time over the last 4 full days, 96 of 96 hours. It was first seen by BestRustServers.xyz on 9 October 2026.
What is the location of Blazingcoder2's House of Rust?
No region is published by Blazingcoder2's House of Rust. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. You can reach it at 51.79.46.206:20000.
Rules and Settings
What is the map on Blazingcoder2's House of Rust?
Generated by the game, the map on Blazingcoder2's House of Rust is procedural, size 3,500, seed 471471404. On RustMaps, from this page, the same size and seed show the same map.
Blazingcoder2's House of Rust rules and settings: what are they?
The name Blazingcoder2's House of Rust carries no gather multiplier. With no stated limit, groups default to 8 players. Listed as survival, gather, build, raid: the standard game. Player combat and raiding are enabled. Plugins or settings change the game, so it appears under Modded. Plugins in use: Oxide. VAC protection is on.
Wipe Schedule
When does Blazingcoder2's House of Rust wipe?
The record holds too few wipes for Blazingcoder2's House of Rust to show a rhythm. The monthly force wipe applies to every Rust server, and the next is on Thursday 5 November at 19:00 UTC. Its world dates from 5 days 3 hours.
On Blazingcoder2's House of Rust, what occurs on wipe day?
The average busiest point of its recent wipes was 3 players. 15 hours into the latest wipe, the crowd reached its peak.
How to Join
How can I connect to Blazingcoder2's House of Rust?
To connect, type client.connect 51.79.46.206:20000 in the F1 console. Launch Rust on this page opens Rust through Steam and joins you.
Server tags
Published as mp40,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust- Game mode Rust survival, standard.
mp40- Max players Slot count is 40.
ts8- Group limit The game default is 8 per team.
v2634- Protocol Your game must be on protocol 2634 to connect.
cs167781- Build Game build number: 167781.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code Region code not set.
Mods and access
^o- Oxide Uses Oxide (uMod) for plugins.
^z- Modded The Modded category applies; plugins or settings alter gameplay.
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.