BlockServer01
Offline 31.170.144.218:28015 checked 24d ago
Vital stats
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 61% 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.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Tags
Which Rust Pop Watch lists and filters include BlockServer01?
These are the Rust Pop Watch lists that include BlockServer01: Modded Rust servers, live. These are the filters that list it on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on BlockServer01 mean?
These are the tags BlockServer01 publishes for the browser: gmrust (Game mode): Survival, standard Rust style; mp2 (Max players): There are 2 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game must be on the same protocol version: 2634; cs166586 (Build): Game build: 166586; ptrak (Networking): The network layer is RakNet, which is the game's standard; $r? (Region code): No region code has been set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You'll find players now, queue length and world creation time in the tags, printed at the top of this page.
Player counts
How does BlockServer01 rank against other Rust servers?
A seven-day player-hours placing of #13,809 puts BlockServer01 in the top 61% of all ranked servers.
How many players are on BlockServer01 right now?
BlockServer01 went quiet 24 days 11 hours ago and is offline at the moment.
Server facts
Is BlockServer01 online, and how reliable is it?
Down at the moment: BlockServer01 was last seen 24 days 11 hours ago. Out of 168 hours in the last 7 full days, it was online for 0, a 0% uptime. Rust Pop Watch's first record of it is 2 October 2026.
Where is BlockServer01 located?
No region is published by BlockServer01. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. Connect at 31.170.144.218:28015.
Which Rust version is BlockServer01 on?
Rust network protocol 2634 and build 166586 is the version BlockServer01 runs on Windows. To join, your game must be on the same protocol; Steam handles the update.
Wipe days
What is the wipe schedule on BlockServer01?
BlockServer01's rhythm stays hidden while so few of its wipes are on record. The monthly force wipe takes every Rust server down for a new world, and the next one lands on Thursday 5 November at 19:00 UTC. Its current world has been live for 27 days 13 hours.
The rules
Which map does BlockServer01 run?
The map on BlockServer01 is procedural, made by the game.
What are the rules and settings on BlockServer01?
Nothing in the name tells you the gather rate on BlockServer01. Eight players per group: that is the game's default. the usual game of gathering, building and raiding: that is the survival mode. Fighting and raiding between players is allowed. Plugins or settings alter the game, and the browser lists it as Modded. The plugin count is Oxide. The VAC anti-cheat from Valve is on.
Getting in
How do I join BlockServer01?
Enter client.connect 31.170.144.218:28015 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically.