Offline 185.75.238.230:28015 checked 12d ago
Local Test Server
Connect
srv = rust.server("185.75.238.230: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 bestTop 59% 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 | Fri 16 Oct, 14:51 UTC13d 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.75.238.230:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 14:51 UTC
- hostname
- –
- first seen
- 16 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 · 149 on average | 171/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 82/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 351/350 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 249/700 |
Quick answers
From the figures on this page.
Population data
How does Local Test Server compare in the rankings?
Over the last seven days Local Test Server sits at #12,972 on player hours, in the top 59% of ranked servers.
What population does Local Test Server carry?
Local Test Server returns no live count at this refresh, having last been seen 12 days ago.
Server facts
Which Rust version is Local Test Server on?
Version Rust network protocol 2634 and build 167781 on Windows is reported by Local Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local Test Server, and is it online now?
The latest sample has Local Test Server offline, with a last sighting 12 days ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 16 October 2026.
Where does Local Test Server sit?
For Local Test Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 185.75.238.230:28015.
Map and rules
What rules and settings are recorded for Local Test Server?
You will not find a gather rate in the string Local Test Server. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has Local Test Server loaded?
A procedural map runs on Local Test Server, generated by the game.
Wipe schedule
When does Local Test Server wipe, and on what schedule?
A rhythm cannot be read from the wipes of Local Test Server 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 13 days ago.
On Local Test Server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
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. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on Local Test Server?
These tags are published by Local Test Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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. 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
How can I connect to Local Test Server?
In Rust, F1 opens the console: type client.connect 185.75.238.230:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.