Rust PopulationField survey · Rust servers
Observing 46,789 players 11,635 servers 3,178 with someone on 97 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 15,064habitat unknownfirst seen 6 Oct 2026

Testing

Online 90.146.82.82:28035 checked 9m ago

moddedcarbon

Measurements

Players now
0/ 10
0% full
7-day average
0
peak 1
Rank
#15,064
top 68%
Last wipe
4d ago
no schedule published
Next wipe
–
too few wipes seen yet
Obs. 1 · sightings

Players

AveragePeak
0123409:0018:0003:0013:0022:0007:00

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
15k10k15k20k6 Oct10 Oct15 Oct19 Oct24 Oct28 Oct

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

Obs. 4 · the wipe cycle

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.

1
wipe-day peak
players, last three wipes

The first 48 hours of its last wipes

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

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

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 22:03 UTC4d ago 1 – running 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 Testing rank against other Rust servers?

The last seven days of player hours place Testing at #15,064, within the top 68% of all ranked servers.

How busy is Testing?

The count reads 0 players on Testing, which has 10 slots. Seven days of counting give an average of 0 players and a peak of 1.

Tags

What do the server tags on Testing mean?

The game's server browser reads the tags Testing publishes: gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^z (Modded): This server appears under Modded because plugins or settings alter the game; ^y (Carbon): The plugin framework Carbon runs on this server. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include Testing?

These Rust Population lists include Testing: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Wipe schedule

What does wipe day look like on Testing?

Averaged over recent wipes, 1 players were counted at the busiest point. 4 hours after the latest wipe the crowd peaked.

What is the wipe schedule on Testing?

Its rhythm cannot be told yet: too few of Testing's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 4 days 10 hours ago, that is how long the current world has stood.

Map and rules

Which map does Testing run?

A procedural map, generated by the game, is in use on Testing.

What are the rules and settings on Testing?

Nothing in Testing's name says how gather works. The group limit is 8 players, which is the default. This server runs survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. You find it under Modded, since plugins or settings change how it plays. Carbon plugins are in use here. VAC, Valve's anti-cheat, runs here.

About the server

Which version of Rust does Testing run?

On Linux, Testing runs Rust network protocol 2635 and build 168909. Your game needs the same protocol to join; Steam takes care of updating it.

Is Testing online, and how reliable is it?

You will find Testing online now. It was up 100% of the time over the last 7 full days, 168 out of 168 hours. The first sighting by Rust Population was on 6 October 2026.

Where is Testing located?

A region is not published by Testing. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 90.146.82.82:28035.

How to join

How do I join Testing?

Either enter client.connect 90.146.82.82:28035 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.

Key to its markings

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y

Game

gmvanilla
Game mode This is vanilla survival.
mp10
Max players 10 slots are available.
ts8
Group limit 8 per team is the default limit.
v2635
Protocol Your game needs the same version, protocol 2635, to join.
cs168909
Build The game build is 168909.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code The region code is left blank.

Mods and access

^z
Modded This server appears under Modded because plugins or settings alter the game.
^y
Carbon The plugin framework Carbon runs on this server.

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.