Open every day, at every hour Admission free 11,777 servers and 67,749 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

This server publishes no banner

Exhibit no. 9,189Acc. 2026.9189

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

Rust server · in the archive since 13 September 2026

Online 212.20.40.180:28015 checked 12m ago

biweekly wipes moddedoxide
To visit
Players now 0/ 50
0% full
7-day average0peak 1
Rank#9,189top 41%
Last wipe12h agoThu 29 Oct, 00:04 UTC · biweekly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectednow, 29 Oct 2026, 12:30 UTCAll times UTC.

The record of each wipe

  1. Thu 29 Oct 202600:04 UTC12h ago
    Peak
    –
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Thu 15 Oct 202600:04 UTC14d ago
    Peak
    2
    Crowd
    halved by day 1
    Lasted
    14 days
    Players before
    0
  3. Fri 9 Oct 202618:11 UTC19d ago
    Peak
    2
    Crowd
    held half
    Lasted
    5.2 days
    Players before
    1
  4. Thu 1 Oct 202618:07 UTC FW27d ago
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    8 days
    Players before
    0
  5. Thu 1 Oct 202605:31 UTC28d ago
    Peak
    1
    Crowd
    –
    Lasted
    0.5 days
    Players before
    0
  6. Thu 17 Sep 202600:02 UTC42d ago
    Peak
    1
    Crowd
    halved by day 9
    Lasted
    14.2 days
    Players before
    0
  7. Mon 14 Sep 202611:24 UTC45d ago
    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.

The rhythm

Wipe schedule

from its schedule tag

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

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

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

Hourly average and peak, UTC.

Folder 2

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.

Folder 3

Rank

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.

Related exhibits

Similar servers

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

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags, lists

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

These tags from SOLO_Новосибирск | WIPE 29.10, read by the game's server browser, are: gmvanilla (Game mode): Vanilla survival is the mode; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the default the game ships; v2635 (Protocol): The server runs game protocol 2635; matching it is required to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The region code field is empty; ^b (Biweekly): A wipe every fortnight; ^o (Oxide): A plugin framework, Oxide (uMod), is installed here; ^z (Modded): Under Modded: the game is changed by plugins or settings; jp0 (Custom tag): Standard Rust does not define this tag; the owner or a plugin added it. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.

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

These Rust Server History lists include SOLO_Новосибирск | WIPE 29.10: European Rust servers and Modded Rust servers: the record. It appears under these filters on the server list: 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.

The record

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

Averaged over the last 48 hours: 230 server fps, with 212 the lowest. As many as 44,901 entities were in the world: buildings, deployables and the rest. Memory use peaked at 2,980 MB. Players feel lag when fps drop and the entity count climbs.

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

The recorded build for SOLO_Новосибирск | WIPE 29.10 is Rust network protocol 2635 and build 168909 on Linux. The protocol must match to join, and Steam handles that update.

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

The live count shows SOLO_Новосибирск | WIPE 29.10 online right now. About 10 hours ago is when it last restarted, judged by the uptime it reports. Of 168 hours in the last 7 full days, 167 were up: 99% of the time. The first sighting by Rust Server History was on 13 September 2026.

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

Its name points to Europe, though SOLO_Новосибирск | WIPE 29.10 publishes no region tag. The location on Rust Server History is what a server says, not a lookup of where the machine stands. Its entry gives 212.20.40.180:28015 as the address.

Wipe history

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

At their busiest, its recent wipes drew an average of 2 players. At 14 hours after the latest wipe, the crowd reached its peak. Above half that peak until the next wipe it stayed in 25% of its recent wipes. The fall below half came by day 1 in those wipes where it didn't hold.

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

The prediction follows its tag because the record holds too few of SOLO_Новосибирск | WIPE 29.10's wipes 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 it runs now dates from 12 hours ago. A wipe every two weeks is published in its tags.

Population

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

Over seven days of player hours, SOLO_Новосибирск | WIPE 29.10 ranks #9,189, inside the top 41% of all ranked servers.

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

Of its 50 slots, SOLO_Новосибирск | WIPE 29.10 currently has 0 filled. The seven-day average stands at 0 players; the peak is 1. Stored history puts the busiest hour of the past 48 at 10:00 UTC, averaging 0 players.

Rules, map

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

No gather rate is stated in the name of SOLO_Новосибирск | WIPE 29.10. The limit of 8 players per group is the game's default. survival is the game mode, the usual game, with gathering, building and raiding. PvP and raiding are enabled. Under Modded in the server browser, the game is changed by plugins or settings. Plugins in use: Oxide. The anti-cheat VAC from Valve is active.

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

Seed 6630, size 3,000: such is the procedural map SOLO_Новосибирск | WIPE 29.10 runs, generated by the game. You can look at the map on RustMaps from this page, since one size and seed always give one map.

Joining the server

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

Press F1 in Rust to open the console, then enter client.connect 212.20.40.180:28015 to connect. Launch Rust from this page instead and you join through Steam with the connect already made.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmvanilla
Game mode Vanilla survival is the mode.
mp50
Max players The server holds 50 slots.
ts8
Group limit Teams are capped at 8, the default the game ships.
v2635
Protocol The server runs game protocol 2635; matching it is required to join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet handles the network layer, as standard for the game.
$r?
Region code The region code field is empty.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is installed here.
^z
Modded Under Modded: the game is changed by plugins or settings.

Other

jp0
Custom tag Standard Rust does not define this tag; the owner or a plugin added 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.