RUREADY

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 1d ago · 129.232.154.35:28065

Abstract

We describe the public Rust server RUREADY, reached at 129.232.154.35:28065. It is offline at the last check, against a seven-day mean of 0 and a peak of 1¹. It ranks #8,494 of all servers, the top 38%. It last wiped 3d 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	1/10	10% full
In the queue	0	no queue
Seven-day mean	0	peak 1, 48 h peak 1
Rank²	#8,494	top 38%
Last wipe	3d ago	no schedule published
Next wipe³	–	too few wipes 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.

AveragePeak

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

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, measured since 25 Oct.

4Rank

The server stands in the top 38% 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: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Wipe-day peak	1	players, last three wipes

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Sun 25 Oct, 19:063d ago	1	–	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

Map of RUREADY — Figure 5: The map: Procedural Map, size 3000, seed 6738. Open on RustMaps.

Table 4: The server's published settings.

Address	`129.232.154.35:28065`
Region	–
Max players	10
Group limit	8, the default
Wipe schedule	–
Last wipe	25 Oct 2026, 20:54 UTC
Hostname	–
First seen	25 Oct 2026
Map	Procedural Map
Size	3000
Seed	6738

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 next Rust wipe times [3].

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

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

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does RUREADY perform well?

Over the past 48 hours, it ran at an average of 84 server fps, with a low of 61. Its entity count reached a maximum of 50,068, including buildings, deployables and all other world objects. Memory use peaked at 2,121 MB. When fps is low and entity count climbs, players feel lag.

A.2What location does RUREADY have?

No region is published by RUREADY. Rust Statistics does not look up the machine's location; it shows where the server says it is. 129.232.154.35:28065 is its address.

A.3What is the online status and reliability of RUREADY?

Right now, RUREADY is offline, and the last time it was seen was 27 hours ago. The uptime it reports indicates a restart about 25 hours ago. The server was up 60% of the time over the last 2 full days, 29 of 48 hours. The first record of it by Rust Statistics dates to 25 October 2026.

A.4What version of Rust is run on RUREADY?

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

Wipe schedule

A.5What schedule does RUREADY follow for wipes?

Too few wipes by RUREADY 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. The world currently in use was created 3 days 2 hours ago.

A.6How would you describe wipe day on RUREADY?

Across its recent wipes, the average peak population was 1 players. The peak on the latest wipe came 0 hours after it began.

Population

A.7How does RUREADY compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts RUREADY at #8,494, within the top 38% of ranked servers.

A.8What is the population level of RUREADY?

At this moment RUREADY is offline, having last been seen 27 hours ago. The peak over seven days is 1, against an average of 0. The busiest hour of the last 48 is 20:00 UTC, averaging 0 players.

Tags and filters

A.9How should the tags on RUREADY be interpreted?

gmvanilla (Game mode): Survival on vanilla rules; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; 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): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags RUREADY 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.10Where can RUREADY be found among the Rust Statistics lists and filters?

These Rust Statistics lists include RUREADY: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Settings and map

A.11Under what rules and settings does RUREADY operate?

Its name carries no gather rate for RUREADY. At 8 players, the group limit equals the game's default. The mode is survival, which means gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.12What map is in use on RUREADY?

The game generates RUREADY's procedural map at size 3,000, from seed 6738. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.13How do you connect to RUREADY?

Enter client.connect 129.232.154.35:28065 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?,v2635,gmvanilla,cs168909,ts8,^o^z.

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

Tag	Meaning
Game
`gmvanilla`	Game mode. Survival on vanilla rules.
`mp10`	Max players. The slot count is 10.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2635`	Protocol. The game protocol is 2635; your client must match it to join.
`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. 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 population table. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.