Offline 94.54.148.95:28015 checked 36d ago
PrecisionSorter Test
Connect
srv = rust.server("94.54.148.95: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 bestTop 60% 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
- 94.54.148.95:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Sep 2026, 05:03 UTC
- hostname
- –
- first seen
- 22 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 | 89/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 91/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 77/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 23/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 16/1000 |
Quick answers
From the figures on this page.
Player counts
What position does PrecisionSorter Test take in the server rankings?
Player hours over seven days put PrecisionSorter Test at #13,771, in the top 60% of the ranked set.
What population does PrecisionSorter Test carry?
PrecisionSorter Test returns no live count at this refresh, having last been seen 36 days 12 hours ago.
Server data
What is the Rust version on PrecisionSorter Test?
Rust network protocol 2633 and build 164530 on Windows is what PrecisionSorter Test runs. The protocol has to match before you can join, and Steam does the updating.
Is PrecisionSorter Test up, and what does its uptime show?
The latest sample has PrecisionSorter Test offline, with a last sighting 36 days 12 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 22 September 2026.
Which location does PrecisionSorter Test run from?
No region is published by PrecisionSorter Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 94.54.148.95:28015.
Settings and map
What rules and settings are recorded for PrecisionSorter Test?
No gather rate appears in the name: PrecisionSorter Test. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has PrecisionSorter Test loaded?
The game generates its map: procedural, on PrecisionSorter Test.
Wipe schedule
On what schedule does PrecisionSorter Test wipe?
A rhythm cannot be read from the wipes of PrecisionSorter Test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 36 days 17 hours ago.
Tags and filters
Which lists on Rust Data hold PrecisionSorter Test, and which filters?
The Rust Data lists that PrecisionSorter Test fits are: 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 PrecisionSorter Test?
These tags are published by PrecisionSorter Test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Build number: 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): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join PrecisionSorter Test?
The manual route: launch Rust, F1, then client.connect 94.54.148.95:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.