Offline 86.165.241.219:28015 checked 43d ago
PARADOX-ESP-TEST
Connect
srv = rust.server("86.165.241.219: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 best
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
- 86.165.241.219:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Sep 2026, 05:06 UTC
- hostname
- –
- first seen
- 16 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 · 149 on average | 109/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 · 118 on average | 167/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 50/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 | 25/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does PARADOX-ESP-TEST rank?
Over the last seven days PARADOX-ESP-TEST sits at #13,326 on player hours, in the top – of ranked servers.
How full does PARADOX-ESP-TEST run?
Offline now for PARADOX-ESP-TEST, with the last sample 43 days 4 hours ago.
About the server
What Rust version does PARADOX-ESP-TEST run?
Version Rust network protocol 2633 and build 163794 on Windows is reported by PARADOX-ESP-TEST. Steam updates your game for you, but the protocol must match to join.
How reliable is PARADOX-ESP-TEST, and is it up?
Offline now for PARADOX-ESP-TEST, last seen 43 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 16 September 2026.
Where does PARADOX-ESP-TEST sit?
For PARADOX-ESP-TEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 86.165.241.219:28015.
Map and rules
Which rules apply on PARADOX-ESP-TEST, and what settings?
No gather rate appears in the name: PARADOX-ESP-TEST. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. Anti-cheat status: VAC off.
Which map has PARADOX-ESP-TEST loaded?
PARADOX-ESP-TEST runs a procedural map, which the game generates.
Wipe data
On what schedule does PARADOX-ESP-TEST wipe?
A rhythm cannot be read from the wipes of PARADOX-ESP-TEST on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 43 days 4 hours ago, and that is the one in play.
Tags and filters
Which Rust Data filters and lists contain PARADOX-ESP-TEST?
On Rust Data, PARADOX-ESP-TEST appears in these lists: Modded Rust servers. These filters bring it up 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 PARADOX-ESP-TEST?
These tags are published by PARADOX-ESP-TEST and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Build number: 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into PARADOX-ESP-TEST?
In Rust, F1 opens the console: type client.connect 86.165.241.219:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.