Offline 178.72.116.35:28025 checked 38d ago
probe
Connect
srv = rust.server("178.72.116.35:28026")
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
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
- 178.72.116.35:28025
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Sep 2026, 09:47 UTC
- hostname
- –
- first seen
- 20 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 · 157 on average | 141/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 150/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 114/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 35/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 33/1000 |
Quick answers
From the figures on this page.
Player counts
How does probe compare in the rankings?
Rank #15,481 on seven-day player hours for probe, within the top – of all ranked servers.
How many players does probe hold at once?
The current row shows probe offline; the last response was 38 days 10 hours ago.
About the server
Which Rust version is probe on?
Rust network protocol 2633 and build 164530 on Windows is what probe runs. Steam updates your game for you, but the protocol must match to join.
How reliable is probe, and is it online now?
Offline now for probe, last seen 38 days 10 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 20 September 2026.
Which location does probe run from?
For probe, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 178.72.116.35:28025 is its address.
Rules, settings, map
Which rules apply on probe, and what settings?
You will not find a gather rate in the string probe. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has probe loaded?
The game generates its map: procedural, on probe.
Wipe data
On what schedule does probe wipe?
Too few wipes are on record for probe to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 38 days 10 hours ago.
Tags, lists
Which lists on Rust Data hold probe, and which filters?
The Rust Data lists that probe fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on probe?
The game's server browser reads these tags from probe: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to probe?
Enter client.connect 178.72.116.35:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.