Rust PopulationField survey · Rust servers
Observing 75,280 players 11,830 servers 3,722 with someone on 228 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 9,176habitat unknownfirst seen 13 Sep 2026

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

Online 212.20.40.180:28015 checked 10m ago

biweekly wipes moddedoxide

Measurements

Players now
0/ 50
0% full
7-day average
0
peak 1
Rank
#9,176
top 41%
Last wipe
13h ago
biweekly schedule
Next wipe
7d 4h
Thu 5 Nov, 19:00 UTC FW
Obs. 1 · sightings

Players

AveragePeakWipe
00.250.50.75115:0000:0009:0017:0003:0012:00Wiped Thu 29 Oct, 00:04 UTCWIPE

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

Server fpsWipe
010020030040015:0000:0009:0017:0003:0012: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.

Obs. 3 · standing

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.

Obs. 4 · the wipe cycle

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. 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

7d 4h
Thu 5 Nov, 19:00 UTC
FW
13d 10h
Thu 12 Nov, 00:04 UTC
27d 10h
Thu 26 Nov, 00:04 UTC
35d 4h
Thu 3 Dec, 19:00 UTC
FW
41d 10h
Thu 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.

Log · wipes seen

Wipes

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

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.

Field questions

Quick answers

from the figures on this page

Population

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

By player hours over the last seven days, SOLO_Новосибирск | WIPE 29.10 places at #9,176, within the top 41% of ranked servers.

How busy is SOLO_Новосибирск | WIPE 29.10?

SOLO_Новосибирск | WIPE 29.10 holds 0 players at the moment, out of 50 slots. Averaged over seven days, it drew 0 players and reached a peak of 1. In the last 48 hours the peak hour came at 10:00 UTC, averaging 0 players.

Tags

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

These are the tags SOLO_Новосибирск | WIPE 29.10 publishes, as read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): 50 slots are available; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded; jp0 (Custom tag): This tag falls outside Rust's standard set; the owner or a plugin set it. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include SOLO_Новосибирск | WIPE 29.10?

These Rust Population lists include SOLO_Новосибирск | WIPE 29.10: Rust servers in Europe and Modded Rust servers, counted. Filter the server list by 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 will show up.

Wipe notes

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

Averaged over recent wipes, 2 players were counted at the busiest point. 14 hours after the latest wipe the crowd peaked. Half that peak held until the next wipe in 25% of its recent wipes. In those that did not hold, the fall below half came by day 1.

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

Its tag sets the prediction: too few of SOLO_Новосибирск | WIPE 29.10's wipes are on record to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, which takes every Rust server. The world it runs now dates from 13 hours ago. Its tags set out a wipe schedule of one wipe every two weeks.

Map and rules

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

A procedural map of size 3,000 from seed 6630, generated by the game, is in use on SOLO_Новосибирск | WIPE 29.10. Size and seed together fix the map, so you can view it on RustMaps from this page.

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

The name tells you nothing about gather rates: SOLO_Новосибирск | WIPE 29.10 states none. The group limit is 8 players, which is the default. This server runs survival, gather, build and raid, as in the standard game. You can raid and fight other players here. You find it under Modded, since plugins or settings change how it plays. Oxide plugins are in use here. VAC, Valve's anti-cheat, runs here.

Server details

Which version of Rust does SOLO_Новосибирск | WIPE 29.10 run?

On Linux, SOLO_Новосибирск | WIPE 29.10 runs Rust network protocol 2635 and build 168909. Your game needs the same protocol to join; Steam takes care of updating it.

Does SOLO_Новосибирск | WIPE 29.10 run smoothly?

In the last 48 hours, it averaged 229 server fps, with a low of 212. Entities peaked at 44,901, including buildings, deployables and everything else. The highest memory usage was 2,980 MB. What players experience as lag comes from low fps and a rising entity count.

Is SOLO_Новосибирск | WIPE 29.10 online, and how reliable is it?

SOLO_Новосибирск | WIPE 29.10 is up and running at the moment. About 10 hours ago, it restarted, according to its uptime. Over the last 7 full days, 167 of 168 hours were online, or 99%. The first sighting by Rust Population was on 13 September 2026.

Where is SOLO_Новосибирск | WIPE 29.10 located?

No region tag comes from SOLO_Новосибирск | WIPE 29.10, but the name points to Europe. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. Connect at 212.20.40.180:28015.

How to join

How do I join SOLO_Новосибирск | WIPE 29.10?

Either enter client.connect 212.20.40.180:28015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.

Key to its markings

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 form.
mp50
Max players 50 slots are available.
ts8
Group limit This is the game default: at most 8 per team.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly A wipe happens once a fortnight.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) runs on this server.
^z
Modded The game is changed by plugins or settings, so it is listed under Modded.

Other

jp0
Custom tag This tag falls outside Rust's standard set; the owner or a plugin set it.

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.