Offline 51.38.13.133:26025 checked 23d ago
RAID1
Connect
srv = rust.server("51.38.13.133:26027")
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 5 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 best
Top 71% 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 14, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 5 Oct, 17:15 UTC24d ago | 14 | NaN | running | 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. 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
2500 · seed 3486489- map
- Custom Map
- size
- 2500
- seed
- 3486489
Server
srv.info()- address
- 51.38.13.133:26025
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 17:15 UTC
- hostname
- –
- first seen
- 5 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 · 150 on average | 61/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 107/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 36/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 114/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does RAID1 rank?
Player hours over seven days put RAID1 at #15,980, in the top 71% of the ranked set.
What population does RAID1 carry?
Offline now for RAID1, with the last sample 23 days 10 hours ago.
Server facts
What Rust version does RAID1 run?
The build is Rust network protocol 2634 and build 166652 on Windows, run by RAID1. Steam updates your game for you, but the protocol must match to join.
How reliable is RAID1, and is it up?
Offline now for RAID1, last seen 23 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 5 October 2026.
In which location is RAID1 hosted?
For RAID1, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 51.38.13.133:26025.
Map and rules
Which settings and rules does RAID1 run?
No gather rate appears in the name: RAID1. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has RAID1 selected?
The game generates the map on RAID1: procedural, size 2,500, seed 3486489. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.
Wipe schedule
On what schedule does RAID1 wipe?
A rhythm cannot be read from the wipes of RAID1 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. The world it runs now was generated 24 days 4 hours ago.
What is wipe day on RAID1 like?
Across recent wipes the busiest point averaged 14 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which Rust Data filters and lists contain RAID1?
These Rust Data lists include RAID1: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on RAID1?
These tags are published by RAID1 and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join RAID1?
In Rust, F1 opens the console: type client.connect 51.38.13.133:26025. Launch Rust on this page does the same by opening the game through Steam and connecting.
