local test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 8d ago · 176.60.64.192:28015

Abstract

We describe the public Rust server local test, reached at 176.60.64.192:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,325 of all servers, the top 70%. It last wiped 9d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/10	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,325	top 70%
Last wipe	9d ago	no schedule published
Next wipe³	–	too few wipes seen yet

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.

No hourly history yet.

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 memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

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.

4Rank

The server stands in the top 70% 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

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

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

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Usual gap	0.7 days	between real wipes
Wipe-day peak	0	players, last three wipes

Mon 19 OctSun 18 Oct

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)	Peak	Crowd	Lasted	Before
Mon 19 Oct, 11:349d ago	0	–	running	1
Sun 18 Oct, 18:279d ago	1	–	0.7 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

No map picture published

Figure 5: The map: Procedural Map.

Table 4: The server's published settings.

Address	`176.60.64.192:28015`
Region	–
Max players	10
Group limit	8, the default
Wipe schedule	–
Last wipe	19 Oct 2026, 11:34 UTC
Hostname	–
First seen	18 Oct 2026
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
Rusty Moose \|EU Mondays\|EU · groups of 12+ · weekly · 541 on average	646/700
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average	424/475
Rustoria.co - EU MainEU · groups of 16+ · weekly · 310 on average	37/250
Rusty Moose \|EU Main\|EU · groups of 12+ · weekly · 310 on average	51/250
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 270 on average	213/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 266 on average	116/150

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does local test have?

No region is published by local test. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 176.60.64.192:28015.

A.2What is the reliability of local test, and is it online?

local test is currently offline, with the last sighting 8 days 23 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. It was first observed on 18 October 2026 by Rust Statistics.

A.3What is the Rust version for local test?

local test is running Rust network protocol 2634 and build 167781 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4What schedule does local test follow for wipes?

There are not yet enough recorded wipes for local test to reveal its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 9 days.

A.5What happens on local test when wipe day arrives?

The average busiest point of recent wipes was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.6What is the rank of local test among Rust servers?

The seven-day player-hours ranking puts local test at #15,325, within the top 70% of ranked servers.

A.7What is the population level of local test?

The last recorded sighting of local test was 8 days 23 hours ago; it is offline now.

Tags, lists

A.8What is the meaning of the tags on local test?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset, which local test publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can local test be found among the Rust Statistics lists and filters?

The Rust Statistics lists that local test fits are: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.10Under what rules and settings does local test operate?

No gather rate appears in the name of local test. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means the standard mode, in which you gather, build and raid. Players may raid and fight one another. The server browser lists it under Community. VAC is active: that is Valve's anti-cheat.

A.11What map is in use on local test?

A procedural map, generated by the game, is what local test runs.

Connection

A.12How do you connect to local test?

Enter client.connect 176.60.64.192:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8.

Table 6: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Survival on standard Rust rules.
`mp10`	Max players. 10 slots are available.
`ts8`	Group limit. Teams are limited to 8, as the game defaults.
`v2634`	Protocol. Joining requires the same game version: protocol 2634.
`cs167781`	Build. The game build is 167781.
`ptrak`	Networking. RakNet is the network layer here, as it is by default in the game.
`$r?`	Region code. The region code is unset.

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]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
[3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.