RUST METRICSFlight deck · live data
Data live Servers11,694 Players35,972 Populated2,914 Fresh wipes 3 h94 Scan5 min
‹ All servers144.31.239.85:29015
Offline Full Queue Fresh wipe Wipe due No query

LOCAL UPDATE TEST

Offline 144.31.239.85:29015 checked 16d 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,547top 71%
Last wipe16d 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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

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

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

Wipe timing

What wipe timing does LOCAL UPDATE TEST follow?

The rhythm of LOCAL UPDATE TEST'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. 16 days 15 hours ago the current world was made.

Tags

How should you read the tags on LOCAL UPDATE TEST?

These are the tags LOCAL UPDATE TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167584 (Build): Build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does LOCAL UPDATE TEST appear in Rust Metrics lists and filters?

On Rust Metrics, LOCAL UPDATE TEST 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.

Occupancy

Where does LOCAL UPDATE TEST sit in the rankings?

Player hours over seven days put LOCAL UPDATE TEST at #15,547, in the top 71% of all ranked servers.

What player count does LOCAL UPDATE TEST carry?

Status for LOCAL UPDATE TEST: offline. Last seen 16 days 15 hours ago.

Operator and location

Which location does LOCAL UPDATE TEST run from?

No region comes from LOCAL UPDATE TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 144.31.239.85:29015.

What Rust version is LOCAL UPDATE TEST on?

Rust network protocol 2634 and build 167584 on Windows is the build LOCAL UPDATE TEST runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is LOCAL UPDATE TEST, and is it online now?

Check: connection. LOCAL UPDATE TEST is offline at this moment. Last contact was 16 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 12 October 2026.

Settings and map

How is LOCAL UPDATE TEST configured, and what rules are in force?

Reading the name gives no gather rate for LOCAL UPDATE TEST. 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. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is LOCAL UPDATE TEST on?

Procedural map on LOCAL UPDATE TEST, made by the game's generator.

Connection

How do you connect to LOCAL UPDATE TEST?

Check: join. Open Rust, press F1, then enter client.connect 144.31.239.85:29015. 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?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167584
Build Build 167584.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.