Offline 79.177.135.111:28015 checked 8h ago
Viper
Connect
srv = rust.server("79.177.135.111: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 44% 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
- 79.177.135.111:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 16:40 UTC
- hostname
- –
- first seen
- 27 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 · 152 on average | 41/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 0/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 16/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Viper take in the server rankings?
Rank #9,693 on seven-day player hours for Viper, within the top 44% of all ranked servers.
How full does Viper run?
The current row shows Viper offline; the last response was 8 hours ago. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 10:00 UTC, averaging 1 players.
Server data
What is the Rust version on Viper?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Viper. Steam updates your game for you, but the protocol must match to join.
Is Viper up, and what does its uptime show?
Viper is offline at this refresh; the last response came 8 hours ago. Over the last 1 full day the hours up number 12 of 24, 50%. Its earliest recorded date in Rust Data is 27 October 2026.
In which location is Viper hosted?
For Viper, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 79.177.135.111:28015.
Settings and map
Which rules apply on Viper, and what settings?
No gather rate appears in the name: Viper. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on Viper?
Viper runs a procedural map, which the game generates.
Wipe data
When does Viper wipe, and how often?
A rhythm cannot be read from the wipes of Viper on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 36 hours ago, and that is the one in play.
Tags, lists
Where does Viper appear among Rust Data lists and filters?
The Rust Data lists that Viper fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on Viper?
The game's server browser reads these tags from Viper: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Viper?
In Rust, F1 opens the console: type client.connect 79.177.135.111:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.