Offline 85.193.2.118:28015 checked 23d ago
pepega
Connect
srv = rust.server("85.193.2.118: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 61% 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.118:28015
- region
- –
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 17:57 UTC
- hostname
- –
- first seen
- 4 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 · 160 on average | 39/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 | 49/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 19/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 7/1000 |
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 #13,757, in the top 61% of the ranked set.
How full does pepega run?
Offline now for pepega, with the last sample 23 days 9 hours ago.
About the server
What Rust version does pepega run?
The build is Rust network protocol 2634 and build 166586 on Windows, run by pepega. The protocol has to match before you can join, and Steam does the updating.
How reliable is pepega, and is it up?
pepega is offline at this refresh; the last response came 23 days 9 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 4 October 2026.
Where does pepega sit?
For pepega, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 85.193.2.118:28015 is its address.
Map and rules
Which rules apply on pepega, and what settings?
The name pepega carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on pepega?
A procedural map runs on pepega, generated by the game.
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. The world it runs now was generated 24 days 9 hours ago.
Tags, lists
Where does pepega appear among Rust Data lists and filters?
The Rust Data lists that pepega fits are: 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?
Read by the game's server browser, the tags pepega publishes are: gmrust (Game mode): Survival play, standard Rust; mp250 (Max players): Slot count: 250; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): The server runs build 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^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.
Join steps
What is the way into pepega?
In Rust, F1 opens the console: type client.connect 85.193.2.118:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.