Rust StatisticsWorking papers on every public Rust server · 76,398 players now

PopulaceLab (test)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 9h ago · 24.8.85.119:28335

Abstract

We describe the public Rust server PopulaceLab (test), reached at 24.8.85.119:28335. It is offline at the last check, against a seven-day mean of 0 and a peak of 11. It ranks #14,899 of all servers, the top 67%. It last wiped 1d ago.

Keywordsmodded carbon

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/30% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#14,899top 67%
Last wipe1d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeakWipe
00.250.50.75120:0002:0009:0015:0022:0004:00Wiped Mon 26 Oct, 20:37 UTCWIPE
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
Server fpsWipe
010020030040020:0002:0009:0015:0022:0004:00Wiped Mon 26 Oct, 20:37 UTCWIPE
Figure 2: Server performance. 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 26 Oct.

4Rank

The server stands in the top 67% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k17 Oct19 Oct21 Oct24 Oct26 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap4.5 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak0players, last three wipes
Sat 24 OctSat 17 Oct
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 26 Oct, 20:371d ago – – running 0
Sat 24 Oct, 21:383d ago 0 – 2 d 0
Sat 17 Oct, 18:2710d ago 1 – 7.1 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Custom map, no picture published
Figure 5: The map: Custom Map, size 4500, seed 1530458240.
Table 4: The server's published settings.
Address24.8.85.119:28335
Region–
Max players3
Group limit8, the default
Wipe schedule–
Last wipe26 Oct 2026, 20:37 UTC
Hostname–
First seen17 Oct 2026
MapCustom Map
Size4500
Seed1530458240

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 156 on average194/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average129/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average181/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average136/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average18/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average50/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does PopulaceLab (test) perform well?

Its average server fps over the last 48 hours was 236, with a minimum of 167. The highest number of entities it carried was 130,693, comprising buildings, deployables and all other objects. Its highest memory usage was 6,988 MB. Players experience lag when fps is low and the entity count is rising.

A.2In which location is PopulaceLab (test) based?

There is no region published for PopulaceLab (test). The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 24.8.85.119:28335 is its address.

A.3How reliable is PopulaceLab (test), and is it currently online?

At the present moment, PopulaceLab (test) is offline; it was last seen 9 hours ago. The uptime it reports indicates a restart about 31 hours ago. The server was up 18% of the time over the last 7 full days, 30 of 168 hours. The first record of it by Rust Statistics dates to 17 October 2026.

A.4What version of Rust is run on PopulaceLab (test)?

The version of Rust on PopulaceLab (test) is network protocol 2635 and build 168909, and the operating system is Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5When are wipes carried out on PopulaceLab (test)?

Prediction of the next wipe is impossible for PopulaceLab (test), which wipes irregularly. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The current world has been running for 41 hours.

A.6What characterises wipe day on PopulaceLab (test)?

Recent wipes saw an average peak of 0 players. The peak on the latest wipe came 0 hours after it began.

Population

A.7What is the rank of PopulaceLab (test) among Rust servers?

Ranked by player hours across seven days, PopulaceLab (test) holds #14,899, in the top 67% of all ranked servers.

A.8What is the population level of PopulaceLab (test)?

PopulaceLab (test) is not online now; 9 hours have passed since it was last seen. The peak over seven days is 1, against an average of 0. The busiest hour of the last 48 is 22:00 UTC, averaging 0 players.

Tags and filters

A.9What do the tags associated with PopulaceLab (test) signify?

The game's server browser reads gmvanilla (Game mode): Survival on vanilla rules; mp3 (Max players): It offers 3 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: plugins or settings modify the game; ^y (Carbon): The plugin framework is Carbon, which PopulaceLab (test) publishes as its tags. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.10Where can PopulaceLab (test) be found among the Rust Statistics lists and filters?

The Rust Statistics lists that PopulaceLab (test) fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Settings and map

A.11Which settings and rules are in force on PopulaceLab (test)?

No gather rate appears in the name of PopulaceLab (test). No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Carbon on this server. The server has VAC on, Valve's anti-cheat.

A.12What is the map for PopulaceLab (test)?

The game generates PopulaceLab (test)'s procedural map at size 4,500, from seed 1530458240. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page. The map is named Custom Map.

Connection

A.13What steps are required to join PopulaceLab (test)?

Press F1 inside Rust to open the console and enter client.connect 24.8.85.119:28335. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp3,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. Survival on vanilla rules.
mp3Max players. It offers 3 slots.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.
Mods and access
^zModded. Modded listing: plugins or settings modify the game.
^yCarbon. The plugin framework is Carbon.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.