Offline 185.215.184.138:28015 checked 3d ago
Local Turret Test
Connect
srv = rust.server("185.215.184.138: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 66% 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, 14 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 17:16 UTC4d 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
- 185.215.184.138:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 17:16 UTC
- hostname
- –
- first seen
- 25 Oct 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 | 73/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 · 118 on average | 149/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 51/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 138/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Local Turret Test rank?
Rank #14,638 on seven-day player hours for Local Turret Test, within the top 66% of all ranked servers.
How full does Local Turret Test run?
Local Turret Test returns no live count at this refresh, having last been seen 3 days 12 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What is the Rust version on Local Turret Test?
Rust network protocol 2635 and build 168909 on Windows is what Local Turret Test runs. Steam updates your game for you, but the protocol must match to join.
Is Local Turret Test up, and what does its uptime show?
Local Turret Test is offline at this refresh; the last response came 3 days 12 hours ago. 1 of 72 hours up over the last 3 full days, or 1%. The first row Rust Data holds for it is dated 25 October 2026.
Where does Local Turret Test sit?
For Local Turret 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 185.215.184.138:28015.
Settings and map
Which rules apply on Local Turret Test, and what settings?
You will not find a gather rate in the string Local Turret Test. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Local Turret Test loaded?
Local Turret Test runs a procedural map, which the game generates.
Wipes and dates
When does Local Turret Test wipe, and how often?
Too few wipes are on record for Local Turret Test to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 4 days 3 hours ago, and that is the one in play.
What is wipe day on Local Turret Test like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 14 hours in.
Tags and filters
Which lists on Rust Data hold Local Turret Test, and which filters?
On Rust Data, Local Turret Test appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Local Turret Test?
Read by the game's server browser, the tags Local Turret Test publishes are: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): 5 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Local Turret Test?
Enter client.connect 185.215.184.138:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.