RUST METRICSFlight deck · live data
Data live Servers11,898 Players102,471 Populated3,963 Fresh wipes 3 h334 Scan5 min
‹ All servers62.198.47.194:28015
Offline Full Queue Fresh wipe Wipe due No query

David's Solo Rust

Offline 62.198.47.194:28015 checked 2d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% full 7-day avg7-day peak
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 average1peak 1
Rank#6,827top 31%
Last wipe3d 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
15k10k15k20k20 Sep24 Sep15 Oct19 Oct22 Oct29 Oct

Top 31% 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.

usual gap12.2 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Mon 26 OctWed 14 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 15:40 UTC3d ago 1 – running 0
Wed 14 Oct, 12:01 UTC15d ago 1 – 12.2 days 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

Reset cycle

What should you expect from wipe day on David's Solo Rust?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

When does David's Solo Rust wipe?

Its rhythm cannot be told from the wipes of David's Solo Rust on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 3 days 2 hours ago.

Tag meanings

Which tags does David's Solo Rust carry, and what do they mean?

These are the tags David's Solo Rust publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $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.

Where does David's Solo Rust appear in Rust Metrics lists and filters?

These Rust Metrics lists carry David's Solo Rust: 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 week.

Occupancy

Where does David's Solo Rust sit in the rankings?

Player hours over seven days put David's Solo Rust at #6,827, in the top 31% of all ranked servers.

What player count does David's Solo Rust carry?

David's Solo Rust is not responding; status offline, last seen 2 days ago. Check: players over seven days. Average 1, peak 1.

Operator and location

What location is David's Solo Rust hosted in?

No region tag on David's Solo Rust. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 62.198.47.194:28015.

What Rust version is David's Solo Rust on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by David's Solo Rust. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on David's Solo Rust, and is it online?

David's Solo Rust reports offline. The last reading came 2 days ago. Uptime for the last 7 full days: 16 of 168 hours, or 10%. Reading: first seen 18 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on David's Solo Rust?

No gather rate appears in the name: David's Solo Rust. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is David's Solo Rust on?

Procedural map on David's Solo Rust, made by the game's generator.

Connection

How can you get onto David's Solo Rust?

Press F1 in Rust and enter client.connect 62.198.47.194: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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.