Rust Server TrendsSeismic network · station log
Recording Stations11,851 Players93,847 Active3,878 Wipes · 3 h391 48 h

Station XX-13219 · no signal

Flutes Local Rust Dev

Offline 88.186.146.202:28015 checked 36d ago

moddedoxide
Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,219
top 57%
Last wipe
36d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-13219 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Sep23 Sep25 Sep26 Sep28 Sep29 Sep

Top 57% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 22 Sep, 21:39 UTC36d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
179/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
184/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
80/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 86 on average
351/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 86 on average
245/ 700
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Flutes Local Rust Dev?

Flutes Local Rust Dev uses a procedural map, which the game generates.

Which settings and rules apply on Flutes Local Rust Dev?

You will find no gather rate in the name of Flutes Local Rust Dev. Groups hold up to 8 players, which is the default for the game. survival is the game mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on Flutes Local Rust Dev right now?

Flutes Local Rust Dev is not responding at this moment and is offline, last seen 36 days 15 hours ago.

How does Flutes Local Rust Dev rank against other Rust servers?

On player hours for the past week, Flutes Local Rust Dev sits at #13,219, which puts it inside the top 57% of every ranked server.

Server details

How reliably does Flutes Local Rust Dev stay online?

As recorded now, Flutes Local Rust Dev is not reachable, the last contact having been 36 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 22 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does Flutes Local Rust Dev run from?

No region is published by Flutes Local Rust Dev. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 88.186.146.202:28015 is the address it uses.

What build of Rust does Flutes Local Rust Dev use?

Flutes Local Rust Dev is running Rust network protocol 2633 and build 165217 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Flutes Local Rust Dev?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 1 hours after the wipe.

On what timetable does Flutes Local Rust Dev run its wipes?

On record so far are too few of Flutes Local Rust Dev's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 36 days 18 hours.

Server tags

What do the server tags on Flutes Local Rust Dev mean?

Tags published by Flutes Local Rust Dev and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Flutes Local Rust Dev appear?

The Rust Server Trends lists that take in Flutes Local Rust Dev are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

How do you connect to Flutes Local Rust Dev?

You can connect by pressing F1 in Rust and typing client.connect 88.186.146.202:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build Game build: 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.