Offline 46.181.239.168:27015 checked 8d ago
TestServerRust - AgentRustService Monitor
Connect
srv = rust.server("46.181.239.168:27016")
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 70% of all ranked servers. Ranked on player hours over the last seven days.
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
- 46.181.239.168:27015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 09:33 UTC
- hostname
- –
- first seen
- 15 Oct 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 · 154 on average | 19/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 34/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 | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TestServerRust - AgentRustService Monitor rank?
Rank #15,383 on seven-day player hours for TestServerRust - AgentRustService Monitor, within the top 70% of all ranked servers.
How full does TestServerRust - AgentRustService Monitor run?
TestServerRust - AgentRustService Monitor returns no live count at this refresh, having last been seen 8 days 7 hours ago.
Server facts
What is the Rust version on TestServerRust - AgentRustService Monitor?
Rust network protocol 2634 and build 167781 on Windows is what TestServerRust - AgentRustService Monitor runs. Steam updates your game for you, but the protocol must match to join.
How reliable is TestServerRust - AgentRustService Monitor, and is it up?
Offline now for TestServerRust - AgentRustService Monitor, last seen 8 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 15 October 2026.
Where does TestServerRust - AgentRustService Monitor sit?
For TestServerRust - AgentRustService Monitor, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 46.181.239.168:27015 is its address.
Settings and map
What rules and settings are recorded for TestServerRust - AgentRustService Monitor?
No gather rate appears in the name: TestServerRust - AgentRustService Monitor. The group limit sits at the default of 8 players. 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. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has TestServerRust - AgentRustService Monitor selected?
A procedural map runs on TestServerRust - AgentRustService Monitor, generated by the game.
Wipe data
When does TestServerRust - AgentRustService Monitor wipe, and on what schedule?
A rhythm cannot be read from the wipes of TestServerRust - AgentRustService Monitor 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. This world was created 13 days 17 hours ago.
Tags and filters
Which Rust Data filters and lists contain TestServerRust - AgentRustService Monitor?
The Rust Data lists that TestServerRust - AgentRustService Monitor fits are: 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 TestServerRust - AgentRustService Monitor?
Read by the game's server browser, the tags TestServerRust - AgentRustService Monitor publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; jp0 (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join TestServerRust - AgentRustService Monitor?
Enter client.connect 46.181.239.168:27015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.