Station XX-10237 · no signal
GIGALOX
Offline 88.212.52.147:28015 checked 5d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #10,237
- top 46%
- Last wipe
- 5d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 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 46% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 38.7 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 22 Oct, 11:44 UTC5d ago | M0.0▼falling | 1 | – | running | 2 | |
| Sun 13 Sep, 18:40 UTC44d ago | M0.3▲rising | 3 | held half | 38.7 days | 1 |
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 pageMap and rules
Which map is running on GIGALOX?
A procedural map runs on GIGALOX, generated by the game.
Which settings and rules apply on GIGALOX?
No gather rate appears in the name of GIGALOX. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on GIGALOX right now?
A reading taken now finds GIGALOX offline; the most recent activity was 5 days 20 hours ago. The seven-day average is 1 players, with a peak of 1.
How does GIGALOX rank against other Rust servers?
On player hours for the past week, GIGALOX sits at #10,237, which puts it inside the top 46% of every ranked server.
Server facts
How reliably does GIGALOX stay online?
As recorded now, GIGALOX is not reachable, the last contact having been 5 days 20 hours ago. 5 of 168 hours in the last 7 full days were up time, 3% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does GIGALOX run from?
Nothing about a region comes from GIGALOX. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 88.212.52.147:28015 is the address it uses.
What build of Rust does GIGALOX use?
On Windows, GIGALOX runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on GIGALOX?
On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 0 hours after the wipe. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
How often does GIGALOX wipe, and on which days?
Too few wipes of GIGALOX are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 5 days 20 hours.
Lists and tags
What do the server tags on GIGALOX mean?
Tags published by GIGALOX and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): Slots: 10; 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; cs167781 (Build): It runs game build 167781; 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; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 GIGALOX appear?
You will find GIGALOX on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How to join
How do you connect to GIGALOX?
To join, enter client.connect 88.212.52.147: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.