skin_test
Offline 95.79.77.56:28015 checked 1d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 173/500
- 126/100
- 186/225
- 129/700
- 15/200
- 56/1000
Quick answers
from the figures on this pageWipe timing
When does skin_test wipe?
The rhythm of skin_test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 24 days 2 hours ago.
Tag meanings
How should you read the tags on skin_test?
Tags published by skin_test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does skin_test appear in Rust Metrics lists and filters?
On Rust Metrics, skin_test sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
Where does skin_test sit in the rankings?
Ranking for skin_test: #15,411 on seven-day player hours, top 69% of all ranked servers.
What player count does skin_test carry?
Status for skin_test: offline. Last seen 41 hours ago. Check: player average. 0 over the last seven days.
Server
Which location does skin_test run from?
No region comes from skin_test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 95.79.77.56:28015.
What Rust version is skin_test on?
Reading: skin_test, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.
What is the uptime on skin_test, and is it online?
Reading: offline. skin_test last answered 41 hours ago. Uptime for the last 1 full day: 0 of 24 hours, or 0%. The first sighting on Rust Metrics was 26 October 2026.
Map and rules
How is skin_test configured, and what rules are in force?
No gather rate appears in the name: skin_test. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on skin_test?
The game generates a procedural map for skin_test.
Connection
What do you do to join skin_test?
Press F1 in Rust and enter client.connect 95.79.77.56:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.