RUST METRICSFlight deck · live data
Data live Servers11,681 Players34,835 Populated2,855 Fresh wipes 3 h93 Scan5 min
‹ All servers71.193.134.10:28019
Offline Full Queue Fresh wipe Wipe due No query

Rust Provider Runtime Test - Private LAN

Offline 71.193.134.10:28019 checked 12d ago

COM 1 · connect

Server instruments

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

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,128top 70%
Last wipe13d 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
15k10k15k20k16 Oct17 Oct19 Oct20 Oct22 Oct23 Oct

Top 70% 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 schedule

When does Rust Provider Runtime Test - Private LAN wipe?

To tell the rhythm of Rust Provider Runtime Test - Private LAN, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 13 days ago the current world was made.

Lists and filters

How should you read the tags on Rust Provider Runtime Test - Private LAN?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Rust Provider Runtime Test - Private LAN. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Rust Provider Runtime Test - Private LAN appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Rust Provider Runtime Test - Private LAN: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does Rust Provider Runtime Test - Private LAN sit in the rankings?

Player hours over seven days put Rust Provider Runtime Test - Private LAN at #15,128, in the top 70% of all ranked servers.

What player count does Rust Provider Runtime Test - Private LAN carry?

Rust Provider Runtime Test - Private LAN is not responding; status offline, last seen 12 days 5 hours ago.

Operator and location

Where does Rust Provider Runtime Test - Private LAN sit?

No region comes from Rust Provider Runtime Test - Private LAN. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 71.193.134.10:28019.

What Rust version is Rust Provider Runtime Test - Private LAN on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by Rust Provider Runtime Test - Private LAN. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Rust Provider Runtime Test - Private LAN, and is it online?

Check: connection. Rust Provider Runtime Test - Private LAN is offline at this moment. Last contact was 12 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 16 October 2026.

Map and rules

What rules does Rust Provider Runtime Test - Private LAN enforce, and what are its settings?

Reading the name gives no gather rate for Rust Provider Runtime Test - Private LAN. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is Rust Provider Runtime Test - Private LAN on?

Check: map. Procedural, generated by the game, on Rust Provider Runtime Test - Private LAN.

Join

How do you connect to Rust Provider Runtime Test - Private LAN?

To join: start Rust, press F1 and type client.connect 71.193.134.10:28019. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players The server holds 2 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 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.