Offline 31.56.146.125:28015 checked 26d ago
Local No-EAC
Connect
srv = rust.server("31.56.146.125: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 61% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 09:25 UTC26d 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
- 31.56.146.125:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 09:25 UTC
- hostname
- –
- first seen
- 3 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 · 150 on average | 166/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 81/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 258/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 349/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Local No-EAC rank?
Over the last seven days Local No-EAC sits at #13,904 on player hours, in the top 61% of ranked servers.
What population does Local No-EAC carry?
Offline now for Local No-EAC, with the last sample 26 days 3 hours ago.
Server facts
Which Rust version is Local No-EAC on?
Rust network protocol 2634 and build 166652 on Windows is what Local No-EAC runs. Joining needs the same protocol on your game; Steam handles the update.
Is Local No-EAC up, and what does its uptime show?
Offline now for Local No-EAC, last seen 26 days 3 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 3 October 2026.
Which location does Local No-EAC run from?
There is no region published for Local No-EAC. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 31.56.146.125:28015.
Map and rules
What rules and settings are recorded for Local No-EAC?
No gather rate appears in the name: Local No-EAC. No custom cap; the default of 8 players per group stands. Recorded as survival, 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. The plugin count is Oxide. The VAC field reads off.
What is the map on Local No-EAC?
Local No-EAC runs a procedural map, which the game generates.
Wipes and dates
When does Local No-EAC wipe, and how often?
A rhythm cannot be read from the wipes of Local No-EAC 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 26 days 6 hours ago.
What is wipe day on Local No-EAC like?
Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold Local No-EAC, and which filters?
The Rust Data lists that Local No-EAC 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 No-EAC hold?
Read by the game's server browser, the tags Local No-EAC publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Local No-EAC?
In Rust, F1 opens the console: type client.connect 31.56.146.125:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.