Offline 86.146.176.163:28015 checked 9h ago
Local Server1 MAIN
Connect
srv = rust.server("86.146.176.163: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, measured since 19 Oct. 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 31% 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 | Thu 15 Oct, 20:12 UTC14d ago | 1 | NaN | running | 0 |
| 1 | Tue 6 Oct, 12:20 UTC23d ago | 1 | halved by day 8 | 9.3 days | 0 |
| 2 | Wed 30 Sep, 17:39 UTC29d ago | 0 | NaN | 5.8 days | 1 |
| 3 | Mon 21 Sep, 17:07 UTC38d ago | 1 | held half | 9 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
1500 · seed 9876513
- map
- Procedural Map
- size
- 1500
- seed
- 9876513
Server
srv.info()- address
- 86.146.176.163:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 20:44 UTC
- hostname
- –
- first seen
- 17 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 · 150 on average | 39/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 · 120 on average | 86/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 32/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 86/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 309/350 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Local Server1 MAIN rank?
Over the last seven days Local Server1 MAIN sits at #6,952 on player hours, in the top 31% of ranked servers.
How many players does Local Server1 MAIN hold at once?
Offline now for Local Server1 MAIN, with the last sample 9 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 11:00 UTC, averaging 1 players.
Server facts
How well does Local Server1 MAIN perform?
The 48-hour average is 240 server fps, with a low of 240. Entity numbers reached 7,955, and that includes buildings, deployables and the rest. The memory field tops out at 1,371 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is Local Server1 MAIN on?
Rust network protocol 2635 and build 168909 on Windows is what Local Server1 MAIN runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local Server1 MAIN, and is it online now?
Offline now for Local Server1 MAIN, last seen 9 hours ago. Count back 37 minutes from its reported uptime to get the last restart. Over the last 7 full days the hours up number 21 of 168, 12%. Rust Data logged it first on 17 September 2026.
Which location does Local Server1 MAIN run from?
For Local Server1 MAIN, 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 86.146.176.163:28015.
Settings and map
Which rules apply on Local Server1 MAIN, and what settings?
No gather rate appears in the name: Local Server1 MAIN. No custom cap; the default of 8 players per group stands. 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. VAC is running: Valve's anti-cheat is on.
What is the map on Local Server1 MAIN?
Size 1,500, seed 9876513: the procedural map on Local Server1 MAIN, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does Local Server1 MAIN wipe, and on what schedule?
Irregular wipe times on Local Server1 MAIN leave no next wipe to forecast. 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 14 days 1 hours ago, and that is the one in play.
On Local Server1 MAIN, 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. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. Otherwise the crowd fell below half by day 8.
Tags, lists
Which Rust Data filters and lists contain Local Server1 MAIN?
The Rust Data lists that Local Server1 MAIN 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.
Which meanings do the tags on Local Server1 MAIN hold?
The game's server browser reads these tags from Local Server1 MAIN: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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
How can I connect to Local Server1 MAIN?
In Rust, F1 opens the console: type client.connect 86.146.176.163:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.