Online 69.142.98.34:28215 checked 12m ago
MICRO_SKIN_PREVIEW
Connect
srv = rust.server("69.142.98.34:28216")
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 32% 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 7h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 7h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 7h | 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 2, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:30 UTC FW27d ago | 2 | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 69.142.98.34:28215
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:30 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 154/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does MICRO_SKIN_PREVIEW rank?
Player hours over seven days put MICRO_SKIN_PREVIEW at #7,221, in the top 32% of the ranked set.
How many players does MICRO_SKIN_PREVIEW hold at once?
MICRO_SKIN_PREVIEW reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 21:00 UTC is the busiest, at 1 players.
Server data
What is the Rust version on MICRO_SKIN_PREVIEW?
Rust network protocol 2635 and build 168909 on Windows is what MICRO_SKIN_PREVIEW runs. The protocol has to match before you can join, and Steam does the updating.
Is MICRO_SKIN_PREVIEW up, and what does its uptime show?
The current sample puts MICRO_SKIN_PREVIEW online. 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 MICRO_SKIN_PREVIEW run from?
No region is published by MICRO_SKIN_PREVIEW. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 69.142.98.34:28215.
Settings and map
What rules and settings are recorded for MICRO_SKIN_PREVIEW?
You will not find a gather rate in the string MICRO_SKIN_PREVIEW. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on MICRO_SKIN_PREVIEW?
MICRO_SKIN_PREVIEW runs a procedural map, which the game generates.
Wipes and dates
On what schedule does MICRO_SKIN_PREVIEW wipe?
The only wipe MICRO_SKIN_PREVIEW takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 27 days 16 hours ago.
What is wipe day on MICRO_SKIN_PREVIEW like?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 2 hours in.
Tags, lists
Where does MICRO_SKIN_PREVIEW appear among Rust Data lists and filters?
The Rust Data lists that MICRO_SKIN_PREVIEW fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on MICRO_SKIN_PREVIEW hold?
Read by the game's server browser, the tags MICRO_SKIN_PREVIEW publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join MICRO_SKIN_PREVIEW?
In Rust, F1 opens the console: type client.connect 69.142.98.34:28215. Launch Rust on this page does the same by opening the game through Steam and connecting.