Offline 212.102.62.170:28015 checked 11d ago
PluginTest
Connect
srv = rust.server("212.102.62.170: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 bestTop 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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 | Sun 18 Oct, 11:26 UTC11d ago | 1 | NaN | running | 1 |
# 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
- 212.102.62.170:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 11:33 UTC
- hostname
- –
- first seen
- 18 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 · 149 on average | 174/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 · 119 on average | 143/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 62/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 85 on average | 241/700 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does PluginTest rank?
Over the last seven days PluginTest sits at #13,024 on player hours, in the top 59% of ranked servers.
How many players does PluginTest hold at once?
The current row shows PluginTest offline; the last response was 11 days 1 hours ago.
Server data
What is the Rust version on PluginTest?
The build is Rust network protocol 2634 and build 167781 on Windows, run by PluginTest. Joining needs the same protocol on your game; Steam handles the update.
How reliable is PluginTest, and is it up?
The latest sample has PluginTest offline, with a last sighting 11 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 18 October 2026.
In which location is PluginTest hosted?
For PluginTest, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 212.102.62.170:28015 is its address.
Settings and map
What rules and settings are recorded for PluginTest?
You will not find a gather rate in the string PluginTest. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.
Which map has PluginTest selected?
PluginTest runs a procedural map, which the game generates.
Wipe schedule
When does PluginTest wipe, and how often?
Too few wipes are on record for PluginTest 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 11 days 3 hours ago, and that is the one in play.
On PluginTest, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain PluginTest?
These Rust Data lists include PluginTest: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on PluginTest?
These tags are published by PluginTest and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): Slot count: 500; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to PluginTest?
The manual route: launch Rust, F1, then client.connect 212.102.62.170:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.