Offline 147.45.39.18:28015 checked 20d ago
GIGASERV - SandBox
Connect
srv = rust.server("147.45.39.18:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. # The force wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 147.45.39.18:28015
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 11:19 UTC
- hostname
- –
- first seen
- 9 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | AQRUX RUST BUILD | CREATIVE | SANDBOX | EU · groups of 8+ · monthly · 24 on average | 40/100 |
| 1 | Art of Rust - Official dedicated art server | groups of 20+ · monthly · 8 on average | 5/100 |
| 2 | RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGrade | NA · groups of 100+ · monthly · 7 on average | 5/200 |
| 3 | [EU]Luuxens[PVE&RP]Town|Drugs|Quests|Tiers|Roles|RaidBases|Fire | EU · groups of 16+ · monthly · 6 on average | 8/50 |
| 4 | UTC | BUILDING | CREATIVE | BUILD | ПАЛЯНИЦЯ | EU | UA | EU · groups of 8+ · monthly · 3 on average | 5/40 |
| 5 | [EU]FreeFields/Creative/Building/Sandbox | EU · groups of 8+ · monthly · 2 on average | 12/35 |
Quick answers
From the figures on this page.
Population data
What position does GIGASERV - SandBox take in the server rankings?
Rank #13,650 on seven-day player hours for GIGASERV - SandBox, within the top 62% of all ranked servers.
How many players does GIGASERV - SandBox hold at once?
GIGASERV - SandBox returns no live count at this refresh, having last been seen 20 days 14 hours ago.
About the server
What is the Rust version on GIGASERV - SandBox?
Version Rust network protocol 2634 and build 166652 on Windows is reported by GIGASERV - SandBox. Steam updates your game for you, but the protocol must match to join.
How reliable is GIGASERV - SandBox, and is it up?
Offline now for GIGASERV - SandBox, last seen 20 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 9 October 2026.
Where does GIGASERV - SandBox sit?
No region is published by GIGASERV - SandBox. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 147.45.39.18:28015.
Rules, settings, map
Which settings and rules does GIGASERV - SandBox run?
The name GIGASERV - SandBox carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Vanilla, by its own description: untouched settings: rates, kits and rules as shipped. VAC, Valve's anti-cheat, is enabled.
What is the map on GIGASERV - SandBox?
A procedural map runs on GIGASERV - SandBox, generated by the game.
Wipe schedule
On what schedule does GIGASERV - SandBox wipe?
Expect an estimate: GIGASERV - SandBox's next wipe is projected from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 4 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
Lists and tags
Where does GIGASERV - SandBox appear among Rust Data lists and filters?
The Rust Data lists that GIGASERV - SandBox fits are: Modded Rust servers and Servers with build or creative tags. It appears 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 should you read the server tags on GIGASERV - SandBox?
Read by the game's server browser, the tags GIGASERV - SandBox publishes are: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): Slot count: 0; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into GIGASERV - SandBox?
The manual route: launch Rust, F1, then client.connect 147.45.39.18:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.