Online 108.136.160.56:28015 checked 12m ago
[SEA] RustCamp | 3x | Biweekly
Connect
srv = rust.server("108.136.160.56: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 29 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 · from its schedule tag
srv.wipe_schedule()
Next wipe Sunday 1 November, 22:13 UTC, in 3d 22h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 22h | Sun 1 Nov, 22:13 UTC | wipe |
| 1 | 7d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 17d 22h | Sun 15 Nov, 22:13 UTC | wipe |
| 3 | 31d 22h | Sun 29 Nov, 22:13 UTC | wipe |
| 4 | 35d 19h | 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 | Sun 4 Oct, 22:13 UTC24d 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
3500 · seed 12345
- map
- Procedural Map
- size
- 3500
- seed
- 12345
Server
srv.info()- address
- 108.136.160.56:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 4 Oct 2026, 22:13 UTC
- hostname
- –
- first seen
- 29 Sep 2026
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 | [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 81 on average | 34/115 |
| 1 | Japan Tokyo - Limited Raid Hours |3x|PvP|JP | EA · groups of 8+ · 3x · weekly · 40 on average | 5/300 |
| 2 | [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 25 on average | 0/150 |
| 3 | JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP | EA · groups of 32+ · 5x · biweekly · 14 on average | 4/120 |
| 4 | [TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 | EA · groups of 12+ · 5x · biweekly · 14 on average | 1/200 |
| 5 | Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long | EA · groups of 100+ · 3x · monthly · 7 on average | 4/120 |
Quick answers
From the figures on this page.
Population
What position does [SEA] RustCamp | 3x | Biweekly take in the server rankings?
Player hours over seven days put [SEA] RustCamp | 3x | Biweekly at #15,344, in the top 69% of the ranked set.
How full does [SEA] RustCamp | 3x | Biweekly run?
Current row: 0 players on [SEA] RustCamp | 3x | Biweekly, against 50 slots. Over the last seven days it averaged 0 players.
About the server
What does performance look like on [SEA] RustCamp | 3x | Biweekly?
Averaged over 48 hours: 218 server fps, never under 183. Entity numbers reached 69,800, and that includes buildings, deployables and the rest. The memory field tops out at 2,363 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on [SEA] RustCamp | 3x | Biweekly?
Rust network protocol 2635 and build 168909 on Linux is what [SEA] RustCamp | 3x | Biweekly runs. Steam updates your game for you, but the protocol must match to join.
How reliable is [SEA] RustCamp | 3x | Biweekly, and is it online now?
The current sample puts [SEA] RustCamp | 3x | Biweekly online. The uptime it reports puts the last restart about 2 days 4 hours ago. 111 of 168 hours up over the last 7 full days, or 66%. Its earliest recorded date in Rust Data is 29 September 2026.
In which location is [SEA] RustCamp | 3x | Biweekly hosted?
No region tag is published by [SEA] RustCamp | 3x | Biweekly, though its name points to Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 108.136.160.56:28015 is its address.
Rules, settings, map
Which settings and rules does [SEA] RustCamp | 3x | Biweekly run?
The name carries the figure: [SEA] RustCamp | 3x | Biweekly runs 3x gather. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has [SEA] RustCamp | 3x | Biweekly loaded?
The game generates the map on [SEA] RustCamp | 3x | Biweekly: procedural, size 3,500, seed 12345. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does [SEA] RustCamp | 3x | Biweekly wipe, and on what schedule?
The tag sets the prediction: [SEA] RustCamp | 3x | Biweekly has too few wipes on record to confirm its schedule. On Sunday 1 November at 22:13 UTC the next wipe is due. This world was created 24 days 1 hours ago. Its tags carry a wipe schedule of every two weeks.
On [SEA] RustCamp | 3x | Biweekly, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold [SEA] RustCamp | 3x | Biweekly, and which filters?
These Rust Data lists include [SEA] RustCamp | 3x | Biweekly: Modded Rust servers and 3x Rust servers, filtered live. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 3x.
Which meanings do the tags on [SEA] RustCamp | 3x | Biweekly hold?
These tags are published by [SEA] RustCamp | 3x | Biweekly and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks between wipes; ^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.
How to join
How can I connect to [SEA] RustCamp | 3x | Biweekly?
Enter client.connect 108.136.160.56:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.
