Offline 43.254.45.56:50430 checked 19d ago
NovaCloud Rust resource validation
Connect
srv = rust.server("43.254.45.56:50431")
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 43.254.45.56:50430
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 17:03 UTC
- hostname
- –
- first seen
- 9 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 · 157 on average | 108/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 · 116 on average | 114/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 93/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 27/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Population
How does NovaCloud Rust resource validation compare in the rankings?
Player hours over seven days put NovaCloud Rust resource validation at #15,882, in the top 72% of the ranked set.
What population does NovaCloud Rust resource validation carry?
NovaCloud Rust resource validation returns no live count at this refresh, having last been seen 19 days 4 hours ago.
About the server
What is the Rust version on NovaCloud Rust resource validation?
Version Rust network protocol 2634 and build 167398 on Linux is reported by NovaCloud Rust resource validation. Joining needs the same protocol on your game; Steam handles the update.
Is NovaCloud Rust resource validation up, and what does its uptime show?
NovaCloud Rust resource validation is offline at this refresh; the last response came 19 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 9 October 2026.
Where does NovaCloud Rust resource validation sit?
For NovaCloud Rust resource validation, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 43.254.45.56:50430.
Rules, settings, map
Which rules apply on NovaCloud Rust resource validation, and what settings?
You will not find a gather rate in the string NovaCloud Rust resource validation. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. Anti-cheat status: VAC on.
Which map has NovaCloud Rust resource validation selected?
A procedural map runs on NovaCloud Rust resource validation, generated by the game.
Wipe data
When does NovaCloud Rust resource validation wipe, and how often?
Too few wipes are on record for NovaCloud Rust resource validation to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 19 days 4 hours ago.
Lists and tags
Which lists on Rust Data hold NovaCloud Rust resource validation, and which filters?
These Rust Data lists include NovaCloud Rust resource validation: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on NovaCloud Rust resource validation hold?
These tags are published by NovaCloud Rust resource validation and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): 2 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join NovaCloud Rust resource validation?
The manual route: launch Rust, F1, then client.connect 43.254.45.56:50430. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.