Offline 88.186.146.202:28015 checked 36d ago
Flutes Local Rust Dev
Connect
srv = rust.server("88.186.146.202:28016")
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 57% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 22 Sep, 21:39 UTC36d 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
- 88.186.146.202:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Sep 2026, 21:39 UTC
- hostname
- –
- first seen
- 22 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 55/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 | 82/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 25/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Population
What position does Flutes Local Rust Dev take in the server rankings?
Over the last seven days Flutes Local Rust Dev sits at #13,219 on player hours, in the top 57% of ranked servers.
How full does Flutes Local Rust Dev run?
The current row shows Flutes Local Rust Dev offline; the last response was 36 days 6 hours ago.
About the server
Which Rust version is Flutes Local Rust Dev on?
Rust network protocol 2633 and build 165217 on Windows is what Flutes Local Rust Dev runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Flutes Local Rust Dev, and is it online now?
Offline now for Flutes Local Rust Dev, last seen 36 days 6 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 22 September 2026.
Which location does Flutes Local Rust Dev run from?
No region is published by Flutes Local Rust Dev. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 88.186.146.202:28015 is its address.
Rules, settings, map
What rules and settings are recorded for Flutes Local Rust Dev?
No gather rate appears in the name: Flutes Local Rust Dev. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Flutes Local Rust Dev loaded?
Flutes Local Rust Dev runs a procedural map, which the game generates.
Wipe schedule
When does Flutes Local Rust Dev wipe, and how often?
Too few wipes are on record for Flutes Local Rust Dev to reveal its rhythm. 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 36 days 8 hours ago.
On Flutes Local Rust Dev, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began.
Tags and filters
Which Rust Data filters and lists contain Flutes Local Rust Dev?
The Rust Data lists that Flutes Local Rust Dev fits are: 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.
How should you read the server tags on Flutes Local Rust Dev?
These tags are published by Flutes Local Rust Dev and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 Flutes Local Rust Dev?
The manual route: launch Rust, F1, then client.connect 88.186.146.202:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.