Offline 129.232.154.35:28065 checked 11h ago
RUREADY
Connect
srv = rust.server("129.232.154.35:28066")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 19:06 UTC2d ago | 1 | NaN | 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())Map
3000 · seed 6738
- map
- Procedural Map
- size
- 3000
- seed
- 6738
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 123/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 132/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 53/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 31/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does RUREADY rank?
Player hours over seven days put RUREADY at #8,535, in the top 38% of the ranked set.
How many players does RUREADY hold at once?
The current row shows RUREADY offline; the last response was 11 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 18:00 UTC is the busiest, at 1 players.
Server data
How smoothly does RUREADY run?
Server fps over the last 48 hours averages 86; the floor is 61. Entity numbers reached 50,068, and that includes buildings, deployables and the rest. The memory field tops out at 2,121 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is RUREADY on?
Rust network protocol 2635 and build 168909 on Windows is what RUREADY runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is RUREADY, and is it up?
RUREADY is offline at this refresh; the last response came 11 hours ago. Count back 25 hours from its reported uptime to get the last restart. Over the last 2 full days the hours up number 29 of 48, 60%. Rust Data logged it first on 25 October 2026.
Where does RUREADY sit?
There is no region published for RUREADY. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 129.232.154.35:28065 is its address.
Settings and map
Which settings and rules does RUREADY run?
You will not find a gather rate in the string RUREADY. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has RUREADY loaded?
RUREADY runs a procedural map of size 3,000 with seed 6738, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does RUREADY wipe, and how often?
The record for RUREADY holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 2 days 10 hours ago.
On RUREADY, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which Rust Data filters and lists contain RUREADY?
The Rust Data lists that RUREADY fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Which meanings do the tags on RUREADY hold?
The game's server browser reads these tags from RUREADY: gmvanilla (Game mode): Survival in vanilla form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into RUREADY?
The manual route: launch Rust, F1, then client.connect 129.232.154.35:28065. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.