Rust PopulationField survey · Rust servers
Observing 40,773 players 11,615 servers 3,012 with someone on 86 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 15,412habitat unknownfirst seen 13 Sep 2026

LocalTest

Offline 104.28.232.201:28015 checked 5d ago

Measurements

Players now
0/ 5
0% full
7-day average
0
peak –
Rank
#15,412
top 69%
Last wipe
5d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct28 Oct

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

Obs. 4 · the wipe cycle

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.

5.1 days
usual gap
between real wipes
33%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 22 OctTue 13 OctThu 8 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 12:04 UTC5d ago 0 – running 1
Tue 13 Oct, 12:26 UTC14d ago 1 – 9 days 0
Thu 8 Oct, 14:12 UTC19d ago 1 – 4.9 days 1
Wed 7 Oct, 19:30 UTC20d ago 1 – 0.8 days 1
Fri 2 Oct, 13:27 UTC25d ago 1 – 5.3 days 1
Sun 20 Sep, 15:32 UTC37d ago 1 held half 11.9 days 1
Thu 17 Sep, 07:12 UTC41d ago 1 – 3.3 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.

Field questions

Quick answers

from the figures on this page

Population

How does LocalTest rank against other Rust servers?

The last seven days of player hours place LocalTest at #15,412, within the top 69% of all ranked servers.

How busy is LocalTest?

At this count LocalTest is offline, with its last sighting 5 days 17 hours ago. We counted 0 players on average across the past week.

Tags

What do the server tags on LocalTest mean?

The game's server browser reads the tags LocalTest publishes: gmrust (Game mode): Survival in the standard Rust style; mp5 (Max players): The server has 5 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include LocalTest?

These Rust Population lists include LocalTest: Community servers, field-listed. Filter the server list by Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week and it will show up.

Wipe notes

What does wipe day look like on LocalTest?

Averaged over recent wipes, 1 players were counted at the busiest point. The crowd on the latest wipe peaked 2 hours in. Half that peak held until the next wipe in 100% of its recent wipes.

What is the wipe schedule on LocalTest?

There is no next wipe to predict: LocalTest wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 5 days 19 hours ago, that is how long the current world has stood.

Settings

Which map does LocalTest run?

The map on LocalTest is procedural, made by the game.

What are the rules and settings on LocalTest?

The name tells you nothing about gather rates: LocalTest states none. No limit is set beyond the standard 8 players per group. survival is what it runs, raid, build and gather: the standard game. Fighting and raiding between players is allowed. You will find it under Community: it is a community server. The anti-cheat VAC from Valve is enabled.

Server details

Which version of Rust does LocalTest run?

On Windows, LocalTest runs Rust network protocol 2634 and build 167781. Your game needs the same protocol to join; Steam takes care of updating it.

Is LocalTest online, and how reliable is it?

We last saw LocalTest 5 days 17 hours ago, and it is offline now. It was up 1% of the time over the last 7 full days, 1 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.

Where is LocalTest located?

Nothing published by LocalTest states a region. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 104.28.232.201:28015.

How to join

How do I join LocalTest?

To connect directly, open Rust's console with F1 and type client.connect 104.28.232.201:28015; or press Launch Rust on this page and Steam opens Rust and joins for you.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp5
Max players The server has 5 slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2634
Protocol Your game needs the same version, protocol 2634, to join.
cs167781
Build Game build: 167781.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code The region code is left blank.

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.