Online 50.52.170.193:28015 checked 10m ago
Rustic-Runners
Connect
srv = rust.server("50.52.170.193: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. 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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 21:50 UTC6d 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 50.52.170.193:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 21:50 UTC
- hostname
- –
- first seen
- 21 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 · 149 on average | 132/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 192/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 71/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 9/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 21/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Rustic-Runners take in the server rankings?
Player hours over seven days put Rustic-Runners at #15,335, in the top 69% of the ranked set.
How many players does Rustic-Runners hold at once?
The sample now reads 0 players for Rustic-Runners, out of 100 slots. Over the last seven days it averaged 0 players.
About the server
Which Rust version is Rustic-Runners on?
Rust network protocol 2635 and build 168909 on Windows is what Rustic-Runners runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Rustic-Runners, and is it online now?
Online is the state at the latest refresh for Rustic-Runners. Uptime of 87% across the last 7 full days: 146 hours of 168. Rust Data logged it first on 21 October 2026.
Which location does Rustic-Runners run from?
There is no region published for Rustic-Runners. Rust Data does not look up where the machine stands; it shows where a server says it is. 50.52.170.193:28015 is its address.
Rules, settings, map
Which rules apply on Rustic-Runners, and what settings?
The name Rustic-Runners carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Rustic-Runners selected?
Rustic-Runners runs a procedural map, which the game generates.
Wipe data
When does Rustic-Runners wipe, and on what schedule?
A rhythm cannot be read from the wipes of Rustic-Runners on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 6 days 12 hours ago.
On Rustic-Runners, what happens on wipe day?
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 Rustic-Runners appear among Rust Data lists and filters?
On Rust Data, Rustic-Runners appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on Rustic-Runners hold?
The game's server browser reads these tags from Rustic-Runners: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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.
Connecting
What is the way to join Rustic-Runners?
The manual route: launch Rust, F1, then client.connect 50.52.170.193:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.