Testing

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 45d ago · 144.130.111.115:28015

Abstract

We describe the public Rust server Testing, reached at 144.130.111.115:28015. It is offline at the last check, against a seven-day mean of 0¹. It last wiped 53d ago.

Keywordsmodded oxide

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²	–	score 0
Last wipe	53d ago	no schedule published
Next wipe³	–	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 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

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

No rank history yet.

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)	Peak	Crowd	Lasted	Before
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.

Address	`144.130.111.115:28015`
Region	–
Max players	10
Group limit	8, the default
Wipe schedule	–
Last wipe	5 Sep 2026, 17:12 UTC
Hostname	–
First seen	13 Sep 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 browse modded Rust servers [2] and predicted wipe schedule [3].

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

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 149 on average	151/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	131/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average	183/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average	79/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 88 on average	9/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	22/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does Testing have?

No region is published by Testing. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 144.130.111.115:28015.

A.2What is the online status and reliability of Testing?

At the present moment, Testing is offline; it was last seen 45 days 22 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.

A.3What version of Rust is run on Testing?

Testing is running Rust network protocol 2633 and build 163207 on the Windows operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4What schedule does Testing follow for wipes?

Too few wipes by Testing have been recorded to determine the pattern. 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 world currently in use was created 53 days 17 hours ago.

Population

A.5How would you characterise the player activity on Testing?

Testing is not online now; 45 days 22 hours have passed since it was last seen.

Tags and filters

A.6What is the meaning of the tags on Testing?

Tags from Testing, read by the game's server browser, are 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; v2633 (Protocol): Joining requires the same game version: protocol 2633; cs163207 (Build): Build 163207 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.7Where can Testing be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Testing fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.8Under what rules and settings does Testing operate?

The name of Testing states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.9What is the map for Testing?

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

How to join

A.10What is the process for joining Testing?

Press F1 inside Rust to open the console and enter client.connect 144.130.111.115: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 mp10,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z.

Table 5: 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.
`v2633`	Protocol. Joining requires the same game version: protocol 2633.
`cs163207`	Build. Build 163207 is the one running.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. No region code is set.
Mods and access
`^o`	Oxide. The plugin framework in use is Oxide (uMod).
`^z`	Modded. The game is altered by plugins or settings, so it is listed as Modded.

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. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.