RUST METRICSFlight deck · live data
Data live Servers11,847 Players92,510 Populated3,855 Fresh wipes 3 h385 Scan5 min
‹ All servers157.85.91.32:24049
Offline Full Queue Fresh wipe Wipe due No query

TrexLuke64

Offline 157.85.91.32:24049 checked 6d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

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,344top 69%
Last wipe12d agono schedule published
Next wipe–too few wipes 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, measured since 23 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
15k10k15k20k23 Sep30 Sep7 Oct15 Oct22 Oct29 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 04:10 UTC12d ago 0 – running 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 should you expect from wipe day on TrexLuke64?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does TrexLuke64 wipe?

The rhythm of TrexLuke64's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 12 days 11 hours ago.

Tag meanings

How should you read the tags on TrexLuke64?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): Slots: 40; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from TrexLuke64. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TrexLuke64?

On Rust Metrics, TrexLuke64 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 2 weeks.

Occupancy

Where does TrexLuke64 sit in the rankings?

Player hours over seven days put TrexLuke64 at #15,344, in the top 69% of all ranked servers.

What is the population on TrexLuke64?

Reading for TrexLuke64: offline at this moment; last seen 6 days 23 hours ago. Seven-day reading: 0 players on average.

Operator and location

What location is TrexLuke64 hosted in?

Reading: location. TrexLuke64 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 157.85.91.32:24049.

What Rust version is TrexLuke64 on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by TrexLuke64. To get in, your game needs the same protocol; Steam applies the update.

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

TrexLuke64 reports offline. The last reading came 6 days 23 hours ago. Reading: 10% uptime over the last 7 full days. It was up 16 of 168 hours. The first sighting on Rust Metrics was 23 September 2026.

Rules and settings

What settings and rules apply on TrexLuke64?

Check: gather rate. The name TrexLuke64 does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is TrexLuke64 on?

Check: map. Procedural, size 1,500, seed 50000, generated by the game on TrexLuke64. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How do you connect to TrexLuke64?

Press F1 in Rust and enter client.connect 157.85.91.32:24049. 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 mp40,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp40
Max players Slots: 40.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
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.