RustLocalControl
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 14h ago · 80.55.38.89:28025
Abstract
We describe the public Rust server RustLocalControl, reached at 80.55.38.89:28025. It is offline at the last check, against a seven-day mean of 1 and a peak of 11. It ranks #6,711 of all servers, the top 30%. It last wiped 22d ago.
Keywordsmodded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 30% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 1 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Tue 6 Oct, 08:0622d ago | 1 | – | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| 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 |
| Map | Procedural Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and next Rust wipe times [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 155 on average | 156/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average | 124/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average | 185/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average | 114/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average | 9/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1What is the location of RustLocalControl?
There is no region published for RustLocalControl. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 80.55.38.89:28025 is its address.
A.2How reliable is RustLocalControl, and is it currently online?
RustLocalControl is currently offline, with the last sighting 14 hours ago. Of the 168 hours in the last 7 full days, 27 were served, an availability of 16%. It was first observed on 6 October 2026 by Rust Statistics.
A.3What version of Rust is run on RustLocalControl?
Rust network protocol 2635 and build 168909 is the version that RustLocalControl runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.
Wipe timing
A.4What schedule does RustLocalControl follow for wipes?
There are not yet enough recorded wipes for RustLocalControl to reveal its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. 22 days 2 hours have passed since the current world was generated.
A.5How would you describe wipe day on RustLocalControl?
The average busiest point of recent wipes was 1 players. The crowd reached its maximum 0 hours after the latest wipe.
Population
A.6What is the rank of RustLocalControl among Rust servers?
Ranked by player hours across seven days, RustLocalControl holds #6,711, in the top 30% of all ranked servers.
A.7How would you characterise the player activity on RustLocalControl?
RustLocalControl is not online now; 14 hours have passed since it was last seen. Averaged over the last seven days: 1 players; the same period peaks at 1. The busiest hour of the last 48 is 11:00 UTC, averaging 1 players.
Tags, lists
A.8How should the tags on RustLocalControl be interpreted?
gmrust (Game mode): Survival on standard Rust rules; mp1 (Max players): 1 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags RustLocalControl publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.9Where can RustLocalControl be found among the Rust Statistics lists and filters?
The Rust Statistics lists that RustLocalControl fits are: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Settings and map
A.10What are the settings and rules that govern RustLocalControl?
Its name carries no gather rate for RustLocalControl. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC is inactive: the anti-cheat from Valve is off.
A.11What is the map for RustLocalControl?
A procedural map, generated by the game, is what RustLocalControl runs.
Connection
A.12What steps are required to join RustLocalControl?
Press F1 inside Rust to open the console and enter client.connect 80.55.38.89:28025. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp1 | Max players. 1 slots are available. |
ts8 | Group limit. The team cap is 8, which is the game default. |
v2635 | Protocol. Your game must run protocol 2635 to connect. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. Networking runs on RakNet, the game's standard layer. |
$r? | Region code. A region code has not been set. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
^z | Modded. Modded listing: plugins or settings modify the game. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.