Offline 24.171.68.3:28015 checked 10d ago
<SERVER_NAME>
Connect
srv = rust.server("24.171.68.3: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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 15h | Thu 3 Dec, 19:00 UTC | FW 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 | Thu 1 Oct, 23:20 UTC FW26d 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
- 24.171.68.3:28015
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 23:20 UTC
- hostname
- –
- first seen
- 13 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 · 530 on average | 231/250 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 329 on average | 15/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 327 on average | 21/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 111/200 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 279 on average | 42/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 264 on average | 42/100 |
Quick answers
From the figures on this page.
Player counts
How does <SERVER_NAME> compare in the rankings?
Rank #15,330 on seven-day player hours for <SERVER_NAME>, within the top 70% of all ranked servers.
How full does <SERVER_NAME> run?
Offline now for <SERVER_NAME>, with the last sample 10 days 3 hours ago.
Server data
What is the Rust version on <SERVER_NAME>?
The build is Rust network protocol 2634 and build 167781 on Linux, run by <SERVER_NAME>. Joining needs the same protocol on your game; Steam handles the update.
How reliable is <SERVER_NAME>, and is it online now?
<SERVER_NAME> is offline at this refresh; the last response came 10 days 3 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 13 September 2026.
Where does <SERVER_NAME> sit?
There is no region published for <SERVER_NAME>. 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 24.171.68.3:28015.
Settings and map
Which settings and rules does <SERVER_NAME> run?
The name <SERVER_NAME> carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
Which map has <SERVER_NAME> loaded?
A procedural map runs on <SERVER_NAME>, generated by the game.
Wipes and dates
When does <SERVER_NAME> wipe, and on what schedule?
A single wipe each month, the force wipe, is all <SERVER_NAME> does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 26 days 4 hours ago.
What is wipe day on <SERVER_NAME> like?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain <SERVER_NAME>?
These Rust Data lists include <SERVER_NAME>: 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.
Which meanings do the tags on <SERVER_NAME> hold?
These tags are published by <SERVER_NAME> and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): 0 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. 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
What is the way to join <SERVER_NAME>?
In Rust, F1 opens the console: type client.connect 24.171.68.3:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.