Offline 91.8.202.37:28015 checked 1d ago
Rip_Was Test Server
Connect
srv = rust.server("91.8.202.37: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 51% 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 | Fri 23 Oct, 14:24 UTC5d 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
- 91.8.202.37:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 14:24 UTC
- hostname
- –
- first seen
- 4 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 · 155 on average | 32/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 30/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 24/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 4/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Rip_Was Test Server rank?
Player hours over seven days put Rip_Was Test Server at #11,353, in the top 51% of the ranked set.
How many players does Rip_Was Test Server hold at once?
Offline now for Rip_Was Test Server, with the last sample 28 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 21:00 UTC is the busiest, at 1 players.
Server data
Which Rust version is Rip_Was Test Server on?
Rust network protocol 2635 and build 168909 on Windows is what Rip_Was Test Server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Rip_Was Test Server, and is it online now?
Offline now for Rip_Was Test Server, last seen 28 hours ago. Over the last 7 full days the hours up number 4 of 168, 2%. Its earliest recorded date in Rust Data is 4 October 2026.
Which location does Rip_Was Test Server run from?
For Rip_Was Test Server, 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. You can reach it at 91.8.202.37:28015.
Rules, settings, map
What rules and settings are recorded for Rip_Was Test Server?
No gather rate appears in the name: Rip_Was Test Server. 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. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Rip_Was Test Server selected?
The game generates its map: procedural, on Rip_Was Test Server.
Wipes and dates
When does Rip_Was Test Server wipe, and on what schedule?
Too few wipes are on record for Rip_Was Test Server to reveal its 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 5 days 11 hours ago.
On Rip_Was Test Server, 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 Rip_Was Test Server appear among Rust Data lists and filters?
On Rust Data, Rip_Was Test Server 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; Last wipe: In the last week.
How should you read the server tags on Rip_Was Test Server?
These tags are published by Rip_Was Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is 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.
How to join
What is the way into Rip_Was Test Server?
In Rust, F1 opens the console: type client.connect 91.8.202.37:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.