Offline 46.30.191.64:28015 checked 38d ago
SigmTAServer
Connect
srv = rust.server("46.30.191.64: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
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
- 46.30.191.64:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Sep 2026, 00:35 UTC
- hostname
- –
- first seen
- 19 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 · 155 on average | 158/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 93/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 | 40/1000 |
Quick answers
From the figures on this page.
Population
How does SigmTAServer compare in the rankings?
Player hours over seven days put SigmTAServer at #13,859, in the top – of the ranked set.
How full does SigmTAServer run?
Offline now for SigmTAServer, with the last sample 38 days 19 hours ago.
About the server
What is the Rust version on SigmTAServer?
Version Rust network protocol 2633 and build 163794 on Windows is reported by SigmTAServer. The protocol has to match before you can join, and Steam does the updating.
How reliable is SigmTAServer, and is it online now?
The latest sample has SigmTAServer offline, with a last sighting 38 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 19 September 2026.
Which location does SigmTAServer run from?
No region is published by SigmTAServer. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 46.30.191.64:28015 is its address.
Settings and map
Which settings and rules does SigmTAServer run?
No gather rate appears in the name: SigmTAServer. No custom cap; the default of 8 players per group stands. 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 is not running; Valve's anti-cheat is off.
What is the map on SigmTAServer?
A procedural map runs on SigmTAServer, generated by the game.
Wipe schedule
When does SigmTAServer wipe, and on what schedule?
A rhythm cannot be read from the wipes of SigmTAServer 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. A new world was started 39 days 8 hours ago, and that is the one in play.
Tags and filters
Which lists on Rust Data hold SigmTAServer, and which filters?
The Rust Data lists that SigmTAServer 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.
Which meanings do the tags on SigmTAServer hold?
Read by the game's server browser, the tags SigmTAServer publishes are: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into SigmTAServer?
The manual route: launch Rust, F1, then client.connect 46.30.191.64:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.