RUST METRICSFlight deck · live data
Data live Servers11,755 Players63,128 Populated3,519 Fresh wipes 3 h137 Scan5 min
‹ All servers86.87.46.56:28015
Offline Full Queue Fresh wipe Wipe due No query

Jeffrey test server

Offline 86.87.46.56:28015 checked 16d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 1 /4

Players now

25% 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#13,605top 62%
Last wipe19d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct12 Oct15 Oct18 Oct

Top 62% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 07:12 UTC19d ago 1 – running 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.

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 Jeffrey test server?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 35 hours.

When does Jeffrey test server wipe?

The rhythm of Jeffrey test server'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 19 days 15 hours ago.

Tags

How should you read the tags on Jeffrey test server?

These are the tags Jeffrey test server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp4 (Max players): 4 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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 Jeffrey test server?

These Rust Metrics lists carry Jeffrey test server: 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.

Occupancy

What position does Jeffrey test server hold among Rust servers?

Player hours over seven days put Jeffrey test server at #13,605, in the top 62% of all ranked servers.

What is the population on Jeffrey test server?

Status for Jeffrey test server: offline. Last seen 16 days 11 hours ago.

Operator and location

Which location does Jeffrey test server run from?

No region tag on Jeffrey test server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 86.87.46.56:28015.

What Rust version is Jeffrey test server on?

Rust network protocol 2634 and build 167398 on Windows is the build Jeffrey test server runs. Matching protocol is required to join. Let Steam update your game.

How reliable is Jeffrey test server, and is it online now?

Jeffrey test server reports offline. The last reading came 16 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 4 October 2026, recorded by Rust Metrics.

Settings and map

What rules does Jeffrey test server enforce, and what are its settings?

No gather rate appears in the name: Jeffrey test server. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Jeffrey test server?

Procedural map on Jeffrey test server, made by the game's generator.

How to join

How can you get onto Jeffrey test server?

Press F1 in Rust and enter client.connect 86.87.46.56:28015. 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 mp4,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp4
Max players 4 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.