Offline 88.175.92.131:28015 checked 19d ago
Rust Local Test
Connect
srv = rust.server("88.175.92.131: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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 | Mon 5 Oct, 17:27 UTC23d ago | 1 | NaN | running | 1 |
| 1 | Thu 1 Oct, 20:37 UTC FW27d ago | 1 | held half | 3.9 days | 0 |
| 2 | Wed 23 Sep, 20:33 UTC35d ago | 1 | held half | 8 days | 1 |
| 3 | Sun 20 Sep, 22:40 UTC38d ago | 1 | NaN | 2.9 days | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 88.175.92.131:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 17:27 UTC
- hostname
- –
- first seen
- 16 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 · 516 on average | 453/475 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 364/375 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 43/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 31/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 52/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 243 on average | 151/200 |
Quick answers
From the figures on this page.
Population
What position does Rust Local Test take in the server rankings?
Over the last seven days Rust Local Test sits at #13,578 on player hours, in the top 61% of ranked servers.
How many players does Rust Local Test hold at once?
Offline now for Rust Local Test, with the last sample 19 days 12 hours ago.
About the server
What Rust version does Rust Local Test run?
Rust network protocol 2634 and build 167398 on Windows is what Rust Local Test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Rust Local Test, and is it up?
Offline now for Rust Local Test, last seen 19 days 12 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 16 September 2026.
Which location does Rust Local Test run from?
There is no region published for Rust Local Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 88.175.92.131:28015.
Settings and map
Which rules apply on Rust Local Test, and what settings?
No gather rate appears in the name: Rust Local Test. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
When does Rust Local Test wipe, and how often?
Rust Local Test wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 23 days 17 hours ago.
On Rust Local Test, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags and filters
Where does Rust Local Test appear among Rust Data lists and filters?
On Rust Data, Rust Local Test 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.
Which meanings do the tags on Rust Local Test hold?
The game's server browser reads these tags from Rust Local Test: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Build number: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Rust Local Test?
Enter client.connect 88.175.92.131:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.