Online 24.87.152.238:28015 checked 12m ago
RIP Profiler local test server
Connect
srv = rust.server("24.87.152.238: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 69% 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
- 24.87.152.238:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 02:41 UTC
- hostname
- –
- first seen
- 26 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 · 149 on average | 0/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 47/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 12/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 45/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 211/215 |
Quick answers
From the figures on this page.
Player counts
How does RIP Profiler local test server compare in the rankings?
Player hours over seven days put RIP Profiler local test server at #15,262, in the top 69% of the ranked set.
How full does RIP Profiler local test server run?
The sample now reads 0 players for RIP Profiler local test server, out of 10 slots. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on RIP Profiler local test server?
The build is Rust network protocol 2635 and build 168909 on Linux, run by RIP Profiler local test server. Steam updates your game for you, but the protocol must match to join.
Is RIP Profiler local test server up, and what does its uptime show?
RIP Profiler local test server reports itself online at the current refresh. Uptime of 65% across the last 3 full days: 47 hours of 72. The first row Rust Data holds for it is dated 26 October 2026.
Where does RIP Profiler local test server sit?
No region is published by RIP Profiler local test server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 24.87.152.238:28015.
Map and rules
Which settings and rules does RIP Profiler local test server run?
The name RIP Profiler local test server carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on RIP Profiler local test server?
RIP Profiler local test server runs a procedural map, which the game generates.
Wipe schedule
On what schedule does RIP Profiler local test server wipe?
A rhythm cannot be read from the wipes of RIP Profiler local test server 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. The world it runs now was generated 3 days 21 hours ago.
Lists and tags
Which lists on Rust Data hold RIP Profiler local test server, and which filters?
On Rust Data, RIP Profiler local test server 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; Last wipe: In the last week.
Which meanings do the tags on RIP Profiler local test server hold?
These tags are published by RIP Profiler local test server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $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.
How to join
What is the way into RIP Profiler local test server?
The manual route: launch Rust, F1, then client.connect 24.87.152.238:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.