RUST METRICSFlight deck · live data
Data live Servers11,790 Players64,938 Populated3,582 Fresh wipes 3 h124 Scan5 min
‹ All servers64.40.8.191:29015
Online Full Queue Fresh wipe Wipe due No query

Lost In Rust Test Server

Online 64.40.8.191:29015 checked 12m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Wed 20:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg7-day peak 1, past the slots
0 10 30 60 120 256 FPS 30 SERVER FPS

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 105,472 ×1000

Entities

48 h range 104,651–107,789 · memory 3,077 MB
1239 ET SINCE RESTART 11:54

Uptime

11 h 54 min since its last restart, at the last reading
7-day average0peak 1
Rank#13,509top 61%
Last wipe21h agono schedule published
Next wipe–no rhythm it keeps
Memory3,077MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75100:0004:0008:0011:0015:0020:00Wiped Wed 28 Oct, 00:17 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
01020304000:0004:0008:0011:0015:0020:00Wiped Wed 28 Oct, 00:17 UTCWIPE

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 17 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.7 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Wed 21 OctTue 20 OctSun 18 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 00:17 UTC21h ago – – running 0
Wed 21 Oct, 01:48 UTC7d ago 1 halved by day 1 6.9 days 0
Tue 20 Oct, 02:08 UTC8d ago 1 – 1 days 0
Sun 18 Oct, 14:20 UTC10d ago 1 – 1.5 days 0
Thu 15 Oct, 00:20 UTC13d ago 0 – 3.6 days 0
Tue 13 Oct, 02:07 UTC15d ago 2+1 queue – 1.9 days 0
Mon 5 Oct, 23:57 UTC22d ago 1 halved by day 1 7.1 days 0
Sun 4 Oct, 15:37 UTC24d ago 2 – 1.3 days 1
Sat 3 Oct, 23:05 UTC24d ago 2 – 0.7 days 0
Sat 3 Oct, 02:31 UTC25d ago 2 – 0.9 days 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 timing

What happens on Lost In Rust Test Server when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 21 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.

What wipe timing does Lost In Rust Test Server follow?

No next wipe can be predicted for Lost In Rust Test Server, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 21 hours ago the current world was made.

Tag meanings

Which tags does Lost In Rust Test Server carry, and what do they mean?

These are the tags Lost In Rust Test Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): Slots: 0; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; 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; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server; oxidation (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Lost In Rust Test Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Lost In Rust Test Server: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Population

Where does Lost In Rust Test Server sit in the rankings?

Player hours over seven days put Lost In Rust Test Server at #13,509, in the top 61% of all ranked servers.

What is the population on Lost In Rust Test Server?

Reading for Lost In Rust Test Server: 0 players online now. Seven-day check: 0 players on average. Peak reading: 1. Check: 48-hour peak. 00:00 UTC, 1 players on average.

Server

What location is Lost In Rust Test Server hosted in?

No region comes from Lost In Rust Test Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 64.40.8.191:29015.

What Rust version is Lost In Rust Test Server on?

Reading: Lost In Rust Test Server, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for Lost In Rust Test Server?

Over the last 48 hours the average was 30 server fps; the floor was 30. Peak entity count: 107,789. Buildings, deployables and all else included. Memory peak: 3,563 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on Lost In Rust Test Server, and is it online?

Lost In Rust Test Server reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 11 hours ago. Uptime for the last 7 full days: 85 of 168 hours, or 51%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does Lost In Rust Test Server enforce, and what are its settings?

Check: gather rate. The name Lost In Rust Test Server does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on Lost In Rust Test Server?

Check: map. Procedural, size 4,700, seed 1337, generated by the game on Lost In Rust Test Server. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Custom Map.

How to join

How can you get onto Lost In Rust Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z,oxidation

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players Slots: 0.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
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.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

Other

oxidation
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.