Offline 119.101.116.140:28017 checked 22d ago
probe
Connect
srv = rust.server("119.101.116.140:28018")
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
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
- 119.101.116.140:28017
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 04:45 UTC
- hostname
- –
- first seen
- 7 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 87/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 148/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 60/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 170/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
How does probe compare in the rankings?
Rank #15,956 on seven-day player hours for probe, within the top 71% of all ranked servers.
How full does probe run?
Offline now for probe, with the last sample 22 days 14 hours ago.
About the server
What Rust version does probe run?
The build is Rust network protocol 2634 and build 166652 on Windows, run by probe. The protocol has to match before you can join, and Steam does the updating.
How reliable is probe, and is it online now?
probe is offline at this refresh; the last response came 22 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 7 October 2026.
Which location does probe run from?
There is no region published for probe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 119.101.116.140:28017.
Settings and map
Which rules apply on probe, and what settings?
No gather rate appears in the name: probe. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has probe loaded?
A procedural map runs on probe, generated by the game.
Wipe schedule
When does probe wipe, and on what schedule?
A rhythm cannot be read from the wipes of probe on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 22 days 15 hours ago.
Lists and tags
Which lists on Rust Data hold probe, and which filters?
These Rust Data lists include probe: 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.
How should you read the server tags on probe?
These tags are published by probe and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; 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): Plugins or settings alter the game, so it sits under Modded. 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
How can I connect to probe?
Enter client.connect 119.101.116.140:28017 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.