Offline 74.38.7.110:28018 checked 28d ago
orca-probe
Connect
srv = rust.server("74.38.7.110:28019")
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, measured since 30 Sep. 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 70% 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())
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 | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does orca-probe rank?
Player hours over seven days put orca-probe at #16,839, in the top 70% of the ranked set.
How many players does orca-probe hold at once?
Offline now for orca-probe, with the last sample 28 days 14 hours ago.
About the server
What Rust version does orca-probe run?
Version Rust network protocol 2633 and build 164530 on Windows is reported by orca-probe. The protocol has to match before you can join, and Steam does the updating.
Is orca-probe up, and what does its uptime show?
orca-probe is offline at this refresh; the last response came 28 days 14 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 30 September 2026.
In which location is orca-probe hosted?
For orca-probe, 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 74.38.7.110:28018.
Settings and map
What rules and settings are recorded for orca-probe?
The name orca-probe carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has orca-probe loaded?
orca-probe runs a procedural map of size 6,000 with seed 890293165, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Custom Map.
Wipe schedule
When does orca-probe wipe, and how often?
The record for orca-probe holds too few wipes to show a 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 54 days 17 hours ago.
Tags, lists
Where does orca-probe appear among Rust Data lists and filters?
On Rust Data, orca-probe appears in these lists: 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 orca-probe?
These tags are published by orca-probe and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): The server runs build 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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
What is the way into orca-probe?
In Rust, F1 opens the console: type client.connect 74.38.7.110:28018. Launch Rust on this page does the same by opening the game through Steam and connecting.