Offline 162.43.50.29:28015 checked 1h ago
SOLOTEST07
Connect
srv = rust.server("162.43.50.29:29015")
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 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 01:30 UTC27d ago | 1 | NaN | running | 1 |
# 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
4250 · seed 28714298
- map
- Procedural Map
- size
- 4250
- seed
- 28714298
Server
srv.info()- address
- 162.43.50.29:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 03:05 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 522 on average | 232/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 310/325 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 24/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 24/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 50/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 246 on average | 142/200 |
Quick answers
From the figures on this page.
Population
How does SOLOTEST07 compare in the rankings?
Player hours over seven days put SOLOTEST07 at #4,699, in the top 21% of the ranked set.
How many players does SOLOTEST07 hold at once?
The current row shows SOLOTEST07 offline; the last response was 1 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 10:00 UTC is the busiest, at 1 players.
About the server
How well does SOLOTEST07 perform?
Server fps over the last 48 hours averages 47; the floor is 30. Buildings, deployables and all else in the world took the count as high as 104,567 entities. A high of 3,260 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is SOLOTEST07 on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by SOLOTEST07. Steam updates your game for you, but the protocol must match to join.
How reliable is SOLOTEST07, and is it online now?
SOLOTEST07 is offline at this refresh; the last response came 1 hours ago. Count back 5 hours from its reported uptime to get the last restart. Uptime of 36% across the last 7 full days: 61 hours of 168. Rust Data logged it first on 13 September 2026.
Which location does SOLOTEST07 run from?
There is no region published for SOLOTEST07. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 162.43.50.29:28015.
Rules, settings, map
Which settings and rules does SOLOTEST07 run?
The name SOLOTEST07 carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
Which map has SOLOTEST07 selected?
The game generates the map on SOLOTEST07: procedural, size 4,250, seed 28714298. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does SOLOTEST07 wipe, and how often?
The record for SOLOTEST07 holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 27 days 6 hours ago.
On SOLOTEST07, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in.
Tags, lists
Which lists on Rust Data hold SOLOTEST07, and which filters?
These Rust Data lists include SOLOTEST07: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on SOLOTEST07?
Read by the game's server browser, the tags SOLOTEST07 publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; 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): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join SOLOTEST07?
Enter client.connect 162.43.50.29:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.