At press time 11,617 servers35,735 players74 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 15,341

LRUST | x2 Vanilla+ | BP Share | Biweekly

Online 149.202.49.90:28015 checked 13m ago

LRUST | x2 Vanilla+ | BP Share | Biweekly is a Rust server. At the last count it had 0 players of a possible 50. It stands at No. 15,341 of the ranked servers, the top 69%. It last wiped 26d ago. Its own tags class it as 2x, modded, oxide.

§ 1Attendance

AveragePeak
0123407:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

§ 2Performance

010020030040007:0016:0001:0010:0020:0005:00

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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

§ 3Standingthe rank, daily · 1 is best

RankRank in region
15k10k15k20k28 Sep4 Oct10 Oct17 Oct23 Oct29 Oct

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

§ 4The wipe scheduletoo few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

The rhythm
Usual gap3 days

between real wipes

Wipe-day peak6

players, last three wipes

Crowd held0%

else halves by day 1

The first 48 hours of its last wipes

Fri 2 OctTue 29 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 25 hours in.

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 20:07 UTC26d ago 4 – running 0
Tue 29 Sep, 20:21 UTC29d ago 7 halved by day 1 3 days 1

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.

§ 6In its own wordsas the server describes itself

x2 gather | BP SHARE | Biweekly wipe No kits, no TP, no shop - just vanilla, boosted Build remove : /remove New seed every wipe Max 50 players

§ 7Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes335/350 EU · groups of 16+ · 2x · monthly · 809 on average
  2. 2 Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes136/150 EU · groups of 16+ · 2x · monthly · 601 on average
  3. 3 Atlas - US 2X Monthly | Vanilla+ | No BP Wipes96/150 NA · groups of 16+ · 2x · monthly · 372 on average
  4. 4 EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr43/150 EU · groups of 50+ · 2x · monthly · 350 on average
  5. 5 Magic Rust #18 — Vanilla 2x | Baйп 28.10786/670 EU · groups of 150+ · 2x · weekly · 331 on average
  6. 6 MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.1063/1000 EU · groups of 300+ · 2x · weekly · 314 on average

§ 8Questions answeredfrom the figures in this entry

Server record

The Rust version for LRUST | x2 Vanilla+ | BP Share | Biweekly: which one?

The server LRUST | x2 Vanilla+ | BP Share | Biweekly is on Rust network protocol 2634 and build 167781, hosted on Linux. To join, your game must be on the same protocol; Steam handles the update.

How reliable is LRUST | x2 Vanilla+ | BP Share | Biweekly, and is it online now?

LRUST | x2 Vanilla+ | BP Share | Biweekly currently answers as online. Of note: the reported uptime places the last restart about 7 days 7 hours ago. In the last 7 full days it was up for 167 of 168 hours, 99% of the time. The first sighting at Rust Server Stats was on 28 September 2026.

What is the performance of LRUST | x2 Vanilla+ | BP Share | Biweekly like?

For the last 48 hours the average was 151 server fps, with a low of 102. The entity count reached 49,914: buildings, deployables and all else in the world. Up to 2,969 MB of memory was used. An entity count climbing and fps running low are felt in-game as lag.

Where does LRUST | x2 Vanilla+ | BP Share | Biweekly operate from?

No region is published by LRUST | x2 Vanilla+ | BP Share | Biweekly. Rust Server Stats records the stated location of a server, not the location of the machine. At 149.202.49.90:28015 stands the address.

Rules, settings, map

The map for LRUST | x2 Vanilla+ | BP Share | Biweekly: which one is it?

LRUST | x2 Vanilla+ | BP Share | Biweekly runs a procedural map, generated by the game, of size 3,000 with seed 2142499688. Because size and seed fix the map, it can be viewed on RustMaps from here.

What settings and rules does LRUST | x2 Vanilla+ | BP Share | Biweekly run?

By its own name, LRUST | x2 Vanilla+ | BP Share | Biweekly gathers at 2x. The group limit is 8 players, the game's default. Play is survival, gather, build and raid: the standard game. Player-versus-player fighting and raiding are enabled. The server browser lists it under Modded, where plugins or settings alter the game. Plugins run here: Oxide. The VAC anti-cheat from Valve is active.

Player record

What are the player numbers on LRUST | x2 Vanilla+ | BP Share | Biweekly?

0 players are on LRUST | x2 Vanilla+ | BP Share | Biweekly at present; the slot count is 50. Averaged over the last seven days, the population is 0 players.

Where does LRUST | x2 Vanilla+ | BP Share | Biweekly sit in the rankings?

The seven-day player-hour table places LRUST | x2 Vanilla+ | BP Share | Biweekly at #15,341, within the top 69% of ranked servers.

Tags, lists

Where does LRUST | x2 Vanilla+ | BP Share | Biweekly appear among the Rust Server Stats lists and filters?

These are the Rust Server Stats lists that include LRUST | x2 Vanilla+ | BP Share | Biweekly: 2x Rust servers and Modded Rust servers. On the server list it comes up under these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.

How should the tags on LRUST | x2 Vanilla+ | BP Share | Biweekly be read?

gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 is the number of slots; ts8 (Group limit): The default applies: 8 per team; v2634 (Protocol): Join only on protocol 2634; other versions cannot connect; cs167781 (Build): The build number is 167781; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code absent; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the browser lists it as Modded — that is the set of tags LRUST | x2 Vanilla+ | BP Share | Biweekly publishes for the game's browser. The tags also carry its current players, its queue and the date its world was made. These appear at the top of this page.

Wipe record

What happens on LRUST | x2 Vanilla+ | BP Share | Biweekly when wipe day arrives?

The average peak across recent wipes was 6 players. 25 hours after the latest wipe, the crowd peaked. The crowd held above half the peak until the next wipe in 0% of recent wipes. In those cases the crowd dropped below half by day 1.

The wipe timetable for LRUST | x2 Vanilla+ | BP Share | Biweekly: what does it show?

Too few wipes of LRUST | x2 Vanilla+ | BP Share | Biweekly are on record to establish its rhythm. The monthly force wipe falls on every Rust server alike, and Thursday 5 November at 19:00 UTC is the next one. The present world dates from 26 days 10 hours.

Connection

Which steps join LRUST | x2 Vanilla+ | BP Share | Biweekly?

To connect, open the console with F1 in Rust and enter client.connect 149.202.49.90:28015. The Launch Rust and join button on this page does the same through Steam.

§ 9Key to the tagswhat each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp50
Max players 50 is the number of slots.
ts8
Group limit The default applies: 8 per team.
v2634
Protocol Join only on protocol 2634; other versions cannot connect.
cs167781
Build The build number is 167781.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code absent.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the browser lists it as Modded.

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.