Offline 81.161.32.221:29015 checked 3d ago
LocalRustServer1987
Connect
srv = rust.server("81.161.32.221: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 33% 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 08:41 UTC4d ago | 1 | NaN | running | 0 |
| 1 | Tue 20 Oct, 07:42 UTC8d ago | 1 | halved by day 2 | 4 days | 1 |
| 2 | Thu 17 Sep, 23:47 UTC40d ago | 1 | held half | 32.3 days | 1 |
| 3 | Wed 16 Sep, 10:43 UTC42d ago | 1 | NaN | 1.5 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 81.161.32.221:29015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 08:41 UTC
- hostname
- –
- first seen
- 16 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 · 554 on average | 416/500 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 277/300 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 295 on average | 42/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 294 on average | 35/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 273 on average | 75/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 252 on average | 94/200 |
Quick answers
From the figures on this page.
Population
How does LocalRustServer1987 compare in the rankings?
Player hours over seven days put LocalRustServer1987 at #7,379, in the top 33% of the ranked set.
How full does LocalRustServer1987 run?
The current row shows LocalRustServer1987 offline; the last response was 3 days ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
Which Rust version is LocalRustServer1987 on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by LocalRustServer1987. Joining needs the same protocol on your game; Steam handles the update.
How reliable is LocalRustServer1987, and is it up?
The latest sample has LocalRustServer1987 offline, with a last sighting 3 days ago. Uptime of 11% across the last 7 full days: 18 hours of 168. Its earliest recorded date in Rust Data is 16 September 2026.
Which location does LocalRustServer1987 run from?
For LocalRustServer1987, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 81.161.32.221:29015 is its address.
Map and rules
Which settings and rules does LocalRustServer1987 run?
You will not find a gather rate in the string LocalRustServer1987. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is not running; Valve's anti-cheat is off.
What is the map on LocalRustServer1987?
LocalRustServer1987 runs a procedural map, which the game generates.
Wipes and dates
When does LocalRustServer1987 wipe, and how often?
LocalRustServer1987 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. A new world was started 4 days 13 hours ago, and that is the one in play.
On LocalRustServer1987, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. In the wipes where it did not hold, half was lost by day 2.
Tags, lists
Which Rust Data filters and lists contain LocalRustServer1987?
The Rust Data lists that LocalRustServer1987 fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on LocalRustServer1987?
Read by the game's server browser, the tags LocalRustServer1987 publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is 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 LocalRustServer1987?
Enter client.connect 81.161.32.221:29015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.