Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h0 48 h

Station XX-4076 · recording

СушнякВась| Труба/Kanat

Online 57.128.233.7:2134 checked 3h ago

moddedoxide
Connect
Players now
0/ 150
0% full
Motion · 24 h
M0.2falling
−2 players on the day
7-day average
0
peak 4
Rank
#4,076
top 18%
Last wipe
4d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-4076 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 150 slots
Motion · 24 h
M0.2falling−2 players
Sharpest hour
−2into Wed 14:00 UTC
Peak · 48 h
4most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123421:0006:0015:0023:0008:0017:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020021:0006:0015:0023:0008:0017:00

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 14 Oct. 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
15k10k15k20k14 Oct17 Oct20 Oct22 Oct25 Oct28 Oct

Top 18% 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.

usual gap
7.8 daysbetween real wipes
wipe-day peak
4players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 24 OctFri 16 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 24 Oct, 11:14 UTC4d ago M0.0steady 3 – running 3
Fri 16 Oct, 15:46 UTC12d ago M0.3rising 4 held half 7.8 days 2

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
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 127 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 115 on average
183/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 90 on average
126/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
19/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
50/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 74 on average
453/ 700
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on СушнякВась| Труба/Kanat?

СушнякВась| Труба/Kanat runs a procedural map of size 6,000 with seed 42658162, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on СушнякВась| Труба/Kanat?

No gather rate appears in the name of СушнякВась| Труба/Kanat. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on СушнякВась| Труба/Kanat right now?

At this moment, СушнякВась| Труба/Kanat records 0 players across 150 slots. The seven-day average is 0 players, with a peak of 4. The busiest point in the last 48 hours came at 12:00 UTC, averaging 3 players.

How does СушнякВась| Труба/Kanat rank against other Rust servers?

On player hours for the past week, СушнякВась| Труба/Kanat sits at #4,076, which puts it inside the top 18% of every ranked server.

Server facts

How reliably does СушнякВась| Труба/Kanat stay online?

СушнякВась| Труба/Kanat is up at the moment. Going by the uptime figure it reports, it restarted about 2 days 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. 14 October 2026 is when Rust Server Trends first recorded it.

How well does СушнякВась| Труба/Kanat perform under load?

The 48-hour average is 132 server fps; 44 is the lowest observed. At its highest, it carried 218,680 entities: buildings, deployables and the world's other contents. Memory use peaked at 6,497 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does СушнякВась| Труба/Kanat run from?

The name of СушнякВась| Труба/Kanat points to Europe, even though it publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 57.128.233.7:2134.

Which Rust version is СушнякВась| Труба/Kanat running?

Rust network protocol 2635 and build 168909 on Linux is what СушнякВась| Труба/Kanat runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on СушнякВась| Труба/Kanat?

4 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.

On what timetable does СушнякВась| Труба/Kanat run its wipes?

The rhythm of СушнякВась| Труба/Kanat cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 4 days 8 hours is how long the current world has been running.

Tags

What do the server tags on СушнякВась| Труба/Kanat mean?

Tags published by СушнякВась| Труба/Kanat and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp150 (Max players): Slots: 150; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^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 СушнякВась| Труба/Kanat appear?

These Rust Server Trends lists include СушнякВась| Труба/Kanat: EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Connecting

How do you connect to СушнякВась| Труба/Kanat?

Enter client.connect 57.128.233.7:2134 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp150,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp150
Max players Slots: 150.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

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.