Online 78.29.14.210:28115 checked 6m ago
Solo|x2|Kits|TP|Vip[Viking]
Connect
srv = rust.server("78.29.14.210:28116")
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 bestTop 13% of all ranked servers, and #125 of the solo servers (top 56%). Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()Next wipe Monday 2 November, 00:13 UTC, in 3d 12h. # Every Monday at 00:13 UTC · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 12h | Mon 2 Nov, 00:13 UTC | wipe |
| 1 | 7d 6h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 10d 12h | Mon 9 Nov, 00:13 UTC | wipe |
| 3 | 17d 12h | Mon 16 Nov, 00:13 UTC | wipe |
| 4 | 24d 12h | Mon 23 Nov, 00:13 UTC | wipe |
| 5 | 31d 12h | Mon 30 Nov, 00:13 UTC | wipe |
| 6 | 35d 6h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 38d 12h | Mon 7 Dec, 00:13 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 38 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 00:13 UTC3d ago | 4 | NaN | running | 0 |
| 1 | Mon 19 Oct, 00:12 UTC10d ago | 4 | held half | 7 days | 0 |
| 2 | Mon 12 Oct, 00:04 UTC17d ago | 4 | held half | 7 days | 0 |
| 3 | Mon 5 Oct, 00:13 UTC24d ago | 5 | held half | 7 days | 0 |
| 4 | Thu 1 Oct, 23:56 UTC FW27d ago | 4 | held half | 3 days | 0 |
| 5 | Mon 28 Sep, 00:04 UTC31d ago | 6 | halved by day 2 | 4 days | 0 |
| 6 | Sun 20 Sep, 23:56 UTC38d ago | 4 | held half | 7 days | 0 |
| 7 | Mon 14 Sep, 00:07 UTC45d ago | 4 | held half | 7 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
4500 · seed 1607695022- map
- Procedural Map
- size
- 4500
- seed
- 1607695022
Server
srv.info()- address
- 78.29.14.210:28115
- region
- –
- max players
- 100
- group limit
- solo
- wipe schedule
- weekly
- last wipe
- 26 Oct 2026, 00:13 UTC
- hostname
- –
- first seen
- 13 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 | WARBANDITS.GG EU 2X SOLO ONLY|Loot+|X2 JUST WIPED | EU · solo · 2x · weekly · 64 on average | 41/200 |
| 1 | Blood Rust - Purple [solo, x2] | EU · solo · 2x · weekly · 54 on average | 49/200 |
| 2 | WARBANDITS.GG 2X SOLO ONLY|Loot+|X2 JUST WIPED | NA · solo · 2x · weekly · 47 on average | 18/200 |
| 3 | Magic Rust #16 — Modded 2x (Toлькo SOLO) | Pyccкий | EU · solo · 2x · weekly · 43 on average | 52/100 |
| 4 | EU Limitless 2x Solo Only | No BP Wipes|Noob Friendly|x2|Max 1 | EU · solo · 2x · weekly · 29 on average | 7/200 |
| 5 | Bestrust Solo ONLY 2x | JUST FULLWIPED 29.10 10/29 | EU · solo · 2x · weekly · 12 on average | 84/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Solo|x2|Kits|TP|Vip[Viking] rank?
Player hours over seven days put Solo|x2|Kits|TP|Vip[Viking] at #2,801, in the top 13% of the ranked set. Its position in the solo group is #125.
What population does Solo|x2|Kits|TP|Vip[Viking] carry?
Solo|x2|Kits|TP|Vip[Viking] reports 2 players at this refresh, with 100 slots configured. Over the last seven days it averaged 1 players and peaked at 7. Peak hour in the last 48 hours: 08:00 UTC, mean 4 players.
Server facts
How smoothly does Solo|x2|Kits|TP|Vip[Viking] run?
Averaged over 48 hours: 52 server fps, never under 10. Buildings, deployables and all else in the world took the count as high as 118,177 entities. Memory peaked at 4,361 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is Solo|x2|Kits|TP|Vip[Viking] on?
Rust network protocol 2635 and build 168909 on Linux is what Solo|x2|Kits|TP|Vip[Viking] runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Solo|x2|Kits|TP|Vip[Viking], and is it online now?
Solo|x2|Kits|TP|Vip[Viking] reports itself online at the current refresh. The uptime it reports puts the last restart about 10 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.
Where does Solo|x2|Kits|TP|Vip[Viking] sit?
For Solo|x2|Kits|TP|Vip[Viking], 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 78.29.14.210:28115.
Settings and map
Which rules apply on Solo|x2|Kits|TP|Vip[Viking], and what settings?
Gather sits at 2x, read from the server's own name: Solo|x2|Kits|TP|Vip[Viking]. Solo play only. Teams are not allowed. Game mode survival, with this note: gather, build, raid: the standard loop. 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 Solo|x2|Kits|TP|Vip[Viking] loaded?
Solo|x2|Kits|TP|Vip[Viking] runs a procedural map of size 4,500 with seed 1607695022, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does Solo|x2|Kits|TP|Vip[Viking] wipe, and how often?
every Monday at 00:13 UTC is how Solo|x2|Kits|TP|Vip[Viking] wipes. The schedule puts the next wipe on Monday 2 November at 00:13 UTC. This world was created 3 days 11 hours ago. Its tags carry a weekly wipe schedule.
What is wipe day on Solo|x2|Kits|TP|Vip[Viking] like?
The average peak over recent wipes is 4 players. The crowd on the latest wipe topped out 38 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 80% of the time. Otherwise the crowd fell below half by day 2.
Tags and filters
Which Rust Data filters and lists contain Solo|x2|Kits|TP|Vip[Viking]?
The Rust Data lists that Solo|x2|Kits|TP|Vip[Viking] fits are: Modded Rust servers, 2x Rust servers and Solo Rust servers, group limit 1. Under these filters on the server list, it is listed: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Which meanings do the tags on Solo|x2|Kits|TP|Vip[Viking] hold?
These tags are published by Solo|x2|Kits|TP|Vip[Viking] and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts1 (Group limit): The team cap is 1; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^w (Weekly): A wipe every week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into Solo|x2|Kits|TP|Vip[Viking]?
In Rust, F1 opens the console: type client.connect 78.29.14.210:28115. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at http://viking.gamestores.app/.