Rust Server TrendsSeismic network · station log
Recording Stations11,795 Players69,100 Active3,591 Wipes · 3 h187 48 h

Station XX-9189 · recording

SOLO_Новосибирск | WIPE 29.10

Online 212.20.40.180:28015 checked 10m ago

biweekly wipes moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#9,189
top 41%
Last wipe
12h ago
biweekly schedule
Next wipe
7d 6h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-9189 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Thu 10:00 UTC
Peak · 48 h
1most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
00.250.50.75113:0022:0007:0016:0002:0011:00Wiped Thu 29 Oct, 00:04 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
010020030040013:0022:0007:0016:0002:0011:00Wiped Thu 29 Oct, 00:04 UTCWIPE

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 17 Sep. 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Expected events

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe · high confidence

usual gap
6.6 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
25%else halves by day 1

Coming wipes

  1. 7d 6hThu 5 Nov, 19:00 UTCFW
  2. 13d 11hThu 12 Nov, 00:04 UTC
  3. 27d 11hThu 26 Nov, 00:04 UTC
  4. 35d 6hThu 3 Dec, 19:00 UTCFW
  5. 41d 11hThu 10 Dec, 00:04 UTC

The first 48 hours of its last wipes

Thu 15 OctFri 9 OctThu 1 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 29 Oct, 00:04 UTC12h ago – – – – running 0
Thu 15 Oct, 00:04 UTC14d ago M0.3rising 2 halved by day 1 14 days 0
Fri 9 Oct, 18:11 UTC19d ago M0.0rising 2 held half 5.2 days 1
Thu 1 Oct, 18:07 UTC FW27d ago M0.0rising 1 halved by day 1 8 days 0
Thu 1 Oct, 05:31 UTC28d ago M0.0rising 1 – 0.5 days 0
Thu 17 Sep, 00:02 UTC42d ago M0.0rising 1 halved by day 9 14.2 days 0
Mon 14 Sep, 11:24 UTC45d ago M0.5rising 3 held half 2.5 days 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
СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10 EU · groups of 50+ · biweekly · 9 on average
9/ 200
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ EU · groups of 8+ · biweekly · 8 on average
9/ 200
[ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026) EU · groups of 16+ · biweekly · 4 on average
2/ 50
РЕЛАКС #2 Х2|Для новичков| No Limit EU · groups of 10+ · biweekly · 3 on average
2/ 200
#1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RU EU · groups of 10+ · biweekly · 3 on average
2/ 300
PurrRust|РУССКИЙ ДЛЯ НОВИЧКОВ|Vanilla2x|27.10 EU · groups of 8+ · biweekly · 2 on average
3/ 80
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on SOLO_Новосибирск | WIPE 29.10?

Generated by the game, the map on SOLO_Новосибирск | WIPE 29.10 is procedural, size 3,000 with seed 6630. 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 SOLO_Новосибирск | WIPE 29.10?

No gather rate appears in the name of SOLO_Новосибирск | WIPE 29.10. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Live population

What is the current population on SOLO_Новосибирск | WIPE 29.10?

A reading taken now shows 0 players on SOLO_Новосибирск | WIPE 29.10, which has 50 slots. Across seven days this server recorded an average of 0 players and a peak of 1. Averaged over the last 48 hours, the busiest hour was 10:00 UTC at 0 players.

How does SOLO_Новосибирск | WIPE 29.10 rank against other Rust servers?

The last seven days of player hours place SOLO_Новосибирск | WIPE 29.10 at #9,189, in the top 41% of all ranked servers.

Operator and location

How reliably does SOLO_Новосибирск | WIPE 29.10 stay online?

As recorded now, SOLO_Новосибирск | WIPE 29.10 is running. The uptime it reports puts its last restart about 10 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.

How well does SOLO_Новосибирск | WIPE 29.10 perform under load?

The 48-hour average is 230 server fps; 212 is the lowest observed. The world held up to 44,901 entities at its peak, buildings and deployables included. Its highest memory use was 2,980 MB. Low fps together with a growing entity count is what players experience as lag.

Where in the world is SOLO_Новосибирск | WIPE 29.10 hosted?

The name of SOLO_Новосибирск | WIPE 29.10 points to Europe, even though it publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 212.20.40.180:28015.

What build of Rust does SOLO_Новосибирск | WIPE 29.10 use?

Rust network protocol 2635 and build 168909 on Linux is what SOLO_Новосибирск | WIPE 29.10 runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on SOLO_Новосибирск | WIPE 29.10?

2 players, on average, was the busiest crowd at its recent wipes. 14 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 25% of its recent wipes. It fell under half by day 1 in the wipes where it didn't hold.

On what timetable does SOLO_Новосибирск | WIPE 29.10 run its wipes?

The prediction follows its tag, because too few of SOLO_Новосибирск | WIPE 29.10's wipes are on record to confirm its schedule. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. It has run its current world for 12 hours. In its tags it sets out a wipe schedule of every two weeks.

Lists and tags

What do the server tags on SOLO_Новосибирск | WIPE 29.10 mean?

The game's server browser reads the tags SOLO_Новосибирск | WIPE 29.10 publishes: gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): The server has 50 slots; 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): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): It wipes once a fortnight; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; jp0 (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does SOLO_Новосибирск | WIPE 29.10 appear?

These Rust Server Trends lists include SOLO_Новосибирск | WIPE 29.10: EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.

How to join

What steps get you onto SOLO_Новосибирск | WIPE 29.10?

You can connect by pressing F1 in Rust and typing client.connect 212.20.40.180: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 mp50,ptrak,jp0,$r?,v2635,^b,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla mode.
mp50
Max players The server has 50 slots.
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 The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

jp0
Custom tag The owner or a plugin set this tag, and it's not one of Rust's standard tags.

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.