Offline 106.156.231.73:28016 checked 16h ago
NINJA WORKS Server
Connect
srv = rust.server("106.156.231.73: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 23% 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 2, 24 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 08:17 UTC8d ago | 2 | NaN | running | 1 |
| 1 | Mon 19 Oct, 03:00 UTC10d ago | 1 | NaN | 1.2 days | 1 |
| 2 | Thu 1 Oct, 19:09 UTC FW27d ago | 1 | held half | 17.3 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 106.156.231.73:28016
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 08:17 UTC
- hostname
- –
- first seen
- 15 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 · 152 on average | 44/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 62/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 18/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 4/1000 |
Quick answers
From the figures on this page.
Population
How does NINJA WORKS Server compare in the rankings?
Player hours over seven days put NINJA WORKS Server at #5,191, in the top 23% of the ranked set.
How many players does NINJA WORKS Server hold at once?
Offline now for NINJA WORKS Server, with the last sample 16 hours ago. Over the last seven days it averaged 1 players and peaked at 2. Peak hour in the last 48 hours: 12:00 UTC, mean 1 players.
Server facts
What is the Rust version on NINJA WORKS Server?
Rust network protocol 2635 and build 168909 on Windows is what NINJA WORKS Server runs. Steam updates your game for you, but the protocol must match to join.
Is NINJA WORKS Server up, and what does its uptime show?
The latest sample has NINJA WORKS Server offline, with a last sighting 16 hours ago. Uptime of 22% across the last 7 full days: 37 hours of 168. Its earliest recorded date in Rust Data is 15 September 2026.
In which location is NINJA WORKS Server hosted?
For NINJA WORKS Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 106.156.231.73:28016 is its address.
Map and rules
What rules and settings are recorded for NINJA WORKS Server?
You will not find a gather rate in the string NINJA WORKS Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on NINJA WORKS Server?
NINJA WORKS Server runs a procedural map, which the game generates.
Wipe schedule
When does NINJA WORKS Server wipe, and on what schedule?
NINJA WORKS Server wipes on no fixed rhythm, so there is nothing to predict. 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 8 days 21 hours ago.
What is wipe day on NINJA WORKS Server like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 24 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags and filters
Where does NINJA WORKS Server appear among Rust Data lists and filters?
These Rust Data lists include NINJA WORKS Server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on NINJA WORKS Server?
The game's server browser reads these tags from NINJA WORKS Server: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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
What is the way to join NINJA WORKS Server?
Enter client.connect 106.156.231.73:28016 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.