Skip to the story

Live edition71,182 playing on 11,803 servers

Rust Insights

Server profile

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

Online, with 0 of 50 players on; ranked #9,184 of every public Rust server, the top 41%. It last wiped 13h ago.

Filed under biweekly wipes moddedoxide
Launch Rust and join
0/ 50 players now 0% full
07-day averagepeak 1
#9,184ranktop 41%
13h agolast wipebiweekly schedule
7d 5hnext wipeThu 5 Nov, 19:00 UTC FW

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeakWipe
00.250.50.75114:0023:0008:0016:0002:0011:00Wiped Thu 29 Oct, 00:04 UTCWIPE

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

Server fpsWipe
010020030040014:0023:0008:0016:0002:0011:00Wiped Thu 29 Oct, 00:04 UTCWIPE

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

The wipe cycle

Wipe schedule

From its schedule tag.

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

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

Coming wipes

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

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

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

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

The record

Wipes

Every wipe we saw, newest first.

WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 00:04 UTC13h 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 UTC28d 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 UTC45d ago 3 held half 2.5 days 0

Note: 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.

If you like this one

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 average7/200
  2. RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average8/200
  3. [ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026)EU · groups of 16+ · biweekly · 4 on average2/50
  4. РЕЛАКС #2 Х2|Для новичков| No LimitEU · groups of 10+ · biweekly · 3 on average2/200
  5. #1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RUEU · groups of 10+ · biweekly · 3 on average2/300
  6. PurrRust|РУССКИЙ ДЛЯ НОВИЧКОВ|Vanilla2x|27.10EU · groups of 8+ · biweekly · 2 on average1/80

The short version

Quick answers

From the figures on this page.

Wipe cycle

On SOLO_Новосибирск | WIPE 29.10, what happens on wipe day?

At their busiest, its recent wipes drew 2 players on average. 14 hours into the latest wipe, the crowd on the server reached its peak. Half the peak held until the next wipe in 25% of its recent wipes. The cases that did not hold saw the crowd fall below half by day 1.

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

Too few wipes are on record for SOLO_Новосибирск | WIPE 29.10 to confirm its schedule, so the tag guides the prediction. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that applies to all Rust servers. 13 hours have passed since its current world was created. Its tags carry an every-two-weeks wipe schedule.

Server details

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

Server fps averaged 229 over 48 hours; the lowest reading was 212. The world held a peak of 44,901 entities, counting buildings, deployables and all the rest. The highest memory figure was 2,980 MB. Lag, for players, is low fps and an entity count that keeps climbing.

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

Running on Linux, SOLO_Новосибирск | WIPE 29.10 is on Rust network protocol 2635 and build 168909. Joining needs your game on the same protocol, which Steam updates for you.

How reliable is SOLO_Новосибирск | WIPE 29.10, and is it up at the moment?

At the time of this check SOLO_Новосибирск | WIPE 29.10 is online. About 10 hours ago is when it last restarted, judged from the uptime it reports. The last 7 full days gave 167 of 168 hours up, or 99% of the time. On 13 September 2026 is when Rust Insights first saw it.

In which location does SOLO_Новосибирск | WIPE 29.10 sit?

No region tag comes from SOLO_Новосибирск | WIPE 29.10, though the name suggests Europe. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. You can reach it at 212.20.40.180:28015.

Tags

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

These tags come from SOLO_Новосибирск | WIPE 29.10 and are read by the game's server browser: gmvanilla (Game mode): This server runs vanilla survival; mp50 (Max players): It holds 50 slots; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): Your game must run the same version to join: the protocol is 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks is the gap between wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is filed under Modded; jp0 (Custom tag): A plugin or the owner set this tag; it is not one of Rust's standard tags. You will find the present player count, the queue and the world's creation time among the tags, and they are displayed at the top of this page.

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

SOLO_Новосибирск | WIPE 29.10 appears among the following Rust Insights lists: Rust servers in Europe and Modded Rust servers, explained. On the server list, the filters that surface it 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.

Population

How many players are on SOLO_Новосибирск | WIPE 29.10 right now, and how does that number move?

SOLO_Новосибирск | WIPE 29.10 shows 0 players at the moment, against 50 slots. The seven-day average is 0 players, and the highest point in that week was 1. Its strongest hour in the past 48 was 10:00 UTC, with an average of 0 players.

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

Player hours over seven days put SOLO_Новосибирск | WIPE 29.10 at #9,184, within the top 41% of the ranked field.

Rules and settings

What are the settings and rules for SOLO_Новосибирск | WIPE 29.10?

No gather rate appears in the name of SOLO_Новосибирск | WIPE 29.10. No group limit is set, so the game's default of 8 players applies. You get survival as the game mode, the standard game: gather, build, raid. Players may raid and fight one another. Plugins or settings change the game, so it sits under Modded in the browser. Plugins: Oxide run here. Anti-cheat: VAC, from Valve, is on.

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

Size 3,000 and seed 6630 define the procedural map on SOLO_Новосибирск | WIPE 29.10, generated by the game. Size and seed give the same map each time, so this page lets you look at it on RustMaps.

Connecting

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

To connect, start Rust and enter client.connect 212.20.40.180:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.

The small print

Server tags

What each one means.

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

Game

gmvanilla
Game mode This server runs vanilla survival.
mp50
Max players It holds 50 slots.
ts8
Group limit The game default applies: teams cap at 8.
v2635
Protocol Your game must run the same version to join: the protocol is 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet handles the network layer, as it does by default.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two weeks is the gap between wipes.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is filed under Modded.

Other

jp0
Custom tag A plugin or the owner set this tag; it is not one of Rust's standard tags.

Note: 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.