Offline 85.193.2.195:28015 checked 25d ago
pepega
Connect
srv = rust.server("85.193.2.195: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 64% 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 85.193.2.195:28015
- region
- –
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 19:00 UTC
- hostname
- –
- first seen
- 2 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 | 132/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 | 14/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does pepega rank?
Over the last seven days pepega sits at #14,526 on player hours, in the top 64% of ranked servers.
How full does pepega run?
The current row shows pepega offline; the last response was 25 days 4 hours ago.
Server facts
What Rust version does pepega run?
Rust network protocol 2634 and build 166586 on Windows is what pepega runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is pepega, and is it online now?
The latest sample has pepega offline, with a last sighting 25 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 2 October 2026.
Which location does pepega run from?
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.195:28015 is its address.
Rules, settings, map
Which rules apply on pepega, and what settings?
No gather rate appears in the name: pepega. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Wipe data
When does pepega wipe, and how often?
The record for pepega 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. The world it runs now was generated 25 days 5 hours ago.
Lists and tags
Where does pepega appear among Rust Data lists and filters?
On Rust Data, pepega 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.
How should you read the server tags on pepega?
These tags are published by pepega and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp250 (Max players): The server lists 250 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Connecting
What is the way into pepega?
In Rust, F1 opens the console: type client.connect 85.193.2.195:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.