Offline 83.217.171.135:28015 checked 28d ago
Local Staging Test Server
Connect
srv = rust.server("83.217.171.135:28016")
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 68% 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 | Tue 29 Sep, 21:01 UTC28d 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 83.217.171.135:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 21:01 UTC
- hostname
- –
- first seen
- 29 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 · 543 on average | 679/725 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 429/475 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 308 on average | 40/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 308 on average | 52/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 268 on average | 228/250 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 266 on average | 134/175 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Local Staging Test Server rank?
Over the last seven days Local Staging Test Server sits at #16,186 on player hours, in the top 68% of ranked servers.
How full does Local Staging Test Server run?
The current row shows Local Staging Test Server offline; the last response was 28 days 16 hours ago.
Server data
What Rust version does Local Staging Test Server run?
The build is Rust network protocol 2634 and build 166257 on Windows, run by Local Staging Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local Staging Test Server, and is it online now?
Local Staging Test Server is offline at this refresh; the last response came 28 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 29 September 2026.
In which location is Local Staging Test Server hosted?
For Local Staging Test Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 83.217.171.135:28015 is its address.
Rules, settings, map
Which rules apply on Local Staging Test Server, and what settings?
The name Local Staging Test Server carries no gather rate. 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. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Wipe data
When does Local Staging Test Server wipe, and on what schedule?
A rhythm cannot be read from the wipes of Local Staging Test Server on record, which are too few. 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 28 days 16 hours ago.
On Local Staging Test Server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does Local Staging Test Server appear among Rust Data lists and filters?
These Rust Data lists include Local Staging Test Server: Rust community servers, unfiltered. These filters bring it up 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 Local Staging Test Server hold?
These tags are published by Local Staging Test Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): Slot count: 5; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166257 (Build): Recorded game build: 166257; ptrak (Networking): The network layer is RakNet, standard for the game; $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 Local Staging Test Server?
In Rust, F1 opens the console: type client.connect 83.217.171.135:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.