Station XX-13650 · no signal
GIGASERV - SandBox
Offline 147.45.39.18:28015 checked 19d ago
- Players now
- 1/ ?
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,650
- top 62%
- Last wipe
- 26d ago
- monthly schedule
- Next wipe
- 7d 19h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of ? slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on GIGASERV - SandBox?
A procedural map runs on GIGASERV - SandBox, generated by the game.
Which settings and rules apply on GIGASERV - SandBox?
The name of GIGASERV - SandBox gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game 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. The plugins run on Oxide. It describes itself as vanilla, which means rates, kits and rules are as Facepunch ships them. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on GIGASERV - SandBox?
No players are recorded on GIGASERV - SandBox at this moment; it is offline, and the last sighting was 19 days 22 hours ago.
How does GIGASERV - SandBox rank against other Rust servers?
Over the last seven days, GIGASERV - SandBox recorded enough player hours to reach #13,650 worldwide, placing it in the top 62% of all ranked servers.
Operator and location
How reliably does GIGASERV - SandBox stay online?
GIGASERV - SandBox is down at the moment; the last recorded contact was 19 days 22 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 9 October 2026.
Which region does GIGASERV - SandBox run from?
Nothing about a region comes from GIGASERV - SandBox. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 147.45.39.18: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. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
On what timetable does GIGASERV - SandBox run its wipes?
An estimate from the force wipe gives GIGASERV - SandBox's next wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. It has run its current world for 26 days 11 hours. The tags it publishes carry a monthly wipe schedule.
Lists and 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): You'll find standard Rust survival here; mp0 (Max players): 0 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^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): Plugins or settings alter the game, so it's listed 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?
You will find GIGASERV - SandBox on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust build and creative servers, live. You will find it under these filters on the server list: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How to join
How do you connect to GIGASERV - SandBox?
To join, enter client.connect 147.45.39.18: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.
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.