Online 176.57.174.158:28915 checked 6m ago
NEXHALD
Connect
srv = rust.server("176.57.174.158:28916")
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 22 Sep. 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 best
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:00 UTC FW28d ago | 0 | 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())
About this server · in its own words
print(srv.description)
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 | 85/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 150/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 58/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 153/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 346/350 |
Quick answers
From the figures on this page.
Player counts
What position does NEXHALD take in the server rankings?
Over the last seven days NEXHALD sits at #15,269 on player hours, in the top 68% of ranked servers.
What population does NEXHALD carry?
Current row: 0 players on NEXHALD, against 50 slots. Over the last seven days it averaged 0 players.
Server data
How well does NEXHALD perform?
Averaged over 48 hours: 58 server fps, never under 51. Entity numbers reached 91,128, and that includes buildings, deployables and the rest. A high of 4,326 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is NEXHALD on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by NEXHALD. Joining needs the same protocol on your game; Steam handles the update.
How reliable is NEXHALD, and is it online now?
The current sample puts NEXHALD online. Count back 6 minutes from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 22 September 2026.
In which location is NEXHALD hosted?
For NEXHALD, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 176.57.174.158:28915 is its address.
Settings and map
Which rules apply on NEXHALD, and what settings?
The name NEXHALD carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Premium status is needed to join. The VAC field reads off.
Which map has NEXHALD selected?
The game generates the map on NEXHALD: procedural, size 4,096, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipe schedule
When does NEXHALD wipe, and on what schedule?
A single wipe each month, the force wipe, is all NEXHALD does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 28 days 2 hours ago.
On NEXHALD, what happens on wipe day?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain NEXHALD?
On Rust Data, NEXHALD appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: Premium; Server tag: Premium ^q, Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on NEXHALD hold?
These tags are published by NEXHALD and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon; ^q (Premium): Premium status is needed to join. 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 to join NEXHALD?
Enter client.connect 176.57.174.158:28915 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. Premium status is needed to join.