Offline 31.208.58.48:28031 checked 21d ago
Local protocol reference
Connect
srv = rust.server("31.208.58.48:28032")
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 bestTop 72% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 7 Oct, 08:28 UTC21d ago | 0 | 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
- 31.208.58.48:28031
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 08:49 UTC
- hostname
- –
- first seen
- 6 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 · 549 on average | 147/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 125/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 14/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 284 on average | 18/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 13/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 249 on average | 38/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Local protocol reference rank?
Rank #15,966 on seven-day player hours for Local protocol reference, within the top 72% of all ranked servers.
How full does Local protocol reference run?
Offline now for Local protocol reference, with the last sample 21 days 20 hours ago.
Server data
Which Rust version is Local protocol reference on?
Version Rust network protocol 2634 and build 166652 on Linux is reported by Local protocol reference. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local protocol reference, and is it up?
Local protocol reference is offline at this refresh; the last response came 21 days 20 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 6 October 2026.
Which location does Local protocol reference run from?
No region is published by Local protocol reference. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 31.208.58.48:28031.
Rules, settings, map
Which rules apply on Local protocol reference, and what settings?
The name Local protocol reference carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC off.
Which map has Local protocol reference selected?
The game generates its map: procedural, on Local protocol reference.
Wipe data
When does Local protocol reference wipe, and how often?
Too few wipes are on record for Local protocol reference to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 21 days 20 hours ago, and that is the one in play.
On Local protocol reference, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does Local protocol reference appear among Rust Data lists and filters?
The Rust Data lists that Local protocol reference fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on Local protocol reference hold?
The game's server browser reads these tags from Local protocol reference: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): The server runs build 166652; ptsw (Networking): 'sw' is the network layer field; $r? (Region code): No region code is set. 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.
Join steps
What is the way into Local protocol reference?
The manual route: launch Rust, F1, then client.connect 31.208.58.48:28031. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.