Offline 156.146.35.179:28015 checked 10d ago
TamuSV
Connect
srv = rust.server("156.146.35.179: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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. # The force wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 156.146.35.179:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 06:38 UTC
- hostname
- –
- first seen
- 19 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 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 65/300 |
| 1 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No Killing | NA · groups of 8+ · monthly · 48 on average | 46/200 |
| 2 | [US] RustEZ Survival PvE | No Decay | No Raiding | No Killing | NA · groups of 8+ · monthly · 37 on average | 38/200 |
| 3 | Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | Jet | NA · no group limit · 1x · monthly · 37 on average | 93/125 |
| 4 | [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本 | EA · groups of 8+ · monthly · 34 on average | 25/100 |
| 5 | Zombie Land PVE Monthly | Raids | Skills | Custom Maps | NA · groups of 14+ · monthly · 33 on average | 37/100 |
Quick answers
From the figures on this page.
Population
How does TamuSV compare in the rankings?
Rank #15,311 on seven-day player hours for TamuSV, within the top 70% of all ranked servers.
How full does TamuSV run?
TamuSV returns no live count at this refresh, having last been seen 10 days 12 hours ago.
Server data
Which Rust version is TamuSV on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by TamuSV. Steam updates your game for you, but the protocol must match to join.
How reliable is TamuSV, and is it up?
Offline now for TamuSV, last seen 10 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 19 October 2026.
In which location is TamuSV hosted?
For TamuSV, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 156.146.35.179:28015.
Rules, settings, map
What rules and settings are recorded for TamuSV?
You will not find a gather rate in the string TamuSV. No custom cap; the default of 8 players per group stands. pve is the game mode here, and player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on TamuSV?
The game generates its map: procedural, on TamuSV.
Wipes and dates
When does TamuSV wipe, and how often?
The next wipe for TamuSV is an estimate, drawn from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 27 days 16 hours ago. Its tags carry a monthly wipe schedule.
Lists and tags
Where does TamuSV appear among Rust Data lists and filters?
These Rust Data lists include TamuSV: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on TamuSV?
These tags are published by TamuSV and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into TamuSV?
Enter client.connect 156.146.35.179:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.