Rust StatisticsWorking papers on every public Rust server · 35,842 players now

TestServer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 38d ago · 112.70.223.138:28015

Abstract

We describe the public Rust server TestServer, reached at 112.70.223.138:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,308 of all servers. It last wiped 55d 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.
MeasureValueNote
Players now1/1100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,308no region published
Last wipe55d agono schedule published
Next wipe3–no wipe 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 memory4. 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

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
No wipe seen yet.

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 4: The map: Procedural Map.
Table 3: The server's published settings.
Address112.70.223.138:28015
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe3 Sep 2026, 23:04 UTC
Hostname–
First seen20 Sep 2026
MapProcedural 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 servers wiping soon [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 555 on average164/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average96/200
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average15/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 286 on average17/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average12/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average17/200

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does TestServer have?

A region is not published by TestServer. Rust Statistics does not look up the machine's location; it shows where the server says it is. 112.70.223.138:28015 is its address.

A.2How reliable is TestServer, and is it currently online?

TestServer is currently offline, with the last sighting 38 days 22 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. It was first observed on 20 September 2026 by Rust Statistics.

A.3What is the Rust version for TestServer?

The version of Rust on TestServer is network protocol 2633 and build 162929, and the operating system is Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.4On what cycle does TestServer wipe?

The record of TestServer's wipes is not yet sufficient to establish 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 55 days 4 hours.

Player count

A.5How does TestServer compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts TestServer at #13,308, within the top – of ranked servers.

A.6What is the population level of TestServer?

The last recorded sighting of TestServer was 38 days 22 hours ago; it is offline now.

Tags and filters

A.7What do the tags associated with TestServer signify?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs162929 (Build): Build 162929 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset, which TestServer publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.8Where can TestServer be found among the Rust Statistics lists and filters?

The Rust Statistics lists that TestServer fits are: Rust community servers, measured. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

A.9Which settings and rules are in force on TestServer?

Its name carries no gather rate for TestServer. The group cap is 8 players, which is the default in the game. The mode is survival, which means the standard mode, in which you gather, build and raid. Players may raid and fight one another. It is a community server, as the browser's Community listing shows. The server has VAC on, Valve's anti-cheat.

A.10On which map does TestServer take place?

The game generates the map on TestServer; that format is procedural.

Connection

A.11How do you connect to TestServer?

Press F1 inside Rust to open the console and enter client.connect 112.70.223.138:28015. 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 mp1,ptrak,$r?,v2633,gmrust,cs162929,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp1Max players. 1 slots are available.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs162929Build. Build 162929 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.