Offline 188.29.127.108:28215 checked 30d ago
LOCAL-TEST-DO-NOT-JOIN
Connect
srv = rust.server("188.29.127.108:28216")
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 71% 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 | Tue 29 Sep, 11:14 UTC30d 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
- 188.29.127.108:28215
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 11:14 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 · 495 on average | 84/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 115/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 283 on average | 397/450 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 21/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 476/525 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 362/425 |
Quick answers
From the figures on this page.
Population data
What position does LOCAL-TEST-DO-NOT-JOIN take in the server rankings?
Player hours over seven days put LOCAL-TEST-DO-NOT-JOIN at #16,882, in the top 71% of the ranked set.
What population does LOCAL-TEST-DO-NOT-JOIN carry?
The current row shows LOCAL-TEST-DO-NOT-JOIN offline; the last response was 30 days 13 hours ago.
About the server
What is the Rust version on LOCAL-TEST-DO-NOT-JOIN?
Version Rust network protocol 2633 and build 165217 on Windows is reported by LOCAL-TEST-DO-NOT-JOIN. Steam updates your game for you, but the protocol must match to join.
How reliable is LOCAL-TEST-DO-NOT-JOIN, and is it up?
LOCAL-TEST-DO-NOT-JOIN is offline at this refresh; the last response came 30 days 13 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 29 September 2026.
Which location does LOCAL-TEST-DO-NOT-JOIN run from?
For LOCAL-TEST-DO-NOT-JOIN, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 188.29.127.108:28215 is its address.
Settings and map
What rules and settings are recorded for LOCAL-TEST-DO-NOT-JOIN?
No gather rate appears in the name: LOCAL-TEST-DO-NOT-JOIN. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Which map has LOCAL-TEST-DO-NOT-JOIN loaded?
The game generates its map: procedural, on LOCAL-TEST-DO-NOT-JOIN.
Wipe schedule
On what schedule does LOCAL-TEST-DO-NOT-JOIN wipe?
A rhythm cannot be read from the wipes of LOCAL-TEST-DO-NOT-JOIN on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 30 days 13 hours ago.
What is wipe day on LOCAL-TEST-DO-NOT-JOIN like?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain LOCAL-TEST-DO-NOT-JOIN?
On Rust Data, LOCAL-TEST-DO-NOT-JOIN appears in these lists: 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.
How should you read the server tags on LOCAL-TEST-DO-NOT-JOIN?
Read by the game's server browser, the tags LOCAL-TEST-DO-NOT-JOIN publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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-TEST-DO-NOT-JOIN?
The manual route: launch Rust, F1, then client.connect 188.29.127.108:28215. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.