Online 157.85.94.33:20552 checked 12m ago
Private - Raid Type Test
Connect
srv = rust.server("157.85.94.33:20553")
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, measured since 15 Oct. 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 61% 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 2, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 14:55 UTC14d ago | 2 | 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
3000 · seed 1337
- map
- Procedural Map
- size
- 3000
- seed
- 1337
Server
srv.info()- address
- 157.85.94.33:20552
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 14:55 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 · 149 on average | 186/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.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 · 118 on average | 179/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 91/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 284/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 236/700 |
Quick answers
From the figures on this page.
Player counts
What position does Private - Raid Type Test take in the server rankings?
Over the last seven days Private - Raid Type Test sits at #13,641 on player hours, in the top 61% of ranked servers.
How full does Private - Raid Type Test run?
The sample now reads 0 players for Private - Raid Type Test, out of 5 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 18:00 UTC is the busiest, at 1 players.
Server facts
How smoothly does Private - Raid Type Test run?
The 48-hour average is 191 server fps, with a low of 142. Buildings, deployables and all else in the world took the count as high as 47,347 entities. Memory peaked at 4,954 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on Private - Raid Type Test?
Rust network protocol 2635 and build 167781 on Linux is what Private - Raid Type Test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Private - Raid Type Test, and is it up?
Private - Raid Type Test reports itself online at the current refresh. A restart about 31 minutes ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 15 October 2026.
Which location does Private - Raid Type Test run from?
There is no region published for Private - Raid Type Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 157.85.94.33:20552 is its address.
Map and rules
What rules and settings are recorded for Private - Raid Type Test?
The name Private - Raid Type Test 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. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Private - Raid Type Test?
The game generates the map on Private - Raid Type Test: procedural, size 3,000, seed 1337. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does Private - Raid Type Test wipe, and how often?
The record for Private - Raid Type Test holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 14 days ago.
On Private - Raid Type Test, what happens on wipe day?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 2 hours in.
Tags and filters
Where does Private - Raid Type Test appear among Rust Data lists and filters?
These Rust Data lists include Private - Raid Type Test: 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.
Which meanings do the tags on Private - Raid Type Test hold?
Read by the game's server browser, the tags Private - Raid Type Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join Private - Raid Type Test?
Enter client.connect 157.85.94.33:20552 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.