Offline 84.32.48.20:28015 checked 22d ago
TEST Server
Connect
srv = rust.server("84.32.48.20: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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 5 Oct, 14:42 UTC22d ago | 1 | NaN | running | 1 |
| 1 | Fri 2 Oct, 11:49 UTC25d ago | 1 | NaN | 3.1 days | 1 |
| 2 | Thu 24 Sep, 19:05 UTC33d ago | 1 | held half | 7.7 days | 1 |
| 3 | Tue 22 Sep, 16:35 UTC35d ago | 1 | held half | 2.1 days | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 84.32.48.20:28015
- region
- –
- max players
- 150
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 16:38 UTC
- hostname
- –
- first seen
- 21 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 · 160 on average | 42/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 47/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 18/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 5/1000 |
Quick answers
From the figures on this page.
Population data
How does TEST Server compare in the rankings?
Rank #15,497 on seven-day player hours for TEST Server, within the top 69% of all ranked servers.
How full does TEST Server run?
Offline now for TEST Server, with the last sample 22 days 10 hours ago.
Server data
What Rust version does TEST Server run?
Version Rust network protocol 2634 and build 166586 on Windows is reported by TEST Server. The protocol has to match before you can join, and Steam does the updating.
Is TEST Server up, and what does its uptime show?
Offline now for TEST Server, last seen 22 days 10 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 21 September 2026.
Where does TEST Server sit?
There is no region published for TEST Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 84.32.48.20:28015 is its address.
Map and rules
Which rules apply on TEST Server, and what settings?
You will not find a gather rate in the string TEST Server. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe data
When does TEST Server wipe, and on what schedule?
No next wipe can be predicted for TEST Server, which wipes at irregular times. 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 22 days 10 hours ago, and that is the one in play.
On TEST Server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags and filters
Which Rust Data filters and lists contain TEST Server?
On Rust Data, TEST Server appears in these lists: 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.
How should you read the server tags on TEST Server?
These tags are published by TEST Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): The server lists 150 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): The server runs build 166586; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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. 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 TEST Server?
The manual route: launch Rust, F1, then client.connect 84.32.48.20:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.