Rust Data

rustdata.spaceservers85.172.104.178:35381.ipynb

Run all rust-data · live

‹ All servers

Online 85.172.104.178:35380 checked 9m ago

theBest | X3 | TP | SETHOME | NOLIMIT

3x biweekly wipes moddedoxide

Connect

srv = rust.server("85.172.104.178:35381")
print(srv.connect_command)

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 3 # peak 12
rank #1,915 # top 9%
last wipe 13d ago # biweekly schedule
next wipe 7d 17h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
0246802:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608002:0011:0020:0005:0014:0000: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · fixed weekdays

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 17h. # The force wipe · high confidence

usual gap28 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak11players, last three wipes
crowd held50%else halves by day 10

Coming wipes

inatkind
07d 17hThu 5 Nov, 19:00 UTCFW force wipe
114d 5hThu 12 Nov, 06:59 UTCwipe
235d 17hThu 3 Dec, 19:00 UTCFW force wipe
342d 5hThu 10 Dec, 06:59 UTCwipe

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 13, 11 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 15 Oct, 06:59 UTC13d ago 13 NaN running 1
1 Thu 1 Oct, 18:20 UTC FW27d ago 11 held half 13.5 days 1
2 Thu 17 Sep, 07:12 UTC41d ago 10 halved by day 10 14.5 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.

display(srv.map, srv.info())

Map

4500 · seed 762259399
Map of theBest | X3 | TP | SETHOME | NOLIMIT
map
Procedural Map
size
4500
seed
762259399
Open on RustMaps

Server

srv.info()
address
85.172.104.178:35380
region
–
max players
100
group limit
8, the default
wipe schedule
biweekly
last wipe
15 Oct 2026, 06:59 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Ищешь ламповый RUST-сервер с модами? Добро пожаловать на theBest! - Рейты ресурсов и компонентов х3 (сера остаётся честной — х1). - Вайпы строго по расписанию — два раза в месяц. - «Ночная защита от рейда» с 00:00 до 8:00 (МСК). - Стабильные плагины, авторские ивенты и даже куриные фермы. Каждый вайп мы добавляем новые фишки, чтобы игра не превращалась в рутину.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 125 on average438/470
1HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 121 on average110/120
2AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 105 on average59/100
3AceRust.com 3x Solo/Duo/Trio/Quad |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 11 on average9/150
4Bestrust X3 Solo/Duo/Trio - Weekly | Active AdminsEU · groups of 8+ · 3x · biweekly · 2 on average0/100
5OldFarts 3x Resources - No KOS - PVP zonesNA · groups of 128+ · 3x · biweekly · 2 on average0/100

Quick answers

From the figures on this page.

Population data

What position does theBest | X3 | TP | SETHOME | NOLIMIT take in the server rankings?

Rank #1,915 on seven-day player hours for theBest | X3 | TP | SETHOME | NOLIMIT, within the top 9% of all ranked servers.

How full does theBest | X3 | TP | SETHOME | NOLIMIT run?

Current row: 1 players on theBest | X3 | TP | SETHOME | NOLIMIT, against 100 slots. Over the last seven days it averaged 3 players and peaked at 12. Averaged by hour over 48 hours, 13:00 UTC is the busiest, at 6 players.

Server data

How well does theBest | X3 | TP | SETHOME | NOLIMIT perform?

The 48-hour average is 58 server fps, with a low of 31. Buildings, deployables and all else in the world took the count as high as 148,798 entities. Memory peaked at 4,836 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is theBest | X3 | TP | SETHOME | NOLIMIT on?

Rust network protocol 2635 and build 168909 on Windows is what theBest | X3 | TP | SETHOME | NOLIMIT runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is theBest | X3 | TP | SETHOME | NOLIMIT, and is it online now?

The current sample puts theBest | X3 | TP | SETHOME | NOLIMIT online. A restart about 22 hours ago is what its reported uptime implies. Uptime of 97% across the last 7 full days: 163 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is theBest | X3 | TP | SETHOME | NOLIMIT hosted?

No region is published by theBest | X3 | TP | SETHOME | NOLIMIT. Rust Data does not look up where the machine stands; it shows where a server says it is. 85.172.104.178:35380 is its address.

Rules, settings, map

What rules and settings are recorded for theBest | X3 | TP | SETHOME | NOLIMIT?

Gather sits at 3x, read from the server's own name: theBest | X3 | TP | SETHOME | NOLIMIT. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has theBest | X3 | TP | SETHOME | NOLIMIT selected?

theBest | X3 | TP | SETHOME | NOLIMIT runs a procedural map of size 4,500 with seed 762259399, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

When does theBest | X3 | TP | SETHOME | NOLIMIT wipe, and how often?

Wipes on theBest | X3 | TP | SETHOME | NOLIMIT run every 4 weeks on Thursday at 06:59 UTC. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 13 days 18 hours ago. A fortnightly wipe schedule is published in its tags.

What is wipe day on theBest | X3 | TP | SETHOME | NOLIMIT like?

The average peak over recent wipes is 11 players. Peak population on the latest wipe came 11 hours in. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. The drop under half arrived by day 10 in the other cases.

Tags, lists

Which lists on Rust Data hold theBest | X3 | TP | SETHOME | NOLIMIT, and which filters?

These Rust Data lists include theBest | X3 | TP | SETHOME | NOLIMIT: Modded Rust servers and 3x Rust servers, filtered live. Under these filters on the server list, it is listed: 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 2 weeks; Gather rate: 3x.

Which meanings do the tags on theBest | X3 | TP | SETHOME | NOLIMIT hold?

These tags are published by theBest | X3 | TP | SETHOME | NOLIMIT and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; oxidation (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to theBest | X3 | TP | SETHOME | NOLIMIT?

In Rust, F1 opens the console: type client.connect 85.172.104.178:35380. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://thebestx3.ru/.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,^b,gmvanilla,cs168909,ts8,^o^z,oxidation

Game

gmvanilla
Game mode Survival in vanilla form.
mp100
Max players 100 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Other

oxidation
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.

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.

Rust Data 41,011 players 11,701 servers online