Offline 2.134.73.108:28015 checked 24d ago
Local Test Server
Connect
srv = rust.server("2.134.73.108: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, measured since 17 Sep. 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 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 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 11:37 UTC24d ago | 1 | NaN | running | 0 |
| 1 | Fri 2 Oct, 17:24 UTC26d ago | 1 | NaN | 1.8 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
2000 · seed 12345
- map
- Procedural Map
- size
- 2000
- seed
- 12345
Server
srv.info()- address
- 2.134.73.108:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 11:37 UTC
- hostname
- –
- first seen
- 13 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 54/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 76/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 24/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Population data
What position does Local Test Server take in the server rankings?
Player hours over seven days put Local Test Server at #16,001, in the top 71% of the ranked set.
What population does Local Test Server carry?
The current row shows Local Test Server offline; the last response was 24 days 14 hours ago.
Server facts
Which Rust version is Local Test Server on?
Version Rust network protocol 2634 and build 166586 on Windows is reported by Local Test Server. Joining needs the same protocol on your game; Steam handles the update.
Is Local Test Server up, and what does its uptime show?
Offline now for Local Test Server, last seen 24 days 14 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 13 September 2026.
In which location is Local Test Server hosted?
No region is published by Local Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 2.134.73.108:28015.
Rules, settings, map
Which settings and rules does Local Test Server run?
No gather rate appears in the name: Local Test Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has Local Test Server loaded?
The game generates the map on Local Test Server: procedural, size 2,000, seed 12345. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does Local Test Server wipe, and how often?
Too few wipes are on record for Local Test Server to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 24 days 18 hours ago, and that is the one in play.
What is wipe day on Local Test Server like?
The average peak over recent wipes is 1 players. 2 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does Local Test Server appear among Rust Data lists and filters?
On Rust Data, Local Test Server appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Local Test Server?
The game's server browser reads these tags from Local Test Server: gmrust (Game mode): Rust survival in its standard form; mp15 (Max players): Slot count: 15; 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): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to Local Test Server?
The manual route: launch Rust, F1, then client.connect 2.134.73.108:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.