Offline 188.255.171.116:28015 checked 24d ago
WindowsGSM - Server #2
Connect
srv = rust.server("188.255.171.116: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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 23 Sep, 02:20 UTC37d ago | 2 | NaN | running | 1 |
| 1 | Mon 14 Sep, 12:07 UTC45d ago | 1 | halved by day 3 | 8.6 days | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 188.255.171.116:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Sep 2026, 02:20 UTC
- hostname
- –
- first seen
- 14 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 | 15/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 33/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 4/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 15/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 128/200 |
Quick answers
From the figures on this page.
Population data
How does WindowsGSM - Server #2 compare in the rankings?
Rank #15,980 on seven-day player hours for WindowsGSM - Server #2, within the top 71% of all ranked servers.
How many players does WindowsGSM - Server #2 hold at once?
WindowsGSM - Server #2 returns no live count at this refresh, having last been seen 24 days 14 hours ago.
About the server
Which Rust version is WindowsGSM - Server #2 on?
Version Rust network protocol 2633 and build 163794 on Windows is reported by WindowsGSM - Server #2. Joining needs the same protocol on your game; Steam handles the update.
Is WindowsGSM - Server #2 up, and what does its uptime show?
WindowsGSM - Server #2 is offline at this refresh; the last response came 24 days 14 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 14 September 2026.
Where does WindowsGSM - Server #2 sit?
For WindowsGSM - Server #2, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 188.255.171.116:28015.
Settings and map
Which settings and rules does WindowsGSM - Server #2 run?
No gather rate appears in the name: WindowsGSM - Server #2. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Wipes and dates
When does WindowsGSM - Server #2 wipe, and on what schedule?
A rhythm cannot be read from the wipes of WindowsGSM - Server #2 on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 37 days ago.
On WindowsGSM - Server #2, what happens on wipe day?
The average peak over recent wipes is 2 players. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 3 in the other cases.
Tags and filters
Where does WindowsGSM - Server #2 appear among Rust Data lists and filters?
On Rust Data, WindowsGSM - Server #2 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on WindowsGSM - Server #2?
Read by the game's server browser, the tags WindowsGSM - Server #2 publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): The server runs build 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^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.
Connecting
What is the way to join WindowsGSM - Server #2?
In Rust, F1 opens the console: type client.connect 188.255.171.116:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.