Offline 89.134.26.234:28015 checked 4d ago
Test Server 2026
Connect
srv = rust.server("89.134.26.234:28017")
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. 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 50% 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 | Fri 23 Oct, 09:10 UTC5d ago | 1 | NaN | running | 1 |
| 1 | Mon 12 Oct, 20:18 UTC16d ago | 1 | held half | 10.5 days | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 89.134.26.234:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 09:10 UTC
- hostname
- –
- first seen
- 12 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 · 157 on average | 98/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 101/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 87/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 29/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 21/1000 |
Quick answers
From the figures on this page.
Population
How does Test Server 2026 compare in the rankings?
Player hours over seven days put Test Server 2026 at #11,095, in the top 50% of the ranked set.
How many players does Test Server 2026 hold at once?
Test Server 2026 returns no live count at this refresh, having last been seen 4 days 12 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
About the server
Which Rust version is Test Server 2026 on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Test Server 2026. Joining needs the same protocol on your game; Steam handles the update.
Is Test Server 2026 up, and what does its uptime show?
Test Server 2026 is offline at this refresh; the last response came 4 days 12 hours ago. 26 of 168 hours up over the last 7 full days, or 15%. Its earliest recorded date in Rust Data is 12 October 2026.
In which location is Test Server 2026 hosted?
No region is published by Test Server 2026. Rust Data does not look up where the machine stands; it shows where a server says it is. 89.134.26.234:28015 is its address.
Settings and map
Which settings and rules does Test Server 2026 run?
No gather rate appears in the name: Test Server 2026. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on Test Server 2026?
A procedural map runs on Test Server 2026, generated by the game.
Wipe data
When does Test Server 2026 wipe, and on what schedule?
A rhythm cannot be read from the wipes of Test Server 2026 on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 5 days 12 hours ago, and that is the one in play.
On Test Server 2026, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Which Rust Data filters and lists contain Test Server 2026?
On Rust Data, Test Server 2026 appears in these lists: Modded Rust servers. It appears under these 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.
How should you read the server tags on Test Server 2026?
The game's server browser reads these tags from Test Server 2026: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Test Server 2026?
The manual route: launch Rust, F1, then client.connect 89.134.26.234:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.