Offline 85.190.161.19:10200 checked 15d ago
Maeddy's Russerver
Connect
srv = rust.server("85.190.161.19:10201")
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 17 Sep. 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 71% 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 8d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 23h | 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, 17:54 UTC FW26d 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
4000 · seed 47156
- map
- Procedural Map
- size
- 4000
- seed
- 47156
Server
srv.info()- address
- 85.190.161.19:10200
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:54 UTC
- hostname
- –
- first seen
- 13 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 · 163 on average | 207/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 186/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 32/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 85 on average | 179/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 60/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Maeddy's Russerver take in the server rankings?
Over the last seven days Maeddy's Russerver sits at #15,568 on player hours, in the top 71% of ranked servers.
What population does Maeddy's Russerver carry?
Maeddy's Russerver returns no live count at this refresh, having last been seen 15 days 12 hours ago.
Server facts
What Rust version does Maeddy's Russerver run?
Rust network protocol 2634 and build 167398 on Windows is what Maeddy's Russerver runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Maeddy's Russerver, and is it up?
Maeddy's Russerver is offline at this refresh; the last response came 15 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does Maeddy's Russerver run from?
No region is published by Maeddy's Russerver. 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 85.190.161.19:10200.
Settings and map
Which settings and rules does Maeddy's Russerver run?
No gather rate appears in the name: Maeddy's Russerver. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Maeddy's Russerver?
Maeddy's Russerver runs a procedural map of size 4,000 with seed 47156, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
On what schedule does Maeddy's Russerver wipe?
A single wipe each month, the force wipe, is all Maeddy's Russerver 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 26 days 1 hours ago.
What is wipe day on Maeddy's Russerver like?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain Maeddy's Russerver?
These Rust Data lists include Maeddy's Russerver: 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.
Which meanings do the tags on Maeddy's Russerver hold?
Read by the game's server browser, the tags Maeddy's Russerver publishes are: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): The server runs build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Maeddy's Russerver?
Enter client.connect 85.190.161.19:10200 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.
