Offline 185.215.184.188:28015 checked 2d ago
Local Rust Test 4000
Connect
srv = rust.server("185.215.184.188: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 32% 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 | Mon 26 Oct, 10:22 UTC3d ago | 1 | NaN | running | 1 |
| 1 | Sun 25 Oct, 17:16 UTC4d ago | 1 | NaN | 0.7 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 185.215.184.188:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 10:22 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 · 150 on average | 21/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 44/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 182/215 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Local Rust Test 4000 rank?
Over the last seven days Local Rust Test 4000 sits at #7,177 on player hours, in the top 32% of ranked servers.
How full does Local Rust Test 4000 run?
Offline now for Local Rust Test 4000, with the last sample 2 days 3 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server data
Which Rust version is Local Rust Test 4000 on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Local Rust Test 4000. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local Rust Test 4000, and is it online now?
The latest sample has Local Rust Test 4000 offline, with a last sighting 2 days 3 hours ago. 20 of 96 hours up over the last 4 full days, or 21%. Its earliest recorded date in Rust Data is 25 October 2026.
In which location is Local Rust Test 4000 hosted?
For Local Rust Test 4000, 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. You can reach it at 185.215.184.188:28015.
Map and rules
Which rules apply on Local Rust Test 4000, and what settings?
No gather rate appears in the name: Local Rust Test 4000. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Local Rust Test 4000 selected?
The game generates its map: procedural, on Local Rust Test 4000.
Wipes and dates
When does Local Rust Test 4000 wipe, and on what schedule?
A rhythm cannot be read from the wipes of Local Rust Test 4000 on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 14 hours ago.
On Local Rust Test 4000, 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
Which lists on Rust Data hold Local Rust Test 4000, and which filters?
The Rust Data lists that Local Rust Test 4000 fits are: 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.
Which meanings do the tags on Local Rust Test 4000 hold?
These tags are published by Local Rust Test 4000 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join Local Rust Test 4000?
Enter client.connect 185.215.184.188:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.