Offline 212.142.65.126:28015 checked 7d ago
Local Rust Dev
Connect
srv = rust.server("212.142.65.126: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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 | Sun 4 Oct, 19:24 UTC24d ago | 1 | NaN | running | 0 |
| 1 | Sat 3 Oct, 17:01 UTC26d ago | 1 | NaN | 1.1 days | 0 |
| 2 | Fri 2 Oct, 19:26 UTC26d ago | 1 | NaN | 0.9 days | 0 |
| 3 | Sun 27 Sep, 13:10 UTC32d ago | 0 | NaN | 5.3 days | 0 |
| 4 | Fri 25 Sep, 20:09 UTC33d ago | 1 | NaN | 1.7 days | 1 |
# 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
- 212.142.65.126:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 19:24 UTC
- hostname
- –
- first seen
- 19 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 | 156/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 190/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 102/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 237/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population
How does Local Rust Dev compare in the rankings?
Rank #15,344 on seven-day player hours for Local Rust Dev, within the top 69% of all ranked servers.
How full does Local Rust Dev run?
Local Rust Dev returns no live count at this refresh, having last been seen 7 days 2 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is Local Rust Dev on?
Rust network protocol 2634 and build 167781 on Windows is what Local Rust Dev runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Local Rust Dev, and is it online now?
The latest sample has Local Rust Dev offline, with a last sighting 7 days 2 hours ago. Uptime of 1% across the last 7 full days: 2 hours of 168. Rust Data logged it first on 19 September 2026.
Where does Local Rust Dev sit?
No region is published by Local Rust Dev. 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 212.142.65.126:28015.
Map and rules
Which settings and rules does Local Rust Dev run?
No gather rate appears in the name: Local Rust Dev. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Local Rust Dev selected?
A procedural map runs on Local Rust Dev, generated by the game.
Wipe data
On what schedule does Local Rust Dev wipe?
Local Rust Dev wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 24 days 22 hours ago.
On Local Rust Dev, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does Local Rust Dev appear among Rust Data lists and filters?
The Rust Data lists that Local Rust Dev fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Local Rust Dev hold?
Read by the game's server browser, the tags Local Rust Dev publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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 into Local Rust Dev?
Enter client.connect 212.142.65.126:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.