Online 88.99.24.242:41218 checked 10m ago
monster-vip3-10-23-2002
Connect
srv = rust.server("88.99.24.242:41219")
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 1 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 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 15h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 15h | 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 22:00 UTC FW27d ago | 0 | 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
2500 · seed 1337
- map
- Procedural Map
- size
- 2500
- seed
- 1337
Server
srv.info()- address
- 88.99.24.242:41218
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 22:00 UTC
- hostname
- –
- first seen
- 1 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 555 on average | 141/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 115/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 14/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 286 on average | 19/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 11/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 250 on average | 18/200 |
Quick answers
From the figures on this page.
Population data
How does monster-vip3-10-23-2002 compare in the rankings?
Player hours over seven days put monster-vip3-10-23-2002 at #15,358, in the top 69% of the ranked set.
How full does monster-vip3-10-23-2002 run?
The sample now reads 0 players for monster-vip3-10-23-2002, out of 1 slots. Over the last seven days it averaged 0 players.
Server data
What does performance look like on monster-vip3-10-23-2002?
Server fps over the last 48 hours averages 238; the floor is 228. The entity count peaked at 28,248, covering buildings, deployables and the rest of the world. A high of 2,138 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What Rust version does monster-vip3-10-23-2002 run?
The build is Rust network protocol 2634 and build 166494 on Linux, run by monster-vip3-10-23-2002. The protocol has to match before you can join, and Steam does the updating.
How reliable is monster-vip3-10-23-2002, and is it up?
Online is the state at the latest refresh for monster-vip3-10-23-2002. The uptime it reports puts the last restart about 6 days 14 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 1 October 2026.
Which location does monster-vip3-10-23-2002 run from?
For monster-vip3-10-23-2002, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 88.99.24.242:41218 is its address.
Rules, settings, map
Which settings and rules does monster-vip3-10-23-2002 run?
You will not find a gather rate in the string monster-vip3-10-23-2002. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
Which map has monster-vip3-10-23-2002 loaded?
monster-vip3-10-23-2002 runs a procedural map of size 2,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does monster-vip3-10-23-2002 wipe, and on what schedule?
A single wipe each month, the force wipe, is all monster-vip3-10-23-2002 does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 27 days 5 hours ago.
What is wipe day on monster-vip3-10-23-2002 like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does monster-vip3-10-23-2002 appear among Rust Data lists and filters?
The Rust Data lists that monster-vip3-10-23-2002 fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on monster-vip3-10-23-2002?
The game's server browser reads these tags from monster-vip3-10-23-2002: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join monster-vip3-10-23-2002?
Enter client.connect 88.99.24.242:41218 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.