RUST METRICSFlight deck · live data
Data live Servers11,620 Players35,915 Populated2,914 Fresh wipes 3 h77 Scan5 min
‹ All servers85.64.209.86:28015
Offline Full Queue Fresh wipe Wipe due No query

RustRE Linux EOS bounded trace

Offline 85.64.209.86:28015 checked 42d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
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 average0peak –
Rank#15,441no region published
Last wipe42d agono schedule published
Next wipe–no wipe seen yet
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. 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 Sep21 Sep22 Sep
PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

How often does RustRE Linux EOS bounded trace wipe, and when?

The rhythm of RustRE Linux EOS bounded trace's wipes cannot be told yet: too few are on record. 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 42 days 11 hours ago.

Tags

Which tags does RustRE Linux EOS bounded trace carry, and what do they mean?

These are the tags RustRE Linux EOS bounded trace publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show RustRE Linux EOS bounded trace?

On Rust Metrics, RustRE Linux EOS bounded trace sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does RustRE Linux EOS bounded trace hold among Rust servers?

Player hours over seven days put RustRE Linux EOS bounded trace at #15,441, in the top – of all ranked servers.

What player count does RustRE Linux EOS bounded trace carry?

Status for RustRE Linux EOS bounded trace: offline. Last seen 42 days 8 hours ago.

Operator and location

What location is RustRE Linux EOS bounded trace hosted in?

No region comes from RustRE Linux EOS bounded trace. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 85.64.209.86:28015.

What Rust version is RustRE Linux EOS bounded trace on?

Rust network protocol 2633 and build 163794 on Linux is the build RustRE Linux EOS bounded trace runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on RustRE Linux EOS bounded trace, and is it online?

RustRE Linux EOS bounded trace reports offline. The last reading came 42 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Settings and map

What rules does RustRE Linux EOS bounded trace enforce, and what are its settings?

Check: gather rate. The name RustRE Linux EOS bounded trace does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is RustRE Linux EOS bounded trace on?

Procedural map on RustRE Linux EOS bounded trace, made by the game's generator.

Connection

How can you get onto RustRE Linux EOS bounded trace?

Check: join. Open Rust, press F1, then enter client.connect 85.64.209.86:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.