Online 66.179.242.247:28015 checked 11m ago
SigMaGames.net Monthly kits
Connect
srv = rust.server("66.179.242.247:28017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))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, measured since 17 Sep. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 22:07 UTC FW27d ago | 0 | 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
5000 · seed 790386263
- map
- Procedural Map
- size
- 5000
- seed
- 790386263
Server
srv.info()- address
- 66.179.242.247:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 22:07 UTC
- hostname
- –
- first seen
- 13 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 · 151 on average | 108/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 160/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 66/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 187/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 349/350 |
Quick answers
From the figures on this page.
Player counts
What position does SigMaGames.net Monthly kits take in the server rankings?
Over the last seven days SigMaGames.net Monthly kits sits at #15,289 on player hours, in the top 69% of ranked servers.
What population does SigMaGames.net Monthly kits carry?
SigMaGames.net Monthly kits reports 0 players at this refresh, with 500 slots configured. Over the last seven days it averaged 0 players.
About the server
How smoothly does SigMaGames.net Monthly kits run?
The 48-hour average is 113 server fps, with a low of 74. Entity numbers reached 133,277, and that includes buildings, deployables and the rest. Memory peaked at 5,807 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on SigMaGames.net Monthly kits?
Rust network protocol 2635 and build 168909 on Linux is what SigMaGames.net Monthly kits runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is SigMaGames.net Monthly kits, and is it online now?
Online is the state at the latest refresh for SigMaGames.net Monthly kits. A restart about 6 days 20 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does SigMaGames.net Monthly kits run from?
No region is published by SigMaGames.net Monthly kits. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 66.179.242.247:28015 is its address.
Settings and map
Which settings and rules does SigMaGames.net Monthly kits run?
The name SigMaGames.net Monthly kits carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, 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. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on SigMaGames.net Monthly kits?
Custom map, 5,000, run by SigMaGames.net Monthly kits; the file is published, so download it here.
Wipe schedule
When does SigMaGames.net Monthly kits wipe, and on what schedule?
Once a month SigMaGames.net Monthly kits wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 27 days 21 hours ago.
What is wipe day on SigMaGames.net Monthly kits like?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which lists on Rust Data hold SigMaGames.net Monthly kits, and which filters?
The Rust Data lists that SigMaGames.net Monthly kits fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on SigMaGames.net Monthly kits?
These tags are published by SigMaGames.net Monthly kits and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon; rustmaps (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join SigMaGames.net Monthly kits?
In Rust, F1 opens the console: type client.connect 66.179.242.247:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.