Offline 163.44.125.241:28015 checked 11d ago
RustServer_2901
Connect
srv = rust.server("163.44.125.241: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, measured since 17 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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 2, 26 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 10:03 UTC27d ago | 2 | NaN | running | 0 |
| 1 | Fri 18 Sep, 17:01 UTC40d ago | 1 | halved by day 5 | 13.7 days | 0 |
| 2 | Thu 17 Sep, 19:54 UTC41d ago | 1 | NaN | 0.9 days | 6 |
| 3 | Thu 17 Sep, 11:31 UTC42d ago | 6 | NaN | 0.3 days | 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
4250 · seed 1042219269
- map
- Procedural Map
- size
- 4250
- seed
- 1042219269
Server
srv.info()- address
- 163.44.125.241:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 10:03 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 · 514 on average | 538/575 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 430/475 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 290 on average | 167/250 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 57/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 275 on average | 221/250 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 236 on average | 304/350 |
Quick answers
From the figures on this page.
Population data
What position does RustServer_2901 take in the server rankings?
Rank #13,584 on seven-day player hours for RustServer_2901, within the top 62% of all ranked servers.
How full does RustServer_2901 run?
RustServer_2901 returns no live count at this refresh, having last been seen 11 days 16 hours ago.
About the server
What is the Rust version on RustServer_2901?
The build is Rust network protocol 2634 and build 167781 on Linux, run by RustServer_2901. Joining needs the same protocol on your game; Steam handles the update.
Is RustServer_2901 up, and what does its uptime show?
The latest sample has RustServer_2901 offline, with a last sighting 11 days 16 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 13 September 2026.
Which location does RustServer_2901 run from?
For RustServer_2901, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 163.44.125.241:28015 is its address.
Rules, settings, map
Which settings and rules does RustServer_2901 run?
No gather rate appears in the name: RustServer_2901. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Which map has RustServer_2901 loaded?
The game generates the map on RustServer_2901: procedural, size 4,250, seed 1042219269. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does RustServer_2901 wipe, and on what schedule?
RustServer_2901 wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 27 days 4 hours ago.
On RustServer_2901, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 26 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 5.
Tags, lists
Where does RustServer_2901 appear among Rust Data lists and filters?
On Rust Data, RustServer_2901 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 RustServer_2901?
Read by the game's server browser, the tags RustServer_2901 publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to RustServer_2901?
In Rust, F1 opens the console: type client.connect 163.44.125.241:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.