Offline 195.93.149.246:28015 checked 11d ago
213 Test
Connect
srv = rust.server("195.93.149.246: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. 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 53% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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 2, 2 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 15:17 UTC12d ago | 2 | NaN | running | 1 |
| 1 | Thu 15 Oct, 07:37 UTC13d ago | 2 | NaN | 1.3 days | 1 |
| 2 | Wed 14 Oct, 13:44 UTC14d ago | 2 | NaN | 0.7 days | 0 |
| 3 | Tue 13 Oct, 22:57 UTC15d ago | 2 | NaN | 0.6 days | 0 |
| 4 | Mon 12 Oct, 09:23 UTC16d ago | 2 | NaN | 1.6 days | 0 |
| 5 | Wed 7 Oct, 19:12 UTC21d ago | 1 | NaN | 4.6 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
- map
- –
- size
- –
- seed
- –
Server
srv.info()- address
- 195.93.149.246:28015
- region
- – · ger
- max players
- 10
- group limit
- not published
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 15:17 UTC
- hostname
- –
- first seen
- 7 Oct 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 · 560 on average | 237/275 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 162/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 292 on average | 28/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 291 on average | 16/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 34/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 45/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does 213 Test rank?
Rank #11,484 on seven-day player hours for 213 Test, within the top 53% of all ranked servers.
How full does 213 Test run?
The current row shows 213 Test offline; the last response was 11 days 15 hours ago.
Server facts
What is the Rust version on 213 Test?
Version Rust network protocol 2556 and build 104071 on Windows is reported by 213 Test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is 213 Test, and is it up?
Offline now for 213 Test, last seen 11 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 7 October 2026.
Where does 213 Test sit?
There is no region published for 213 Test, and the region code is ger. 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 195.93.149.246:28015.
Map and rules
Which rules apply on 213 Test, and what settings?
The name 213 Test carries no gather rate. No group limit is published. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC off.
Which map has 213 Test selected?
A procedural map runs on 213 Test, generated by the game.
Wipes and dates
When does 213 Test wipe, and how often?
No next wipe can be predicted for 213 Test, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 12 days 9 hours ago, and that is the one in play.
On 213 Test, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 2 hours after it began.
Tags and filters
Where does 213 Test appear among Rust Data lists and filters?
The Rust Data lists that 213 Test fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.
Which meanings do the tags on 213 Test hold?
These tags are published by 213 Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; v2556 (Protocol): To join, your game must run protocol 2556; cs104071 (Build): The server runs build 104071; ptrak (Networking): Network traffic runs over RakNet, the game standard; $rger (Region code): The row gives ger as its region code. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join 213 Test?
In Rust, F1 opens the console: type client.connect 195.93.149.246:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.