Online 176.215.184.231:28015 checked 8m ago
Rust Devblog 227
Connect
srv = rust.server("176.215.184.231:27015")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 15:53 UTC14d ago | 2 | NaN | running | 1 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 176.215.184.231:28015
- region
- –
- max players
- 100
- group limit
- not published
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 15:53 UTC
- hostname
- –
- first seen
- 15 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 472 on average | 64/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 320 on average | 88/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 283 on average | 195/250 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 279 on average | 5/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 265 on average | 243/250 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 259 on average | 361/375 |
Quick answers
From the figures on this page.
Population
How does Rust Devblog 227 compare in the rankings?
Player hours over seven days put Rust Devblog 227 at #15,270, in the top 69% of the ranked set.
How many players does Rust Devblog 227 hold at once?
Rust Devblog 227 reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on Rust Devblog 227?
Rust network protocol 2219 on Windows is what Rust Devblog 227 runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Rust Devblog 227, and is it online now?
Rust Devblog 227 reports itself online at the current refresh. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 15 October 2026.
Which location does Rust Devblog 227 run from?
For Rust Devblog 227, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 176.215.184.231:28015 is its address.
Map and rules
What rules and settings are recorded for Rust Devblog 227?
No gather rate appears in the name: Rust Devblog 227. No group limit is published. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
What is the map on Rust Devblog 227?
A procedural map runs on Rust Devblog 227, generated by the game.
Wipe schedule
When does Rust Devblog 227 wipe, and on what schedule?
Too few wipes are on record for Rust Devblog 227 to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 14 days 13 hours ago.
On Rust Devblog 227, what happens on wipe day?
The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 5 hours after it began.
Tags and filters
Where does Rust Devblog 227 appear among Rust Data lists and filters?
On Rust Data, Rust Devblog 227 appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all.
How should you read the server tags on Rust Devblog 227?
These tags are published by Rust Devblog 227 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; v2219 (Protocol): Protocol 2219 is required; a different game version cannot connect; ptrak (Networking): Standard network layer for Rust: RakNet; h21aa53ea (Custom tag): A plugin or the owner added this; standard Rust does not define it; stok (Custom tag): A plugin or the owner added this; standard Rust does not define it. 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.
Connecting
What is the way to join Rust Devblog 227?
In Rust, F1 opens the console: type client.connect 176.215.184.231:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.