Rust HeatmapInfrared · players
IR live Players58,743 Servers11,691 Warm3,438 Fresh wipes · 3h104 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–500° · slots

SigmTAServer

Offline 46.30.191.64:28015 checked 38d ago

moddedoxide
Sp1 · players now 1/ 500
0% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#13,859
rank
no region published
39d ago
last wipe
no schedule published
–
next wipe
no wipe seen yet
UTC checked 38d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server performance

This server has not answered a direct query in the last 48 hours.

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.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep

Bx1Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 155 on average
176 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10
EU · groups of 8+ · weekly · 128 on average
120 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 115 on average
189 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 88 on average
131 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 87 on average
15 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 84 on average
51 / 1000

LogQuick answers

from the figures on this page

Wipe day

What is the wipe schedule on SigmTAServer?

The record of SigmTAServer's wipes is not yet long enough to show a rhythm. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world in play now was made 39 days 10 hours ago.

Player counts

How busy is SigmTAServer?

The last time SigmTAServer was seen was 38 days 20 hours ago, and it is offline now.

How does SigmTAServer rank against other Rust servers?

Ranked #13,859 on seven-day player hours, SigmTAServer is in the top – of all ranked servers.

Map and rules

Which map does SigmTAServer run?

SigmTAServer runs a procedural map, which the game generates.

What are the rules and settings on SigmTAServer?

A gather rate is not given in the name SigmTAServer. Groups can contain up to 8 players, the default in the game. survival is the game mode, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. In the server browser it is Modded, meaning plugins or settings modify the game. Oxide plugins run on this server. Anti-cheat: Valve's VAC is off.

Location and uptime

Which version of Rust does SigmTAServer run?

The build on SigmTAServer is Rust network protocol 2633 and build 163794, running on Windows. Your game must run the same protocol to join, and Steam takes care of updating it.

Is SigmTAServer online, and how reliable is it?

SigmTAServer is down just now; the last sighting was 38 days 20 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It first appears in Rust Heatmap records on 19 September 2026.

Where is SigmTAServer located?

A region is not published for SigmTAServer. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 46.30.191.64:28015 is its address.

Tags

Which Rust Heatmap lists and filters include SigmTAServer?

These Rust Heatmap lists include SigmTAServer: Modded Rust servers, by live population. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

What do the server tags on SigmTAServer mean?

These are the tags SigmTAServer publishes for the game's server browser to read: gmrust (Game mode): Rust survival, standard rules; mp500 (Max players): The slot count is 500; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): Your game must match protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Listed as Modded, since settings or plugins change the game. The top of this page also shows the tags for players now, the queue and when the world was made.

Connect

How do I join SigmTAServer?

To join by console, open it with F1 in Rust and enter client.connect 46.30.191.64:28015. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard rules.
mp500
Max players The slot count is 500.
ts8
Group limit The game default applies: 8 per team at most.
v2633
Protocol Your game must match protocol 2633 to get in.
cs163794
Build Build 163794.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Listed as Modded, since settings or plugins change the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.