Offline 133.88.107.138:28015 checked 4d ago
RustServer_4739
Connect
srv = rust.server("133.88.107.138: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 3 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 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 09:23 UTC4d ago | 2 | NaN | running | 0 |
| 1 | Sun 4 Oct, 11:57 UTC25d ago | 0 | NaN | 20.9 days | 0 |
| 2 | Sat 3 Oct, 05:12 UTC26d ago | 0 | NaN | 1.3 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
1000 · seed 8451
- map
- Procedural Map
- size
- 1000
- seed
- 8451
Server
srv.info()- address
- 133.88.107.138:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 09:23 UTC
- hostname
- –
- first seen
- 3 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 · 149 on average | 173/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 81/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 20/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 24/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 260/700 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does RustServer_4739 rank?
Player hours over seven days put RustServer_4739 at #12,860, in the top 58% of the ranked set.
What population does RustServer_4739 carry?
RustServer_4739 returns no live count at this refresh, having last been seen 4 days 1 hours ago. Over the last seven days it averaged 0 players and peaked at 2.
Server facts
What Rust version does RustServer_4739 run?
Rust network protocol 2635 and build 166652 on Linux is what RustServer_4739 runs. The protocol has to match before you can join, and Steam does the updating.
Is RustServer_4739 up, and what does its uptime show?
The latest sample has RustServer_4739 offline, with a last sighting 4 days 1 hours ago. Uptime of 4% across the last 7 full days: 6 hours of 168. Rust Data logged it first on 3 October 2026.
Which location does RustServer_4739 run from?
No region is published by RustServer_4739. Rust Data does not look up where the machine stands; it shows where a server says it is. 133.88.107.138:28015 is its address.
Settings and map
Which rules apply on RustServer_4739, and what settings?
You will not find a gather rate in the string RustServer_4739. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has RustServer_4739 loaded?
The game generates the map on RustServer_4739: procedural, size 1,000, seed 8451. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
On what schedule does RustServer_4739 wipe?
Irregular wipe times on RustServer_4739 leave no next wipe to forecast. 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 4 days 3 hours ago, and that is the one in play.
What is wipe day on RustServer_4739 like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which Rust Data filters and lists contain RustServer_4739?
On Rust Data, RustServer_4739 appears in these lists: 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; Last wipe: In the last week.
How should you read the server tags on RustServer_4739?
Read by the game's server browser, the tags RustServer_4739 publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to RustServer_4739?
In Rust, F1 opens the console: type client.connect 133.88.107.138:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.