Rust Test
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 12m ago · 217.77.1.118:25565
Abstract
We describe the public Rust server Rust Test, reached at 217.77.1.118:25565. At the last check it held 0 of 100 places, against a seven-day mean of 01. It ranks #15,268 of all servers, the top 68%. It last wiped 26d 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 68% 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: 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.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 0 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Sat 3 Oct, 10:2026d ago | 0 | – | running | 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
| Address | 217.77.1.118:25565 |
|---|---|
| Region | – |
| Max players | 100 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 3 Oct 2026, 10:20 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 3000 |
| Seed | 1321362921 |
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 population table [2] and predicted wipe schedule [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 150 on average | 71/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average | 126/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average | 118/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average | 40/700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average | 127/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average | 348/350 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1How well does Rust Test run?
The server fps averaged 45 over the last 48 hours, never dropping below 7. The highest number of entities it carried was 49,684, comprising buildings, deployables and all other objects. Its highest memory usage was 1,799 MB. When fps is low and entity count climbs, players feel lag.
A.2In which location is Rust Test based?
A region is not published by Rust Test. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 217.77.1.118:25565 is its address.
A.3What is the reliability of Rust Test, and is it online?
Rust Test is online at this time. The uptime it reports indicates a restart about 9 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.
A.4What is the Rust version for Rust Test?
Rust Test is running Rust network protocol 2635 and build 168909 on the Linux operating system. To join, your game must use the same protocol; Steam handles the update for you.
Wipe timing
A.5What schedule does Rust Test follow for wipes?
The record of Rust Test's wipes is not yet sufficient to establish its rhythm. 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 current world has been running for 26 days 10 hours.
A.6What happens on Rust Test when wipe day arrives?
The average busiest point of recent wipes was 0 players. The peak on the latest wipe came 0 hours after it began.
Population
A.7What is the rank of Rust Test among Rust servers?
The seven-day player-hours ranking puts Rust Test at #15,268, within the top 68% of ranked servers.
A.8What is the population level of Rust Test?
The current population of Rust Test is 0, drawn from 100 slots. Averaged across the last seven days, the population is 0 players.
Tags, lists
A.9How should the tags on Rust Test be interpreted?
gmrust (Game mode): This is survival as standard Rust plays; mp100 (Max players): The slot count is 100; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags Rust Test publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.10Where can Rust Test be found among the Rust Statistics lists and filters?
These Rust Statistics lists include Rust Test: 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.11What are the settings and rules that govern Rust Test?
The name of Rust Test states no gather rate. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is gather, build and raid: the standard game. Combat and raiding against other players are allowed. It appears under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running. The server has VAC off, Valve's anti-cheat.
A.12What map is in use on Rust Test?
The game generates Rust Test's procedural map at size 3,000, from seed 1321362921. Because size and seed determine the map, RustMaps can show it, linked from this page.
Connection
A.13What steps are required to join Rust Test?
Enter client.connect 217.77.1.118:25565 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 mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. This is survival as standard Rust plays. |
mp100 | Max players. The slot count is 100. |
ts8 | Group limit. The team cap is 8, which is the game default. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. The region code is unset. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
^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. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.