RUST METRICSFlight deck · live data
Data live Servers11,774 Players84,256 Populated3,879 Fresh wipes 3 h167 Scan5 min
‹ All servers46.30.191.64:28015
Offline Full Queue Fresh wipe Wipe due No query

SigmTAServer

Offline 46.30.191.64:28015 checked 39d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,859no region published
Last wipe39d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server 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.

REC 3

Rank

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

Wipe schedule

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

LOG

Wipes

newest first
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

When does SigmTAServer wipe?

The rhythm of SigmTAServer's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 39 days 15 hours ago the current world was made.

Tags

Which tags does SigmTAServer carry, and what do they mean?

These are the tags SigmTAServer publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show SigmTAServer?

These Rust Metrics lists carry SigmTAServer: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does SigmTAServer sit in the rankings?

Player hours over seven days put SigmTAServer at #13,859, in the top – of all ranked servers.

How full does SigmTAServer get?

SigmTAServer is not responding; status offline, last seen 39 days 1 hours ago.

Server details

Which location does SigmTAServer run from?

Reading: location. SigmTAServer gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 46.30.191.64:28015.

What Rust version is SigmTAServer on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by SigmTAServer. To get in, your game needs the same protocol; Steam applies the update.

Is SigmTAServer up, and how often does it stay up?

Reading: offline. SigmTAServer last answered 39 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 September 2026.

Rules and settings

What rules does SigmTAServer enforce, and what are its settings?

Reading the name gives no gather rate for SigmTAServer. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC off, Valve's system.

What map is SigmTAServer on?

Check: map. Procedural, generated by the game, on SigmTAServer.

How to join

What do you do to join SigmTAServer?

To join: start Rust, press F1 and type client.connect 46.30.191.64:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players Slots: 500.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Game build reading: 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter 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.