Offline 85.193.2.18:28015 checked 19d ago
pepega
Connect
srv = rust.server("85.193.2.18: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 bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 85.193.2.18:28015
- region
- –
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 17:57 UTC
- hostname
- –
- first seen
- 8 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 · 162 on average | 30/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 43/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 33/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 9/200 |
| 5 | CSL Scenery Budget Test | groups of 8+ · 85 on average | 0/500 |
Quick answers
From the figures on this page.
Population
What position does pepega take in the server rankings?
Player hours over seven days put pepega at #15,843, in the top 72% of the ranked set.
How many players does pepega hold at once?
pepega returns no live count at this refresh, having last been seen 19 days 8 hours ago.
Server facts
Which Rust version is pepega on?
The build is Rust network protocol 2634 and build 167058 on Windows, run by pepega. Steam updates your game for you, but the protocol must match to join.
How reliable is pepega, and is it up?
Offline now for pepega, last seen 19 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 8 October 2026.
Where does pepega sit?
There is no region published for pepega. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 85.193.2.18:28015 is its address.
Map and rules
Which settings and rules does pepega run?
No gather rate appears in the name: pepega. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has pepega selected?
pepega runs a procedural map, which the game generates.
Wipes and dates
When does pepega wipe, and how often?
Too few wipes are on record for pepega to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 24 days 7 hours ago.
Lists and tags
Where does pepega appear among Rust Data lists and filters?
These Rust Data lists include pepega: 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.
How should you read the server tags on pepega?
The game's server browser reads these tags from pepega: gmrust (Game mode): Survival play, standard Rust; mp250 (Max players): The server lists 250 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167058 (Build): Recorded game build: 167058; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to pepega?
Enter client.connect 85.193.2.18:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.