Online EU 135.125.188.235:5003 checked 11m ago
RustEu Solo/Duo/Trio|BiWeekly|Raidtimer
Connect
srv = rust.server("135.125.188.235:5005")
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 17 Sep. 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 68% of all ranked servers, top 87% in EU, and #514 of the trio servers (top 82%). Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 21h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 10d 0h | Sun 8 Nov, 22:28 UTC | wipe |
| 2 | 24d 0h | Sun 22 Nov, 22:28 UTC | wipe |
| 3 | 34d 21h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 38d 0h | Sun 6 Dec, 22:28 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 11 Oct, 22:28 UTC17d ago | 0 | 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())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rustafied.com - EU Trio | EU · trio · biweekly · 84 on average | 506/600 |
| 1 | CZ/SK #Začátečníci# | EU · trio · biweekly · 2 on average | 2/50 |
| 2 | RustSpain.com | EU Trio Mondays | EU · trio · weekly · 68 on average | 70/200 |
| 3 | 404 RUST SOLO/DUO/TRIO | ВТ | ДЛЯ НОВИЧКОВ 27.10 | EU · trio · monthly · 17 on average | 13/550 |
| 4 | 404 RUST SOLO/DUO/TRIO | СБ | ДЛЯ НОВИЧКОВ 24.10 | EU · trio · monthly · 15 on average | 2/550 |
| 5 | 404 RUST SOLO/DUO/TRIO | ПН | ДЛЯ НОВИЧКОВ 26.10 | EU · trio · monthly · 12 on average | 4/550 |
Quick answers
From the figures on this page.
Player counts
How does RustEu Solo/Duo/Trio|BiWeekly|Raidtimer compare in the rankings?
Player hours over the last seven days: #15,268 for RustEu Solo/Duo/Trio|BiWeekly|Raidtimer, #2,528 in Europe, within the top 68% of the ranked set. Its position in the trio group is #514.
How many players does RustEu Solo/Duo/Trio|BiWeekly|Raidtimer hold at once?
Current row: 0 players on RustEu Solo/Duo/Trio|BiWeekly|Raidtimer, against 120 slots. Over the last seven days it averaged 0 players.
About the server
What does performance look like on RustEu Solo/Duo/Trio|BiWeekly|Raidtimer?
Server fps over the last 48 hours averages 211; the floor is 179. Entity numbers reached 28,282, and that includes buildings, deployables and the rest. Memory peaked at 4,086 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does RustEu Solo/Duo/Trio|BiWeekly|Raidtimer run?
The build is Rust network protocol 2634 and build 167398 on Linux, run by RustEu Solo/Duo/Trio|BiWeekly|Raidtimer. The protocol has to match before you can join, and Steam does the updating.
Is RustEu Solo/Duo/Trio|BiWeekly|Raidtimer up, and what does its uptime show?
RustEu Solo/Duo/Trio|BiWeekly|Raidtimer reports itself online at the current refresh. The uptime it reports puts the last restart about 17 days 21 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does RustEu Solo/Duo/Trio|BiWeekly|Raidtimer sit?
With its EU tag, RustEu Solo/Duo/Trio|BiWeekly|Raidtimer lists itself in Europe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 135.125.188.235:5003 is its address.
Rules, settings, map
What rules and settings are recorded for RustEu Solo/Duo/Trio|BiWeekly|Raidtimer?
The name RustEu Solo/Duo/Trio|BiWeekly|Raidtimer carries no gather rate. trio sets the cap: 3 players per group. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has RustEu Solo/Duo/Trio|BiWeekly|Raidtimer selected?
The game generates the map on RustEu Solo/Duo/Trio|BiWeekly|Raidtimer: procedural, size 2,350, seed 1337. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.
Wipe data
When does RustEu Solo/Duo/Trio|BiWeekly|Raidtimer wipe, and on what schedule?
The prediction follows the tag, because RustEu Solo/Duo/Trio|BiWeekly|Raidtimer's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 17 days 23 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
On RustEu Solo/Duo/Trio|BiWeekly|Raidtimer, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which lists on Rust Data hold RustEu Solo/Duo/Trio|BiWeekly|Raidtimer, and which filters?
The Rust Data lists that RustEu Solo/Duo/Trio|BiWeekly|Raidtimer fits are: EU Rust servers, Modded Rust servers and Trio Rust servers. It appears under these filters on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Every two weeks.
How should you read the server tags on RustEu Solo/Duo/Trio|BiWeekly|Raidtimer?
Read by the game's server browser, the tags RustEu Solo/Duo/Trio|BiWeekly|Raidtimer publishes are: gmrust (Game mode): Rust survival in its standard form; mp120 (Max players): The server lists 120 slots; ts3 (Group limit): The team cap is 3; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): The cycle is fourteen days; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; EU (Europe): The server browser files it under Europe. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to RustEu Solo/Duo/Trio|BiWeekly|Raidtimer?
Enter client.connect 135.125.188.235:5003 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://guavahost.com/ is the website recorded for it.
