Skip to the page
Network live 11,716 servers online 55,754 players aboard 168 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Online 212.20.40.180:28015 checked 10m ago

biweekly wipes moddedoxide
Tracking number · connect
Wipe progress · wiped 10h ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Thu 5 Nov, 19:00 UK Thu 5 Nov, 19:00 UTC FW in 7d 8h · high confidence
0/ 50 players now 0% full
07-day averagepeak 1
#9,247ranktop 42%
10h agolast wipebiweekly schedule
7d 8hnext wipeThu 5 Nov, 19:00 UTC FW
Delivery history

Players, performance and rank

Players

AveragePeakWipe
00.250.50.75111:0020:0005:0014:0000:0009:00Wiped Thu 29 Oct, 00:04 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
010020030040011:0020:0005:0014:0000:0009: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule

from its schedule tag
Next delivery expected

Next wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 7d 8h.

The force wipe · high confidence
6.6 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
2wipe-day peakplayers, last three wipes
25%crowd heldelse halves by day 1

Coming wipes

  1. 7d 8hThu 5 Nov, 19:00 UTC19:00 UKFW
  2. 13d 13hThu 12 Nov, 00:04 UTC00:04 UK
  3. 27d 13hThu 26 Nov, 00:04 UTC00:04 UK
  4. 35d 8hThu 3 Dec, 19:00 UTC19:00 UKFW
  5. 41d 13hThu 10 Dec, 00:04 UTC00:04 UK

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.

Wipes

every wipe as a delivery, newest first
  1. Thu 5 Nov, 19:00 UTC FW19:00 UK · in 7d 8h
    Next wipe expected · the force wipe
  2. Thu 29 Oct, 00:04 UTC 00:04 UK · 10h ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    running
    Players before
    0
  3. Thu 15 Oct, 00:04 UTC 01:04 UK · 14d ago
    Wipe delivered
    Peak
    2
    Crowd
    halved by day 1
    Lasted
    14 days
    Players before
    0
  4. Fri 9 Oct, 18:11 UTC 19:11 UK · 19d ago
    Wipe delivered
    Peak
    2
    Crowd
    held half
    Lasted
    5.2 days
    Players before
    1
  5. Thu 1 Oct, 18:07 UTC FW 19:07 UK · 27d ago
    Force wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    8 days
    Players before
    0
  6. Thu 1 Oct, 05:31 UTC 06:31 UK · 28d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.5 days
    Players before
    0
  7. Thu 17 Sep, 00:02 UTC 01:02 UK · 42d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 9
    Lasted
    14.2 days
    Players before
    0
  8. Mon 14 Sep, 11:24 UTC 12:24 UK · 44d ago
    Wipe delivered
    Peak
    3
    Crowd
    held half
    Lasted
    2.5 days
    Players before
    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.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10EU · groups of 50+ · biweekly · 9 on average 9 / 200
  2. RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average 6 / 200
  3. [ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026)EU · groups of 16+ · biweekly · 4 on average 1 / 50
  4. РЕЛАКС #2 Х2|Для новичков| No LimitEU · groups of 10+ · biweekly · 3 on average 2 / 200
  5. #1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RUEU · groups of 10+ · biweekly · 3 on average 0 / 300
  6. PurrRust|РУССКИЙ ДЛЯ НОВИЧКОВ|Vanilla2x|27.10EU · groups of 8+ · biweekly · 2 on average 1 / 80
Help desk

Quick answers

From the figures on this page.

Player count

Where does SOLO_Новосибирск | WIPE 29.10 place among Rust servers?

Over the past seven days, SOLO_Новосибирск | WIPE 29.10 has climbed to #9,247 for player hours, putting it in the top 42% of all ranked servers.

Is SOLO_Новосибирск | WIPE 29.10 busy at the moment?

At the moment 0 players are on SOLO_Новосибирск | WIPE 29.10, which has 50 slots. Averaged over the past week: 0 players, peaking at 1. The busiest hour over the last 48 hours was 11:00 UTC, averaging 0 players.

Rules and settings

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

Generated by the game with seed 6630, the procedural map on SOLO_Новосибирск | WIPE 29.10 is size 3,000. Size and seed match means the map matches, so you can view it on RustMaps from this page.

What are the rules on SOLO_Новосибирск | WIPE 29.10, and what settings does it run?

You will not find a gather rate in the name of SOLO_Новосибирск | WIPE 29.10. The game's default applies: 8 players to a group at most. You get survival here, gather and build and raid: the standard game. You can raid and fight other players. The server browser lists it as Modded, because plugins or settings alter the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

About the server

What is the location of SOLO_Новосибирск | WIPE 29.10?

The name of SOLO_Новосибирск | WIPE 29.10 points to Europe, though no region tag is published. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. You will find it at 212.20.40.180:28015.

Does SOLO_Новосибирск | WIPE 29.10 perform well?

Averaged over the last 48 hours, server fps was 230, with a low of 212. Buildings, deployables and all the rest of the world pushed its entity count as high as 44,901. 2,980 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.

Is SOLO_Новосибирск | WIPE 29.10 up, and how good is its uptime?

SOLO_Новосибирск | WIPE 29.10 is up and online at the moment. The uptime it reports puts its last restart at about 8 hours ago. It was up 167 of 168 hours over the last 7 full days, 99% of the time. It was first seen by Rust Wipe Tracker on 13 September 2026.

On what Rust version does SOLO_Новосибирск | WIPE 29.10 operate?

On Linux, SOLO_Новосибирск | WIPE 29.10 runs Rust network protocol 2635 and build 168909. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe times

How does SOLO_Новосибирск | WIPE 29.10 handle its wipe days?

The average busiest point of its recent wipes was 2 players. 14 hours after the latest wipe, the crowd reached its peak. Until the next wipe, the crowd stayed over half the peak in 25% of recent cases. Where that did not hold, it dropped below half by day 1.

On what schedule does SOLO_Новосибирск | WIPE 29.10 reset its map?

The prediction follows its tag, because too few of SOLO_Новосибирск | WIPE 29.10's wipes are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. You are playing a world created 10 hours. Its tags give the wipe schedule as every two weeks.

Tags and filters

On Rust Wipe Tracker, which lists and filters is SOLO_Новосибирск | WIPE 29.10 part of?

You will find SOLO_Новосибирск | WIPE 29.10 on the following Rust Wipe Tracker lists: Rust servers in Europe and Modded Rust servers. On the server list, apply 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 and it appears.

What is the meaning of the server tags on SOLO_Новосибирск | WIPE 29.10?

gmvanilla (Game mode): Vanilla survival gameplay; mp50 (Max players): It holds 50 slots; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): No region code is set; ^b (Biweekly): A wipe comes every fortnight; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; jp0 (Custom tag): This isn't a standard Rust tag; it comes from the owner or a plugin are the tags SOLO_Новосибирск | WIPE 29.10 publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

How to join

What steps do you take to join SOLO_Новосибирск | WIPE 29.10?

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 212.20.40.180:28015.

Server tags

what each one means

Published as mp50,ptrak,jp0,$r?,v2635,^b,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Vanilla survival gameplay.
mp50
Max players It holds 50 slots.
ts8
Group limit 8 per team, which is the default.
v2635
Protocol Protocol 2635 is required; a different version can't join.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly A wipe comes every fortnight.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded The game is changed by plugins or settings, hence the Modded listing.

Other

jp0
Custom tag This isn't a standard Rust tag; it comes from the owner or a plugin.

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.