TestServer
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 17d ago · 90.204.149.14:28015
Abstract
We describe the public Rust server TestServer, reached at 90.204.149.14:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,631 of all servers, the top 62%. It last wiped 17d ago.
Keywordsmodded oxide
1Summary statistics
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.
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).
4Rank
The server stands in the top 62% 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.
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.
| Measure | Value | Note |
|---|---|---|
| Usual gap | 2.1 days | between real wipes |
| On rhythm | 50% | of its recent wipes |
| Wipe-day peak | 1 | players, last three wipes |
| Crowd held | 100% | of its cycles kept half the crowd |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Sat 10 Oct, 16:1917d ago | 1 | – | running | 1 |
| Thu 8 Oct, 09:1720d ago | 1 | held half | 2.3 d | 0 |
| Tue 6 Oct, 10:4721d ago | 1 | – | 1.9 d | 1 |
| Sat 3 Oct, 10:3224d ago | 1 | held half | 3 d | 1 |
| Fri 2 Oct, 13:0725d ago | 1 | – | 0.9 d | 1 |
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
| Address | 90.204.149.14:28015 |
|---|---|
| Region | – |
| Max players | 10 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 10 Oct 2026, 16:19 UTC |
| Hostname | – |
| First seen | 1 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 browse modded Rust servers [2] and next Rust wipe times [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 155 on average | 158/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 127 on average | 130/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average | 184/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average | 109/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average | 7/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average | 44/1000 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1What location does TestServer have?
There is no region published for TestServer. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 90.204.149.14:28015 is its address.
A.2What is the online status and reliability of TestServer?
At the present moment, TestServer is offline; it was last seen 17 days 17 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. The first record of it by Rust Statistics dates to 1 October 2026.
A.3What version of Rust is run on TestServer?
TestServer is running Rust network protocol 2634 and build 167398 on the Windows operating system. To join, your game must use the same protocol; Steam handles the update for you.
Wipe schedule
A.4When are wipes carried out on TestServer?
No next wipe can be predicted for TestServer since its wipes occur at irregular intervals. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 17 days 17 hours have passed since the current world was generated.
A.5What happens on TestServer when wipe day arrives?
Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 0 hours after the latest wipe. Half the peak was sustained until the next wipe in 100% of recent wipes.
Player count
A.6How does TestServer compare with other Rust servers in the rankings?
Ranked by player hours across seven days, TestServer holds #13,631, in the top 62% of all ranked servers.
A.7At what level does TestServer operate in terms of players?
TestServer is not online now; 17 days 17 hours have passed since it was last seen.
Tags, lists
A.8What is the meaning of the tags on TestServer?
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; cs167398 (Build): Build 167398 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags TestServer publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.
A.9Where can TestServer be found among the Rust Statistics lists and filters?
These Rust Statistics lists include TestServer: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules, settings, map
A.10What are the settings and rules that govern TestServer?
Its name carries no gather rate for TestServer. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.
A.11What map is in use on TestServer?
On TestServer the terrain is procedural, built by the game itself.
Connection
A.12How do you connect to TestServer?
Enter client.connect 90.204.149.14: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,cs167398,ts8,^o^z.
| 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. |
cs167398 | Build. Build 167398 is the one running. |
ptrak | Networking. RakNet is the network layer here, as it is by default in the game. |
$r? | Region code. A region code has not been set. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
^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. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.