Offline 193.117.69.190:28015 checked 39d ago
NAKA 4000
Connect
srv = rust.server("193.117.69.190: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 bestWipe 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
- 193.117.69.190:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Sep 2026, 08:31 UTC
- hostname
- –
- first seen
- 19 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 · 151 on average | 33/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 57/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 17/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 56/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 51/200 |
Quick answers
From the figures on this page.
Player counts
What position does NAKA 4000 take in the server rankings?
Over the last seven days NAKA 4000 sits at #13,280 on player hours, in the top – of ranked servers.
How full does NAKA 4000 run?
Offline now for NAKA 4000, with the last sample 39 days 20 hours ago.
About the server
Which Rust version is NAKA 4000 on?
Version Rust network protocol 2633 and build 162929 on Windows is reported by NAKA 4000. The protocol has to match before you can join, and Steam does the updating.
Is NAKA 4000 up, and what does its uptime show?
The latest sample has NAKA 4000 offline, with a last sighting 39 days 20 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 19 September 2026.
Where does NAKA 4000 sit?
No region is published by NAKA 4000. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 193.117.69.190:28015 is its address.
Settings and map
Which rules apply on NAKA 4000, and what settings?
The name NAKA 4000 carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has NAKA 4000 selected?
The game generates its map: procedural, on NAKA 4000.
Wipe schedule
On what schedule does NAKA 4000 wipe?
Too few wipes are on record for NAKA 4000 to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 40 days 22 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold NAKA 4000, and which filters?
On Rust Data, NAKA 4000 appears in these lists: 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.
How should you read the server tags on NAKA 4000?
The game's server browser reads these tags from NAKA 4000: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs162929 (Build): Build number: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^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 into NAKA 4000?
In Rust, F1 opens the console: type client.connect 193.117.69.190:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.