Offline 207.148.89.197:28015 checked 30d ago
fp-audit-probe
Connect
srv = rust.server("207.148.89.197: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 best
Top 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 29 Sep, 03:38 UTC30d ago | 0 | NaN | running | 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 207.148.89.197:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 03:45 UTC
- hostname
- –
- first seen
- 29 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 495 on average | 85/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 116/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 283 on average | 407/450 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 24/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 484/525 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 371/425 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does fp-audit-probe rank?
Over the last seven days fp-audit-probe sits at #16,905 on player hours, in the top 71% of ranked servers.
How many players does fp-audit-probe hold at once?
fp-audit-probe returns no live count at this refresh, having last been seen 30 days 19 hours ago.
About the server
What Rust version does fp-audit-probe run?
Rust network protocol 2633 and build 165217 on Linux is what fp-audit-probe runs. The protocol has to match before you can join, and Steam does the updating.
Is fp-audit-probe up, and what does its uptime show?
fp-audit-probe is offline at this refresh; the last response came 30 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 29 September 2026.
In which location is fp-audit-probe hosted?
There is no region published for fp-audit-probe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 207.148.89.197:28015 is its address.
Rules, settings, map
Which rules apply on fp-audit-probe, and what settings?
No gather rate appears in the name: fp-audit-probe. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
What is the map on fp-audit-probe?
A procedural map runs on fp-audit-probe, generated by the game.
Wipe data
On what schedule does fp-audit-probe wipe?
A rhythm cannot be read from the wipes of fp-audit-probe 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. A new world was started 30 days 20 hours ago, and that is the one in play.
What is wipe day on fp-audit-probe like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which Rust Data filters and lists contain fp-audit-probe?
On Rust Data, fp-audit-probe appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on fp-audit-probe?
The game's server browser reads these tags from fp-audit-probe: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. 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.
Join steps
How can I connect to fp-audit-probe?
In Rust, F1 opens the console: type client.connect 207.148.89.197:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.