Online 82.223.22.21:23400 checked 7m ago
4Netplayers Jungle Server Test
Connect
srv = rust.server("82.223.22.21:23404")
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, measured since 29 Sep. 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 29% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 14h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 14h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 14h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:03 UTC FW27d ago | 1 | NaN | running | 0 |
# 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
6000 · seed 1234567890
- map
- Procedural Map
- size
- 6000
- seed
- 1234567890
Server
srv.info()- address
- 82.223.22.21:23400
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:03 UTC
- hostname
- –
- first seen
- 29 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 · 153 on average | 33/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 49/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Population data
How does 4Netplayers Jungle Server Test compare in the rankings?
Over the last seven days 4Netplayers Jungle Server Test sits at #6,381 on player hours, in the top 29% of ranked servers.
How full does 4Netplayers Jungle Server Test run?
4Netplayers Jungle Server Test reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players and peaked at 2. Peak hour in the last 48 hours: 17:00 UTC, mean 1 players.
Server facts
What does performance look like on 4Netplayers Jungle Server Test?
Averaged over 48 hours: 30 server fps, never under 30. The entity count peaked at 204,777, covering buildings, deployables and the rest of the world. Memory peaked at 4,388 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is 4Netplayers Jungle Server Test on?
Rust network protocol 2635 and build 168909 on Linux is what 4Netplayers Jungle Server Test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is 4Netplayers Jungle Server Test, and is it online now?
Online is the state at the latest refresh for 4Netplayers Jungle Server Test. A restart about 22 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 29 September 2026.
Where does 4Netplayers Jungle Server Test sit?
For 4Netplayers Jungle Server Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 82.223.22.21:23400 is its address.
Map and rules
What rules and settings are recorded for 4Netplayers Jungle Server Test?
The name 4Netplayers Jungle Server Test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has 4Netplayers Jungle Server Test loaded?
The game generates the map on 4Netplayers Jungle Server Test: procedural, size 6,000, seed 1234567890. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
On what schedule does 4Netplayers Jungle Server Test wipe?
A single wipe each month, the force wipe, is all 4Netplayers Jungle Server Test does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 27 days 9 hours ago.
What is wipe day on 4Netplayers Jungle Server Test like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which Rust Data filters and lists contain 4Netplayers Jungle Server Test?
The Rust Data lists that 4Netplayers Jungle Server Test fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on 4Netplayers Jungle Server Test?
Read by the game's server browser, the tags 4Netplayers Jungle Server Test publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp10 (Max players): 10 slots in total; 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): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 4Netplayers Jungle Server Test?
The manual route: launch Rust, F1, then client.connect 82.223.22.21:23400. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.