Offline 80.80.98.141:28015 checked 9d ago
DimaRND_Rust
Connect
srv = rust.server("80.80.98.141: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, measured since 11 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 best
Top 70% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 19:27 UTC15d ago | 2 | 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
4500 · seed 1872944127
- map
- Procedural Map
- size
- 4500
- seed
- 1872944127
Server
srv.info()- address
- 80.80.98.141:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 19:27 UTC
- hostname
- –
- first seen
- 11 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 · 163 on average | 48/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 61/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 58/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 17/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does DimaRND_Rust rank?
Player hours over seven days put DimaRND_Rust at #15,275, in the top 70% of the ranked set.
What population does DimaRND_Rust carry?
DimaRND_Rust returns no live count at this refresh, having last been seen 9 days 10 hours ago.
Server facts
What Rust version does DimaRND_Rust run?
Version Rust network protocol 2634 and build 167398 on Linux is reported by DimaRND_Rust. The protocol has to match before you can join, and Steam does the updating.
How reliable is DimaRND_Rust, and is it up?
DimaRND_Rust is offline at this refresh; the last response came 9 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 11 October 2026.
Which location does DimaRND_Rust run from?
For DimaRND_Rust, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 80.80.98.141:28015 is its address.
Map and rules
Which settings and rules does DimaRND_Rust run?
No gather rate appears in the name: DimaRND_Rust. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has DimaRND_Rust selected?
The game generates the map on DimaRND_Rust: procedural, size 4,500, seed 1872944127. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
On what schedule does DimaRND_Rust wipe?
The record for DimaRND_Rust holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 15 days 4 hours ago.
On DimaRND_Rust, what happens on wipe day?
The average peak over recent wipes is 2 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does DimaRND_Rust appear among Rust Data lists and filters?
On Rust Data, DimaRND_Rust appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on DimaRND_Rust?
These tags are published by DimaRND_Rust and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is 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.
Join steps
What is the way to join DimaRND_Rust?
The manual route: launch Rust, F1, then client.connect 80.80.98.141:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.