Offline 80.55.38.89:28025 checked 7h ago
RustLocalControl
Connect
srv = rust.server("80.55.38.89:28027")
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 28% 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 | Tue 6 Oct, 08:06 UTC21d 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
- 80.55.38.89:28025
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 08:06 UTC
- hostname
- –
- first seen
- 6 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 · 160 on average | 40/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 49/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 20/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 5/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does RustLocalControl rank?
Over the last seven days RustLocalControl sits at #6,328 on player hours, in the top 28% of ranked servers.
How many players does RustLocalControl hold at once?
RustLocalControl returns no live count at this refresh, having last been seen 7 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Peak hour in the last 48 hours: 09:00 UTC, mean 1 players.
About the server
What Rust version does RustLocalControl run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by RustLocalControl. Steam updates your game for you, but the protocol must match to join.
How reliable is RustLocalControl, and is it up?
The latest sample has RustLocalControl offline, with a last sighting 7 hours ago. 27 of 168 hours up over the last 7 full days, or 16%. Its earliest recorded date in Rust Data is 6 October 2026.
Where does RustLocalControl sit?
There is no region published for RustLocalControl. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 80.55.38.89:28025 is its address.
Rules, settings, map
Which rules apply on RustLocalControl, and what settings?
No gather rate appears in the name: RustLocalControl. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC off.
Which map has RustLocalControl loaded?
RustLocalControl runs a procedural map, which the game generates.
Wipe data
When does RustLocalControl wipe, and on what schedule?
A rhythm cannot be read from the wipes of RustLocalControl 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. A new world was started 21 days 18 hours ago, and that is the one in play.
On RustLocalControl, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold RustLocalControl, and which filters?
The Rust Data lists that RustLocalControl fits are: 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.
Which meanings do the tags on RustLocalControl hold?
The game's server browser reads these tags from RustLocalControl: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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.
Connecting
What is the way into RustLocalControl?
Enter client.connect 80.55.38.89:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.