Offline 98.240.242.148:28015 checked 27d ago
Siege Dev [siege-dev]
Connect
srv = rust.server("98.240.242.148: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 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 3h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 3h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 3h | 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 21:12 UTC FW27d 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
- 98.240.242.148:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:12 UTC
- hostname
- –
- first seen
- 15 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 · 149 on average | 171/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 82/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 351/350 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 249/700 |
Quick answers
From the figures on this page.
Population data
What position does Siege Dev [siege-dev] take in the server rankings?
Over the last seven days Siege Dev [siege-dev] sits at #15,938 on player hours, in the top 69% of ranked servers.
How many players does Siege Dev [siege-dev] hold at once?
Offline now for Siege Dev [siege-dev], with the last sample 27 days 13 hours ago.
Server facts
Which Rust version is Siege Dev [siege-dev] on?
Rust network protocol 2634 and build 166494 on Windows is what Siege Dev [siege-dev] runs. Steam updates your game for you, but the protocol must match to join.
Is Siege Dev [siege-dev] up, and what does its uptime show?
Siege Dev [siege-dev] is offline at this refresh; the last response came 27 days 13 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 15 September 2026.
Which location does Siege Dev [siege-dev] run from?
No region is published by Siege Dev [siege-dev]. 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 98.240.242.148:28015.
Settings and map
Which settings and rules does Siege Dev [siege-dev] run?
No gather rate appears in the name: Siege Dev [siege-dev]. 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. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Siege Dev [siege-dev] selected?
The game generates its map: procedural, on Siege Dev [siege-dev].
Wipe data
When does Siege Dev [siege-dev] wipe, and how often?
Once a month Siege Dev [siege-dev] wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 18 hours ago, and that is the one in play.
What is wipe day on Siege Dev [siege-dev] like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold Siege Dev [siege-dev], and which filters?
The Rust Data lists that Siege Dev [siege-dev] fits are: 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 Siege Dev [siege-dev] hold?
The game's server browser reads these tags from Siege Dev [siege-dev]: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into Siege Dev [siege-dev]?
Enter client.connect 98.240.242.148:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.