Offline 176.119.83.182:28015 checked 32d ago
NEXUS TEST
Connect
srv = rust.server("176.119.83.182: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 69% 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
- 176.119.83.182:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 19:36 UTC
- hostname
- –
- first seen
- 26 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 · 157 on average | 88/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 91/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 76/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 23/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 16/1000 |
Quick answers
From the figures on this page.
Population
What position does NEXUS TEST take in the server rankings?
Over the last seven days NEXUS TEST sits at #16,081 on player hours, in the top 69% of ranked servers.
How many players does NEXUS TEST hold at once?
Offline now for NEXUS TEST, with the last sample 32 days 1 hours ago.
Server facts
What is the Rust version on NEXUS TEST?
Rust network protocol 2633 and build 165217 on Windows is what NEXUS TEST runs. The protocol has to match before you can join, and Steam does the updating.
Is NEXUS TEST up, and what does its uptime show?
The latest sample has NEXUS TEST offline, with a last sighting 32 days 1 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 26 September 2026.
Where does NEXUS TEST sit?
There is no region published for NEXUS TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 176.119.83.182:28015.
Rules, settings, map
What rules and settings are recorded for NEXUS TEST?
You will not find a gather rate in the string NEXUS TEST. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has NEXUS TEST loaded?
A procedural map runs on NEXUS TEST, generated by the game.
Wipe schedule
On what schedule does NEXUS TEST wipe?
Too few wipes are on record for NEXUS TEST 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 32 days 2 hours ago.
Tags and filters
Which lists on Rust Data hold NEXUS TEST, and which filters?
The Rust Data lists that NEXUS TEST fits are: 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.
How should you read the server tags on NEXUS TEST?
The game's server browser reads these tags from NEXUS TEST: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. 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
How can I connect to NEXUS TEST?
Enter client.connect 176.119.83.182:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.