RUST METRICSFlight deck · live data
Data live Servers11,635 Players30,176 Populated2,756 Fresh wipes 3 h70 Scan5 min
‹ All servers212.20.40.180:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 212.20.40.180:28015 checked 11m ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 03:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 232 SERVER FPS

Server fps

48 h low 194 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 43,429 ×1000

Entities

48 h range 41,310–44,901 · memory 1,455 MB
1239 ET SINCE RESTART 02:58

Uptime

2 h 58 min since its last restart, at the last reading
7-day average0peak 1
Rank#9,255top 42%
Last wipe5h agobiweekly schedule
Next wipe7d 13hThu 5 Nov, 19:00 UTC FW
Memory1,455MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75106:0015:0000:0008:0017:0003:00Wiped Thu 29 Oct, 00:04 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
010020030040006:0015:0000:0008:0017:0003: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.

REC 3

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.

PLAN

Wipe schedule

from its schedule tag

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

usual gap6.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held25%else halves by day 1

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 13hFW
  2. WPT 2Thu 12 Nov, 00:04 UTC13d 18h
  3. WPT 3Thu 26 Nov, 00:04 UTC27d 18h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 13hFW
  5. WPT 5Thu 10 Dec, 00:04 UTC41d 18h

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 00:04 UTC5h ago – – running 0
Thu 15 Oct, 00:04 UTC14d ago 2 halved by day 1 14 days 0
Fri 9 Oct, 18:11 UTC19d ago 2 held half 5.2 days 1
Thu 1 Oct, 18:07 UTC FW27d ago 1 halved by day 1 8 days 0
Thu 1 Oct, 05:31 UTC27d ago 1 – 0.5 days 0
Thu 17 Sep, 00:02 UTC42d ago 1 halved by day 9 14.2 days 0
Mon 14 Sep, 11:24 UTC44d ago 3 held half 2.5 days 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on SOLO_Новосибирск | WIPE 29.10?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 14 hours. Above half that peak the crowd stayed until the next wipe in 25% of recent wipes. It fell below half by day 1 when it didn't.

When does SOLO_Новосибирск | WIPE 29.10 wipe?

The prediction follows its tag, because too few of SOLO_Новосибирск | WIPE 29.10's wipes are on record to confirm its schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 5 hours ago. A wipe schedule of every two weeks is published in its tags.

Tag meanings

How should you read the tags on SOLO_Новосибирск | WIPE 29.10?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; jp0 (Custom tag): Owner or plugin definition: this tag is not a standard Rust one from SOLO_Новосибирск | WIPE 29.10. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does SOLO_Новосибирск | WIPE 29.10 appear in Rust Metrics lists and filters?

On Rust Metrics, SOLO_Новосибирск | WIPE 29.10 sits in these lists: EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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.

Population

Where does SOLO_Новосибирск | WIPE 29.10 sit in the rankings?

Ranking for SOLO_Новосибирск | WIPE 29.10: #9,255 on seven-day player hours, top 42% of all ranked servers.

How full does SOLO_Новосибирск | WIPE 29.10 get?

0 of 50 slots are filled on SOLO_Новосибирск | WIPE 29.10 right now. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 0 players, at 08:00 UTC over the last 48 hours.

Operator and location

Which location does SOLO_Новосибирск | WIPE 29.10 run from?

Check: location. No region tag comes from SOLO_Новосибирск | WIPE 29.10, but the name points to Europe. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 212.20.40.180:28015.

What Rust version is SOLO_Новосибирск | WIPE 29.10 on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by SOLO_Новосибирск | WIPE 29.10. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for SOLO_Новосибирск | WIPE 29.10?

Check: fps. Average 228 server fps over the last 48 hours, low of 194. Within range. Peak entity count: 44,901. Buildings, deployables and all else included. Memory peak: 2,980 MB. Expect lag when fps falls and entities climb.

What is the uptime on SOLO_Новосибирск | WIPE 29.10, and is it online?

Reading: online. SOLO_Новосибирск | WIPE 29.10 answers right now. Check: restart. The uptime it reports puts the last restart about 2 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

What settings and rules apply on SOLO_Новосибирск | WIPE 29.10?

No gather rate appears in the name: SOLO_Новосибирск | WIPE 29.10. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

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

Size 3,000 and seed 6630: the game generates the procedural map on SOLO_Новосибирск | WIPE 29.10 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

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

Check: join. Open Rust, press F1, then enter client.connect 212.20.40.180:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Other

jp0
Custom tag Owner or plugin definition: this tag is not a standard Rust one.

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.