Statistical profileOffline
NINJA WORKS Server
106.156.231.73:28016 checked 17h ago
Connect to this server
1. Main points
Players now
1/ 100
1% full
7-day average
1
peak 2
Rank
#5,187
top 23%
Last wipe
8d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- The server is offline; at its last check there were 1 players on it, 1% of its 100 slots.
- Over the last seven days it averaged 1 players, with a peak of 2.
- It ranks #5,187 of all ranked servers, the top 23%, on player hours over the last seven days.
- Its current map went up 8d ago.
2. Players
Figure 1: Players on NINJA WORKS Server
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 23% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternno rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Usual gap
9.3 days
between real wipes
On rhythm
0%
of its recent wipes
Wipe-day peak
1
players, last three wipes
Crowd held
100%
of its cycles kept half the crowd
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 2, 24 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 20 Oct, 08:17 UTC8d ago | 2 | – | running | 1 |
| Mon 19 Oct, 03:00 UTC10d ago | 1 | – | 1.2 days | 1 |
| Thu 1 Oct, 19:09 UTC FW27d ago | 1 | held half | 17.3 days | 1 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of NINJA WORKS Server
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of NINJA WORKS Server
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 151 on average | 55 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 81 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 29 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6 / 1000 |
10. Quick answers
From the figures on this page.
Wipe records
On what schedule are wipes carried out on NINJA WORKS Server?
No next wipe can be predicted for NINJA WORKS Server, which wipes at irregular times. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. 8 days 22 hours have passed since this world was made.
How is wipe day run on NINJA WORKS Server?
An average of 1 players attended at peak across recent wipes. On the latest wipe, 24 hours passed before the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Server details
How reliable is NINJA WORKS Server, and is it online now?
The latest count records NINJA WORKS Server as offline, last seen 17 hours ago. 37 of 168 hours on across the last 7 full days gives an uptime of 22%. It was first seen by Rust Census on 15 September 2026.
What location has been recorded for NINJA WORKS Server?
No region is published by NINJA WORKS Server. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. At 106.156.231.73:28016 it is addressed.
On which Rust version does NINJA WORKS Server operate?
This release lists NINJA WORKS Server on Rust network protocol 2635 and build 168909, running on Windows. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
What are the current player figures for NINJA WORKS Server?
NINJA WORKS Server is offline at present; its last recording was 17 hours ago. This release records a seven-day average of 1 players and a peak of 2. Over the past 48 hours the highest average fell at 12:00 UTC: 1 players.
In the rankings of Rust servers, where is NINJA WORKS Server placed?
For seven-day player hours, NINJA WORKS Server is ranked #5,187, placing it in the top 23% of all ranked servers.
Tags, lists
On Rust Census, which lists and filters carry NINJA WORKS Server?
The Rust Census lists that NINJA WORKS Server fits are: Modded Rust servers, counted. 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.
Which meanings do the tags on NINJA WORKS Server carry?
These are the tags NINJA WORKS Server publishes for the game's server browser to read: gmrust (Game mode): Survival play, in the standard Rust format; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): This server carries no region code; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Plugins or settings alter the game on this modded server. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
Which map has been recorded for NINJA WORKS Server?
The game generates the procedural map on NINJA WORKS Server.
What settings and rules have been listed for NINJA WORKS Server?
No gather rate is recorded for NINJA WORKS Server in its name. The group cap stands at 8 players, the default for the game. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it under Modded. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Join details
What steps are needed to join NINJA WORKS Server?
Enter client.connect 106.156.231.73:28016 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp100 | Max players The server holds 100 slots. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build Game build: 168909. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code This server carries no region code. |
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded Plugins or settings alter the game on this modded server. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.