Offline 77.162.166.238:28015 checked 4d ago
sigma 67
Connect
srv = rust.server("77.162.166.238:28017")
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 35% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in, with 1 in the queue.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 23:02 UTC4d ago | 3+1 queue | NaN | running | 0 |
# 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
- 77.162.166.238:28015
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 00:42 UTC
- hostname
- –
- first seen
- 23 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Player counts
How does sigma 67 compare in the rankings?
Player hours over seven days put sigma 67 at #7,666, in the top 35% of the ranked set.
What population does sigma 67 carry?
The current row shows sigma 67 offline; the last response was 4 days 13 hours ago. Over the last seven days it averaged 1 players and peaked at 3.
Server facts
What Rust version does sigma 67 run?
Version Rust network protocol 2635 and build 168909 on Windows is reported by sigma 67. The protocol has to match before you can join, and Steam does the updating.
Is sigma 67 up, and what does its uptime show?
Offline now for sigma 67, last seen 4 days 13 hours ago. Uptime of 7% across the last 4 full days: 7 hours of 96. The first row Rust Data holds for it is dated 23 October 2026.
Which location does sigma 67 run from?
There is no region published for sigma 67. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 77.162.166.238:28015 is its address.
Settings and map
Which rules apply on sigma 67, and what settings?
The name sigma 67 carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on sigma 67?
A procedural map runs on sigma 67, generated by the game.
Wipe data
When does sigma 67 wipe, and how often?
The record for sigma 67 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. A new world was started 4 days 19 hours ago, and that is the one in play.
What is wipe day on sigma 67 like?
Across recent wipes the busiest point averaged 3 players. On the latest wipe the peak came 0 hours after the wipe, with a queue of 1.
Tags and filters
Where does sigma 67 appear among Rust Data lists and filters?
On Rust Data, sigma 67 appears in these lists: 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 week.
Which meanings do the tags on sigma 67 hold?
These tags are published by sigma 67 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): 0 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into sigma 67?
In Rust, F1 opens the console: type client.connect 77.162.166.238:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.