Offline 31.36.131.153:28015 checked 25d ago
destiny local test
Connect
srv = rust.server("31.36.131.153: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 | Fri 2 Oct, 15:29 UTC25d 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
- 31.36.131.153:28015
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 15:29 UTC
- hostname
- –
- first seen
- 25 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 · 511 on average | 564/625 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 340 on average | 36/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 337 on average | 68/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 316 on average | 281/325 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 280 on average | 116/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 261 on average | 122/150 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does destiny local test rank?
Player hours over seven days put destiny local test at #13,832, in the top 61% of the ranked set.
How full does destiny local test run?
destiny local test returns no live count at this refresh, having last been seen 25 days 2 hours ago.
Server facts
Which Rust version is destiny local test on?
Rust network protocol 2634 and build 166586 on Windows is what destiny local test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is destiny local test, and is it online now?
Offline now for destiny local test, last seen 25 days 2 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 25 September 2026.
In which location is destiny local test hosted?
For destiny local test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 31.36.131.153:28015.
Rules, settings, map
Which settings and rules does destiny local test run?
The name destiny local test carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. VAC is not running; Valve's anti-cheat is off.
What is the map on destiny local test?
The game generates its map: procedural, on destiny local test.
Wipe schedule
On what schedule does destiny local test wipe?
Too few wipes are on record for destiny local test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 25 days 7 hours ago.
On destiny local test, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does destiny local test appear among Rust Data lists and filters?
On Rust Data, destiny 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.
How should you read the server tags on destiny local test?
These tags are published by destiny local test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp8 (Max players): 8 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): Build number: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. 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.
How to join
What is the way to join destiny local test?
The manual route: launch Rust, F1, then client.connect 31.36.131.153:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.