Online 135.106.169.149:28019 checked 9m ago
Test2 RUST
Connect
srv = rust.server("135.106.169.149:28021")
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 69% 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 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 1h | 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, 21:26 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 135.106.169.149:28019
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:26 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 · 151 on average | 149/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 193/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 96/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 225/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 345/350 |
Quick answers
From the figures on this page.
Player counts
What position does Test2 RUST take in the server rankings?
Over the last seven days Test2 RUST sits at #15,327 on player hours, in the top 69% of ranked servers.
How full does Test2 RUST run?
The sample now reads 0 players for Test2 RUST, out of 10 slots. Over the last seven days it averaged 0 players.
About the server
Which Rust version is Test2 RUST on?
The build is Rust network protocol 2634 and build 166494 on Windows, run by Test2 RUST. Steam updates your game for you, but the protocol must match to join.
Is Test2 RUST up, and what does its uptime show?
Test2 RUST reports itself online at the current refresh. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 29 September 2026.
Where does Test2 RUST sit?
No region is published by Test2 RUST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 135.106.169.149:28019 is its address.
Rules, settings, map
Which rules apply on Test2 RUST, and what settings?
The name Test2 RUST carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Test2 RUST?
The game generates its map: procedural, on Test2 RUST.
Wipe schedule
On what schedule does Test2 RUST wipe?
Once a month Test2 RUST wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 27 days 20 hours ago, and that is the one in play.
What is wipe day on Test2 RUST like?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does Test2 RUST appear among Rust Data lists and filters?
On Rust Data, Test2 RUST 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.
Which meanings do the tags on Test2 RUST hold?
The game's server browser reads these tags from Test2 RUST: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): The server runs build 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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.
Join steps
How can I connect to Test2 RUST?
In Rust, F1 opens the console: type client.connect 135.106.169.149:28019. Launch Rust on this page does the same by opening the game through Steam and connecting.