Offline 108.207.110.158:28015 checked 1d ago
Grampy_Rust
Connect
srv = rust.server("108.207.110.158:28017")
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 25% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 1h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 25 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:58 UTC FW27d ago | 3 | NaN | running | 0 |
# 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
- 108.207.110.158:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 20:46 UTC
- hostname
- –
- first seen
- 13 Sep 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 165/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 94/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 235/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 350/350 |
Quick answers
From the figures on this page.
Player counts
What position does Grampy_Rust take in the server rankings?
Rank #5,688 on seven-day player hours for Grampy_Rust, within the top 25% of all ranked servers.
How full does Grampy_Rust run?
Offline now for Grampy_Rust, with the last sample 41 hours ago. Over the last seven days it averaged 0 players and peaked at 2.
About the server
What Rust version does Grampy_Rust run?
Rust network protocol 2635 and build 168909 on Linux is what Grampy_Rust runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Grampy_Rust, and is it online now?
Offline now for Grampy_Rust, last seen 41 hours ago. 111 of 168 hours up over the last 7 full days, or 66%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Grampy_Rust run from?
For Grampy_Rust, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 108.207.110.158:28015 is its address.
Rules, settings, map
Which settings and rules does Grampy_Rust run?
You will not find a gather rate in the string Grampy_Rust. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Grampy_Rust?
The game generates its map: procedural, on Grampy_Rust.
Wipe data
When does Grampy_Rust wipe, and on what schedule?
The only wipe Grampy_Rust takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 20 hours ago, and that is the one in play.
On Grampy_Rust, what happens on wipe day?
The average peak over recent wipes is 3 players. The crowd on the latest wipe topped out 25 hours after it began.
Lists and tags
Which Rust Data filters and lists contain Grampy_Rust?
The Rust Data lists that Grampy_Rust fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Grampy_Rust hold?
The game's server browser reads these tags from Grampy_Rust: gmvanilla (Game mode): Survival in vanilla form; mp4 (Max players): 4 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
Connecting
What is the way into Grampy_Rust?
The manual route: launch Rust, F1, then client.connect 108.207.110.158:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.