RUST METRICSFlight deck · live data
Data live Servers11,862 Players95,622 Populated4,072 Fresh wipes 3 h159 Scan5 min
‹ All servers152.89.199.20:35500
Online Full Queue Fresh wipe Wipe due No query

BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|

Online 152.89.199.20:35500 checked 11m ago

1.5x moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

last reading Tue 16:00 UTC
0 50 100 150 200 PAX 0 /200

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 91 SERVER FPS

Server fps

48 h low 67 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 119,811 ×1000

Entities

48 h range 119,633–120,484 · memory 3,676 MB
1239 ET SINCE RESTART 4D 02H

Uptime

4 days 2 hours since its last restart, at the last reading
7-day average0peak 1
Rank#12,400top 56%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps
Memory3,676MBat the last reading
REC 1

Players
AveragePeak
0123418:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

REC 2

Server performance
05010015020018:0003:0012:0022:0007:0016: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap6.9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 5

The first 48 hours of its last wipes

Tue 13 OctFri 2 OctFri 25 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 07:45 UTC14d ago 1 – running 0
Fri 2 Oct, 03:32 UTC25d ago 4 halved by day 6 11.2 days 0
Fri 25 Sep, 15:37 UTC32d ago 4 halved by day 3 6.5 days 0
Fri 18 Sep, 16:54 UTC39d ago 3 halved by day 5 6.9 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| when wipe day comes?

At their busiest, its recent wipes drew 3 players on average. 3 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 5 it fell below half when it didn't.

How often does BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| wipe, and when?

No next wipe can be predicted for BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 14 days 9 hours ago.

Tag meanings

How should you read the tags on BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp200 (Max players): 200 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| appear in Rust Metrics lists and filters?

On Rust Metrics, BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| sits in these lists: 1.5x Rust servers, checked live, EU Rust servers, checked and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 1.5x.

Player count

What position does BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| hold among Rust servers?

Player hours over seven days put BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| at #12,400, in the top 56% of all ranked servers.

What player count does BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| carry?

0 of 200 slots are filled on BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| right now. Check: players over seven days. Average 0, peak 1.

Server details

Where does BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| sit?

Reading: location. Nothing in the tags, but the name of BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| points to Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 152.89.199.20:35500.

What Rust version is BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| on?

Rust network protocol 2635 and build 168909 on Windows is the build BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| runs. To get in, your game needs the same protocol; Steam applies the update.

How does BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| perform?

Over the last 48 hours the average was 84 server fps; the floor was 67. Reading: 120,484 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,724 MB. Expect lag when fps falls and entities climb.

What is the uptime on BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|, and is it online?

BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 4 days 2 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| enforce, and what are its settings?

Gather rate check: 1.5x. That comes from the name BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++| on?

From seed 1403708994, the game generates the procedural map on BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|. Its size is 4,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto BTF #1 x1.5 Х2 |КИТ|TP|КЕЙСЫ|FPS+++|LOOT++|?

To join: start Rust, press F1 and type client.connect 152.89.199.20:35500. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp200
Max players 200 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.