Station XX-14930 · no signal
GIGASERV - SandBox
Offline 185.40.7.202:28015 checked 22d ago
- Players now
- 1/ ?
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,930
- top 66%
- Last wipe
- 25d ago
- monthly schedule
- Next wipe
- 8d 15h
- 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 66% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. 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 pageServer rules
Which map is running on GIGASERV - SandBox?
GIGASERV - SandBox uses a procedural map, which the game generates.
Which settings and rules apply on GIGASERV - SandBox?
No gather rate appears in the name of GIGASERV - SandBox. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. It describes itself as vanilla, which means no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on GIGASERV - SandBox right now?
No players are recorded on GIGASERV - SandBox at this moment; it is offline, and the last sighting was 22 days 15 hours ago.
How does GIGASERV - SandBox rank against other Rust servers?
Over the last seven days, GIGASERV - SandBox recorded enough player hours to reach #14,930 worldwide, placing it in the top 66% 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 22 days 15 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 5 October 2026 is when Rust Server Trends first recorded it.
Which region does GIGASERV - SandBox run from?
No region is 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. 185.40.7.202:28015 is the address it uses.
What build of Rust does GIGASERV - SandBox use?
On Windows, GIGASERV - SandBox runs Rust network protocol 2634 and build 166652. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
On what timetable does GIGASERV - SandBox run its wipes?
An estimate from the force wipe gives GIGASERV - SandBox's next wipe. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 25 days 16 hours is how long the current world has been running. Its tags state a monthly wipe schedule.
Server 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): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear 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. These filters bring it up 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.
Connecting
What steps get you onto GIGASERV - SandBox?
To join, enter client.connect 185.40.7.202: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.