Offline 185.40.7.202:28015 checked 22d ago
GIGASERV - SandBox
Connect
srv = rust.server("185.40.7.202: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 66% 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 8d 18h. # 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
- 185.40.7.202:28015
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 11:19 UTC
- hostname
- –
- first seen
- 5 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 · 23 on average | 6/100 |
| 1 | Art of Rust - Official dedicated art server | groups of 20+ · monthly · 8 on average | 8/100 |
| 2 | RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGrade | NA · groups of 100+ · monthly · 7 on average | 11/200 |
| 3 | [EU]Luuxens[PVE&RP]Town|Drugs|Quests|Tiers|Roles|RaidBases|Fire | EU · groups of 16+ · monthly · 6 on average | 10/50 |
| 4 | UTC | BUILDING | CREATIVE | BUILD | ПАЛЯНИЦЯ | EU | UA | EU · groups of 8+ · monthly · 3 on average | 2/40 |
| 5 | [EU]FreeFields/Creative/Building/Sandbox | EU · groups of 8+ · monthly · 3 on average | 1/35 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does GIGASERV - SandBox rank?
Rank #14,930 on seven-day player hours for GIGASERV - SandBox, within the top 66% 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 22 days 12 hours ago.
About the server
What Rust version does GIGASERV - SandBox run?
Rust network protocol 2634 and build 166652 on Windows is what GIGASERV - SandBox runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is GIGASERV - SandBox, and is it online now?
GIGASERV - SandBox is offline at this refresh; the last response came 22 days 12 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 5 October 2026.
Which location does GIGASERV - SandBox run from?
For GIGASERV - SandBox, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 185.40.7.202:28015 is its address.
Map and rules
What rules and settings are recorded for GIGASERV - SandBox?
You will not find a gather rate in the string GIGASERV - SandBox. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. Anti-cheat status: VAC on.
Which map has GIGASERV - SandBox loaded?
GIGASERV - SandBox runs a procedural map, which the game generates.
Wipe schedule
When does GIGASERV - SandBox wipe, and on what schedule?
Expect an estimate: GIGASERV - SandBox's next wipe is projected from the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 25 days 12 hours ago. Its tags carry a monthly wipe schedule.
Tags and filters
Which Rust Data filters and lists contain GIGASERV - SandBox?
These Rust Data lists include GIGASERV - SandBox: 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): Survival play, standard Rust; mp0 (Max players): The server lists 0 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join GIGASERV - SandBox?
The manual route: launch Rust, F1, then client.connect 185.40.7.202:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.