Rust Server TrendsSeismic network · station log
Recording Stations11,911 Players81,677 Active3,856 Wipes · 3 h102 48 h

Station XX-13159 · no signal

GIGASERV - SandBox

Offline 178.140.53.19:28015 checked 7d ago

monthly wipes vanillamoddedoxide
Connect
Players now
1/ ?
Motion · 24 h
M –
too few hourly readings
7-day average
1
peak 1
Rank
#13,159
top 59%
Last wipe
26d ago
monthly schedule
Next wipe
7d 22h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-13159 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of ? slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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, measured since 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k2 Oct7 Oct12 Oct18 Oct23 Oct28 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h. The force wipe · high confidence

wipe-day peak
1players, last three wipes

Coming wipes

  1. 7d 22hThu 5 Nov, 19:00 UTCFW
  2. 35d 22hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 5 Oct, 09:42 UTC23d ago M0.0falling 1 – running 2

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
AQRUX RUST BUILD | CREATIVE | SANDBOX EU · groups of 8+ · monthly · 24 on average
32/ 100
Art of Rust - Official dedicated art server groups of 20+ · monthly · 8 on average
8/ 100
RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGrade NA · groups of 100+ · monthly · 7 on average
8/ 200
[EU]Luuxens[PVE&RP]Town|Drugs|Quests|Tiers|Roles|RaidBases|Fire EU · groups of 16+ · monthly · 6 on average
10/ 50
UTC | BUILDING | CREATIVE | BUILD | ПАЛЯНИЦЯ | EU | UA EU · groups of 8+ · monthly · 3 on average
13/ 40
[EU]FreeFields/Creative/Building/Sandbox EU · groups of 8+ · monthly · 3 on average
8/ 35
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on GIGASERV - SandBox?

The procedural map on GIGASERV - SandBox is size 4,500 with seed 1337, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on GIGASERV - SandBox?

No gather rate appears in the name of GIGASERV - SandBox. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: rates, kits and rules are as Facepunch ships them. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on GIGASERV - SandBox?

A reading taken now finds GIGASERV - SandBox offline; the most recent activity was 7 days 6 hours ago. The seven-day average is 1 players, with a peak of 1.

How does GIGASERV - SandBox rank against other Rust servers?

Over the last seven days, GIGASERV - SandBox recorded enough player hours to reach #13,159 worldwide, placing it in the top 59% of all ranked servers.

Operator and location

How reliably does GIGASERV - SandBox stay online?

As recorded now, GIGASERV - SandBox is not reachable, the last contact having been 7 days 6 hours ago. 4 of 168 hours in the last 7 full days were up time, 2% of the total. 2 October 2026 is when Rust Server Trends first recorded it.

Where in the world is GIGASERV - SandBox hosted?

A region is not published by GIGASERV - SandBox. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 178.140.53.19:28015.

What build of Rust does GIGASERV - SandBox use?

GIGASERV - SandBox is running Rust network protocol 2634 and build 166652 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on GIGASERV - SandBox?

The recent wipes averaged a busiest count of 1 players. 1 hours into the latest wipe, the crowd reached its peak.

On what timetable does GIGASERV - SandBox run its wipes?

At the force wipe each month GIGASERV - SandBox wipes, and at no other time. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. It has run its current world for 26 days 9 hours. Its tags state a monthly wipe schedule.

Tags

What do the server tags on GIGASERV - SandBox mean?

These are the tags GIGASERV - SandBox publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp0 (Max players): The server has 0 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): It runs game build 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does GIGASERV - SandBox appear?

These Rust Server Trends lists include GIGASERV - SandBox: Modded Rust servers, tracked live and Rust build and creative servers, live. On the server list, the filters it matches are: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Join the server

How do you connect to GIGASERV - SandBox?

To join, enter client.connect 178.140.53.19:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,^m,^v,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp0
Max players The server has 0 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166652
Build It runs game build 166652.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Wipe schedule

^m
Monthly Wipes happen monthly, at the same time as Facepunch's force wipe.

Difficulty

^v
Vanilla Rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.