Offline 84.133.6.143:28015 checked 28d ago
TestServer
Connect
srv = rust.server("84.133.6.143:28016")
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 67% 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 | Wed 30 Sep, 15:44 UTC28d 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
- 84.133.6.143:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 30 Sep 2026, 19:05 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 · 156 on average | 46/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 45/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 44/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Player counts
How does TestServer compare in the rankings?
Rank #16,026 on seven-day player hours for TestServer, within the top 67% of all ranked servers.
How full does TestServer run?
Offline now for TestServer, with the last sample 28 days 4 hours ago.
About the server
Which Rust version is TestServer on?
The build is Rust network protocol 2633 and build 165217 on Windows, run by TestServer. Steam updates your game for you, but the protocol must match to join.
How reliable is TestServer, and is it up?
TestServer is offline at this refresh; the last response came 28 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 29 September 2026.
Where does TestServer sit?
No region is published by TestServer. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 84.133.6.143:28015 is its address.
Settings and map
Which rules apply on TestServer, and what settings?
The name TestServer carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. 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 off.
Which map has TestServer selected?
A procedural map runs on TestServer, generated by the game.
Wipes and dates
When does TestServer wipe, and how often?
Too few wipes are on record for TestServer to reveal its rhythm. 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 28 days 5 hours ago.
On TestServer, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does TestServer appear among Rust Data lists and filters?
On Rust Data, TestServer 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 TestServer hold?
These tags are published by TestServer and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to TestServer?
In Rust, F1 opens the console: type client.connect 84.133.6.143:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.