Online 135.148.34.204:28015 checked 12m ago
LinuxGSM
Connect
srv = rust.server("135.148.34.204: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, 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 9h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 9h | Thu 3 Dec, 19:00 UTC | FW force 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 | Thu 1 Oct, 18:06 UTC FW27d 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())
Map
3000 · seed 1897125331
- map
- Procedural Map
- size
- 3000
- seed
- 1897125331
Server
srv.info()- address
- 135.148.34.204:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:06 UTC
- hostname
- –
- first seen
- 13 Sep 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 522 on average | 355/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 327/325 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 33/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 34/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 55/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 246 on average | 168/200 |
Quick answers
From the figures on this page.
Player counts
How does LinuxGSM compare in the rankings?
Over the last seven days LinuxGSM sits at #15,335 on player hours, in the top 69% of ranked servers.
How many players does LinuxGSM hold at once?
LinuxGSM reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players.
About the server
How well does LinuxGSM perform?
Server fps over the last 48 hours averages 97; the floor is 40. Entity numbers reached 50,496, and that includes buildings, deployables and the rest. The memory field tops out at 2,138 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is LinuxGSM on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by LinuxGSM. The protocol has to match before you can join, and Steam does the updating.
How reliable is LinuxGSM, and is it online now?
LinuxGSM reports itself online at the current refresh. A restart about 3 days 12 hours ago is what its reported uptime implies. 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.
Which location does LinuxGSM run from?
No region is published by LinuxGSM. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 135.148.34.204:28015 is its address.
Settings and map
What rules and settings are recorded for LinuxGSM?
You will not find a gather rate in the string LinuxGSM. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Which map has LinuxGSM loaded?
Size 3,000, seed 1897125331: the procedural map on LinuxGSM, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
On what schedule does LinuxGSM wipe?
A single wipe each month, the force wipe, is all LinuxGSM does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 27 days 15 hours ago.
What is wipe day on LinuxGSM like?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does LinuxGSM appear among Rust Data lists and filters?
These Rust Data lists include LinuxGSM: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on LinuxGSM hold?
These tags are published by LinuxGSM and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to LinuxGSM?
Enter client.connect 135.148.34.204:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.
