Offline 85.193.2.190:28015 checked 42d ago
pepega
Connect
srv = rust.server("85.193.2.190: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
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.190:28015
- region
- –
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Sep 2026, 06:30 UTC
- hostname
- –
- first seen
- 15 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 · 158 on average | 62/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 62/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 28/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 9/1000 |
Quick answers
From the figures on this page.
Population data
What position does pepega take in the server rankings?
Rank #15,416 on seven-day player hours for pepega, within the top – of all ranked servers.
How many players does pepega hold at once?
The current row shows pepega offline; the last response was 42 days 16 hours ago.
About the server
Which Rust version is pepega on?
Rust network protocol 2633 and build 163493 on Windows is what pepega runs. Steam updates your game for you, but the protocol must match to join.
Is pepega up, and what does its uptime show?
pepega is offline at this refresh; the last response came 42 days 16 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 15 September 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. You can reach it at 85.193.2.190:28015.
Map and rules
Which settings and rules does pepega run?
No gather rate appears in the name: pepega. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has pepega selected?
The game generates its map: procedural, on pepega.
Wipes and dates
When does pepega wipe, and how often?
A rhythm cannot be read from the wipes of pepega 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 51 days 23 hours ago.
Tags and filters
Which Rust Data filters and lists contain pepega?
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?
These tags are published by pepega and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp250 (Max players): 250 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163493 (Build): The server runs build 163493; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed 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.190:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.