Rust Server IndexCard catalogue of Rust servers

Holdings11,782 servers67,928 players196 fresh wipes

Call no.9189 On the shelf · online

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

Online 212.20.40.180:28015 checked 12m ago

Subjects 1. biweekly wipes 2. modded3. oxide
Players now
0/ 50
0% full
7-day average
0
peak 1
Rank
#9,189
top 41%
Last wipeWiped29 OCT2026 · 12h ago
12h ago · biweekly schedule
Next wipe
7d 6h
Thu 5 Nov, 19:00 UTC FW
Call slipPaste it into the F1 console
Record sheet A · appended

Players

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

Hourly average and peak, UTC.

Record sheet B · appended

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.

Record sheet C · appended

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.

Record sheet D · loan terms

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. in 7d 6hThu 5 Nov, 19:00 UTCFW
  2. in 13d 11hThu 12 Nov, 00:04 UTC
  3. in 27d 11hThu 26 Nov, 00:04 UTC
  4. in 35d 6hThu 3 Dec, 19:00 UTCFW
  5. in 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.

Record sheet E · date due

Wipes

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

Shelf list · shelved beside it

Similar servers

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

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

Quick answers

From the figures on this page.

Rules and settings

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

You will find no gather rate in the name of SOLO_Новосибирск | WIPE 29.10. 8 players per group is the default limit. The server runs survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Oxide. The server has VAC, Valve's anti-cheat, turned on.

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

Generated by the game, the procedural map of SOLO_Новосибирск | WIPE 29.10 has size 3,000 and seed 6630. You can view the map on RustMaps from this page, as the same size and seed give the same map.

Tags and filters

On Rust Server Index, which lists and filters carry SOLO_Новосибирск | WIPE 29.10?

These lists on Rust Server Index take SOLO_Новосибирск | WIPE 29.10: Rust servers filed under Europe and Modded Rust servers, filed by play style. These filters on the server list bring it up: 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 should you read the tags listed for SOLO_Новосибирск | WIPE 29.10?

These are the tags SOLO_Новосибирск | WIPE 29.10 publishes; the game's server browser reads this list: gmvanilla (Game mode): Filed under vanilla survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): Joining needs you on game protocol 2635; cs168909 (Build): Build on file: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set; ^b (Biweekly): The cycle runs to a wipe every fortnight; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): This one is Modded, since plugins or settings change how it plays; jp0 (Custom tag): A custom tag: set by the owner or a plugin, not by Rust itself. The top of this page shows three items from the tags: players at present, queue and world creation time.

Wipe schedule

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

Its recent wipes averaged 2 players at peak. The latest wipe peaked 14 hours in. Its recent wipes kept the crowd above half the peak until the next wipe 25% of the time. In the other cases, numbers dropped below half by day 1.

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

Too few wipes of SOLO_Новосибирск | WIPE 29.10 are recorded to confirm its schedule, so the tag sets the prediction. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, taken by every Rust server. Its present world dates from 12 hours. Filed in its tags: a wipe schedule of every two weeks.

Player counts

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

Filed under rankings: #9,189 for SOLO_Новосибирск | WIPE 29.10 on seven-day player hours, top 41% overall.

How many players are on SOLO_Новосибирск | WIPE 29.10 at the moment?

Filed under live counts: SOLO_Новосибирск | WIPE 29.10, 0 players on 50 slots at present. Filed under seven-day figures: an average of 0 players and a peak of 1. Filed under busiest hour: 10:00 UTC in the last 48 hours, averaging 0 players.

Operator and status

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

Rust network protocol 2635 and build 168909, on Linux, is what SOLO_Новосибирск | WIPE 29.10 runs. Steam keeps your game updated, but the protocol must match for you to join.

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

Right now SOLO_Новосибирск | WIPE 29.10 is up and running. The uptime it reports puts the last restart at about 10 hours ago. Uptime for the last 7 full days came to 99%, 167 hours out of 168. It was first recorded by Rust Server Index on 13 September 2026.

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

The last 48 hours give an average of 230 server fps and a floor of 212. Buildings, deployables and everything else in the world came to as many as 44,901 entities. Up to 2,980 MB of memory was in use. Lag, to players, is low fps and an entity count that climbs.

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

SOLO_Новосибирск | WIPE 29.10 gives no region tag, so the name is the only pointer, and it points to Europe. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 212.20.40.180:28015.

Joining the server

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

If you would rather use the console, press F1 in Rust and enter client.connect 212.20.40.180:28015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmvanilla
Game mode Filed under vanilla survival.
mp50
Max players 50 slots are available.
ts8
Group limit Teams cap at 8, the default setting.
v2635
Protocol Joining needs you on game protocol 2635.
cs168909
Build Build on file: 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly The cycle runs to a wipe every fortnight.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded This one is Modded, since plugins or settings change how it plays.

Other

jp0
Custom tag A custom tag: set by the owner or a plugin, not by Rust itself.

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.