RUST METRICSFlight deck · live data
Data live Servers11,772 Players62,070 Populated3,548 Fresh wipes 3 h127 Scan5 min
‹ All servers157.85.86.209:26272
Offline Full Queue Fresh wipe Wipe due No query

UNbearABLE

Offline 157.85.86.209:26272 checked 3d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 2 /2

Players now

100% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average2peak 2
Rank#5,106top 23%
Last wipe5d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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 19 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
15k10k15k20k20 Sep27 Sep3 Oct10 Oct21 Oct28 Oct

Top 23% 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 rhythm20%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 3

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctSun 4 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 20:42 UTC5d ago 2 – running 1
Fri 16 Oct, 22:40 UTC11d ago 2 held half 6.9 days 1
Sun 4 Oct, 12:47 UTC24d ago 2 – 12.4 days 0
Wed 30 Sep, 17:47 UTC28d ago 2 – 3.8 days 1
Tue 29 Sep, 18:23 UTC29d ago 2 – 1 days 1
Mon 21 Sep, 18:59 UTC37d ago 2 halved by day 3 8 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

Reset cycle

What should you expect from wipe day on UNbearABLE?

An average of 2 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. By day 3 it fell below half when it didn't.

How often does UNbearABLE wipe, and when?

No next wipe can be predicted for UNbearABLE, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 5 days 1 hours ago.

Lists and filters

Which tags does UNbearABLE carry, and what do they mean?

Tags published by UNbearABLE, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does UNbearABLE appear in Rust Metrics lists and filters?

On Rust Metrics, UNbearABLE sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Player count

What position does UNbearABLE hold among Rust servers?

Player hours over seven days put UNbearABLE at #5,106, in the top 23% of all ranked servers.

What player count does UNbearABLE carry?

UNbearABLE is not responding; status offline, last seen 3 days 8 hours ago. Check: players over seven days. Average 2, peak 2.

Server

What location is UNbearABLE hosted in?

No region tag on UNbearABLE. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 157.85.86.209:26272.

What Rust version is UNbearABLE on?

Rust network protocol 2635 and build 168909 on Linux is the build UNbearABLE runs. Check: protocol. To join, your game must match; Steam handles the update.

Is UNbearABLE up, and how often does it stay up?

UNbearABLE reports offline. The last reading came 3 days 8 hours ago. Reading: 14% uptime over the last 7 full days. It was up 24 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does UNbearABLE enforce, and what are its settings?

Check: gather rate. The name UNbearABLE does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on UNbearABLE?

Size 1,800 and seed 1789132995: the game generates the procedural map on UNbearABLE from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

What do you do to join UNbearABLE?

Press F1 in Rust and enter client.connect 157.85.86.209:26272. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players The server holds 2 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.