Offline 178.217.104.231:28015 checked 32d ago
Interium Local Audit
Connect
srv = rust.server("178.217.104.231:28017")
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 61% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 26 Sep, 15:23 UTC32d ago | 1 | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 178.217.104.231:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 15:40 UTC
- hostname
- –
- first seen
- 26 Sep 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 · 560 on average | 187/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 118/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 19/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 288 on average | 12/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 19/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 250 on average | 26/225 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Interium Local Audit rank?
Rank #14,351 on seven-day player hours for Interium Local Audit, within the top 61% of all ranked servers.
How many players does Interium Local Audit hold at once?
Interium Local Audit returns no live count at this refresh, having last been seen 32 days 5 hours ago.
About the server
What is the Rust version on Interium Local Audit?
The build is Rust network protocol 2633 and build 165217 on Windows, run by Interium Local Audit. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Interium Local Audit, and is it up?
Interium Local Audit is offline at this refresh; the last response came 32 days 5 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 26 September 2026.
In which location is Interium Local Audit hosted?
No region is published by Interium Local Audit. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 178.217.104.231:28015 is its address.
Rules, settings, map
What rules and settings are recorded for Interium Local Audit?
The name Interium Local Audit carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC off.
Which map has Interium Local Audit selected?
The game generates its map: procedural, on Interium Local Audit.
Wipe schedule
When does Interium Local Audit wipe, and how often?
The record for Interium Local Audit holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 32 days 10 hours ago, and that is the one in play.
On Interium Local Audit, what happens on wipe day?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does Interium Local Audit appear among Rust Data lists and filters?
On Rust Data, Interium Local Audit 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; Group limit: 5 or more.
How should you read the server tags on Interium Local Audit?
Read by the game's server browser, the tags Interium Local Audit publishes are: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into Interium Local Audit?
In Rust, F1 opens the console: type client.connect 178.217.104.231:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.