Offline 91.210.160.158:28015 checked 24d ago
Local server 261
Connect
srv = rust.server("91.210.160.158: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 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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, 34 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 01:03 UTC25d ago | 1 | 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
- 91.210.160.158:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 01:03 UTC
- hostname
- –
- first seen
- 1 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 · 156 on average | 47/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 44/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 51/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Local server 261 rank?
Player hours over seven days put Local server 261 at #13,861, in the top 61% of the ranked set.
How full does Local server 261 run?
The current row shows Local server 261 offline; the last response was 24 days 11 hours ago.
Server facts
Which Rust version is Local server 261 on?
The build is Rust network protocol 2634 and build 166652 on Windows, run by Local server 261. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Local server 261, and is it up?
Offline now for Local server 261, last seen 24 days 11 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 1 October 2026.
In which location is Local server 261 hosted?
No region is published by Local server 261. Rust Data does not look up where the machine stands; it shows where a server says it is. 91.210.160.158:28015 is its address.
Rules, settings, map
Which rules apply on Local server 261, and what settings?
The name Local server 261 carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. The VAC field reads off.
What is the map on Local server 261?
A procedural map runs on Local server 261, generated by the game.
Wipes and dates
On what schedule does Local server 261 wipe?
A rhythm cannot be read from the wipes of Local server 261 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. This world was created 25 days 22 hours ago.
On Local server 261, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 34 hours after it began.
Tags, lists
Where does Local server 261 appear among Rust Data lists and filters?
On Rust Data, Local server 261 appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Local server 261 hold?
Read by the game's server browser, the tags Local server 261 publishes are: gmrust (Game mode): Survival play, standard Rust; mp15 (Max players): The server lists 15 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into Local server 261?
In Rust, F1 opens the console: type client.connect 91.210.160.158:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.