Offline 85.193.2.122:28015 checked 31d ago
pepega
Connect
srv = rust.server("85.193.2.122: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
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.122:28015
- region
- –
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Sep 2026, 06:30 UTC
- hostname
- –
- first seen
- 26 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 | 81/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 87/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 · 87 on average | 84/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 22/1000 |
Quick answers
From the figures on this page.
Population data
What position does pepega take in the server rankings?
Player hours over seven days put pepega at #15,930, in the top 69% of the ranked set.
How many players does pepega hold at once?
Offline now for pepega, with the last sample 31 days 16 hours ago.
About the server
What is the Rust version on pepega?
Rust network protocol 2633 and build 165217 on Windows is what pepega runs. The protocol has to match before you can join, and Steam does the updating.
Is pepega up, and what does its uptime show?
Offline now for pepega, last seen 31 days 16 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 26 September 2026.
Which location does pepega run from?
There is no region published for pepega. Rust Data does not look up where the machine stands; it shows where a server says it is. 85.193.2.122:28015 is its address.
Map and rules
Which settings and rules does pepega run?
You will not find a gather rate in the string pepega. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. 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. Anti-cheat status: VAC on.
Which map has pepega selected?
The game generates its map: procedural, on pepega.
Wipes and dates
When does pepega wipe, and how often?
Too few wipes are on record for pepega to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 51 days 16 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?
The game's server browser reads these tags from pepega: gmrust (Game mode): Rust survival in its standard form; mp250 (Max players): The server lists 250 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; 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): Modded listing: the game is changed by plugins or settings. 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 pepega?
Enter client.connect 85.193.2.122:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.