Offline 80.187.116.202:28015 checked 30d ago
probe
Connect
srv = rust.server("80.187.116.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 best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
- 80.187.116.202:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Sep 2026, 11:16 UTC
- hostname
- –
- first seen
- 28 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 · 156 on average | 47/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 44/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 51/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does probe rank?
Player hours over seven days put probe at #16,949, in the top 71% of the ranked set.
How many players does probe hold at once?
probe returns no live count at this refresh, having last been seen 30 days 12 hours ago.
Server facts
Which Rust version is probe on?
Version Rust network protocol 2633 and build 163794 on Windows is reported by probe. The protocol has to match before you can join, and Steam does the updating.
Is probe up, and what does its uptime show?
The latest sample has probe offline, with a last sighting 30 days 12 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 28 September 2026.
Where does probe sit?
There is no region published for probe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 80.187.116.202:28015.
Rules, settings, map
Which settings and rules does probe run?
No gather rate appears in the name: probe. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. 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.
Which map has probe selected?
A procedural map runs on probe, generated by the game.
Wipe schedule
When does probe wipe, and on what schedule?
Too few wipes are on record for probe to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 30 days 12 hours ago.
Tags, lists
Which lists on Rust Data hold probe, and which filters?
On Rust Data, probe 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 probe?
Read by the game's server browser, the tags probe publishes are: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): The server runs build 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to probe?
The manual route: launch Rust, F1, then client.connect 80.187.116.202:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.