TestServ12

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 28d ago · 89.125.214.42:28015

Abstract

We describe the public Rust server TestServ12, reached at 89.125.214.42:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #16,810 of all servers, the top 70%. It last wiped 28d 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/50	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#16,810	top 70%
Last wipe	28d 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

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

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	`89.125.214.42:28015`
Region	–
Max players	50
Group limit	8, the default
Wipe schedule	–
Last wipe	30 Sep 2026, 13:39 UTC
Hostname	–
First seen	30 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 modded Rust servers listed live [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 · 150 on average	74/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	128/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average	112/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average	40/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 88 on average	4/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	12/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of TestServ12?

There is no region published for TestServ12. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 89.125.214.42:28015.

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

TestServ12 is currently offline, with the last sighting 28 days 17 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 30 September 2026 by Rust Statistics.

A.3What is the Rust version for TestServ12?

Rust network protocol 2633 and build 165217 is the version that TestServ12 runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4On what cycle does TestServ12 wipe?

Too few wipes by TestServ12 have been recorded to determine the pattern. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 28 days 17 hours have passed since the current world was generated.

Population

A.5What position does TestServ12 occupy in the ranking of Rust servers?

Ranked by player hours across seven days, TestServ12 holds #16,810, in the top 70% of all ranked servers.

A.6How would you characterise the player activity on TestServ12?

At this moment TestServ12 is offline, having last been seen 28 days 17 hours ago.

Tags, lists

A.7How should the tags on TestServ12 be interpreted?

gmvanilla (Game mode): Survival on vanilla rules; mp50 (Max players): It offers 50 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2633 (Protocol): Your game must run protocol 2633 to connect; cs165217 (Build): The game build is 165217; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags TestServ12 publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

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

These Rust Statistics lists include TestServ12: Modded Rust servers. 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.9Under what rules and settings does TestServ12 operate?

The name of TestServ12 states no gather rate. 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. 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. The server has VAC on, Valve's anti-cheat.

A.10What is the map for TestServ12?

On TestServ12 the terrain is procedural, built by the game itself.

How to join

A.11What is the process for joining TestServ12?

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

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

Tag	Meaning
Game
`gmvanilla`	Game mode. Survival on vanilla rules.
`mp50`	Max players. It offers 50 slots.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2633`	Protocol. Your game must run protocol 2633 to connect.
`cs165217`	Build. The game build is 165217.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. A region code has not been set.
Mods and access
`^o`	Oxide. Plugins are handled by Oxide (uMod).
`^z`	Modded. Modded listing: plugins or settings modify the game.

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