Online 195.18.27.46:35500 checked 10m ago
RA TEST
Connect
srv = rust.server("195.18.27.46:35510")
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 26% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 17h | Thu 12 Nov, 10:24 UTC | wipe |
| 2 | 20d 17h | Thu 19 Nov, 10:24 UTC | wipe |
| 3 | 27d 17h | Thu 26 Nov, 10:24 UTC | wipe |
| 4 | 35d 1h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 41d 17h | Thu 10 Dec, 10:24 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 10:24 UTC6h ago | NaN | NaN | running | 1 |
| 1 | Tue 27 Oct, 21:51 UTC1d ago | NaN | NaN | NaN | 0 |
| 2 | Sat 24 Oct, 18:02 UTC4d ago | 1 | halved by day 1 | 3.2 days | 0 |
| 3 | Mon 19 Oct, 12:46 UTC10d ago | NaN | NaN | 5.2 days | 0 |
| 4 | Thu 15 Oct, 19:27 UTC13d ago | 1 | held half | 3.7 days | 0 |
| 5 | Wed 7 Oct, 13:15 UTC22d ago | 4 | halved by day 3 | 8.3 days | 0 |
| 6 | Fri 18 Sep, 12:44 UTC41d ago | 7+4 queue | halved by day 3 | 19 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
6000 · seed 1384870952
- map
- Baйп был 6ч нaзaд
- size
- 6000
- seed
- 1384870952
Server
srv.info()- address
- 195.18.27.46:35500
- region
- –
- max players
- 100
- group limit
- 16 max
- wipe schedule
- weekly
- last wipe
- 29 Oct 2026, 10:24 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 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 1 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 2 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 350/350 |
| 3 | [NA] Willjum's Solo Only | Thursday Wipes | NA · groups of 8+ · weekly · 27 on average | 4/100 |
| 4 | [EU] Willjum's Solo Only | Thursday Wipes | EU · groups of 8+ · weekly · 25 on average | 36/175 |
| 5 | QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 25 on average | 33/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does RA TEST rank?
Over the last seven days RA TEST sits at #5,798 on player hours, in the top 26% of ranked servers.
How full does RA TEST run?
The sample now reads 0 players for RA TEST, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 3. The 48-hour sample puts the busiest hour at 14:00 UTC, averaging 3 players.
About the server
What does performance look like on RA TEST?
Averaged over 48 hours: 30 server fps, never under 29. Entity numbers reached 130,687, and that includes buildings, deployables and the rest. Memory peaked at 3,187 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is RA TEST on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by RA TEST. Steam updates your game for you, but the protocol must match to join.
Is RA TEST up, and what does its uptime show?
The current sample puts RA TEST online. Count back 4 hours from its reported uptime to get the last restart. 106 of 168 hours up over the last 7 full days, or 63%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does RA TEST run from?
There is no region published for RA TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 195.18.27.46:35500.
Map and rules
Which rules apply on RA TEST, and what settings?
You will not find a gather rate in the string RA TEST. The cap on a group is 16 players. Recorded as survival, 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. The description says vanilla, which here means no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat status: VAC on.
Which map has RA TEST selected?
Size 6,000, seed 1384870952: the procedural map on RA TEST, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Baйп был 6ч нaзaд.
Wipe data
When does RA TEST wipe, and on what schedule?
The prediction follows the tag, because RA TEST's wipes on record are too few to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 6 hours ago. A weekly wipe schedule is published in its tags.
What is wipe day on RA TEST like?
The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 5 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 25% of the time. In the wipes where it did not hold, half was lost by day 3.
Tags, lists
Which Rust Data filters and lists contain RA TEST?
These Rust Data lists include RA TEST: Modded Rust servers and Rust tutorial servers. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Tutorial on ^t, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours.
How should you read the server tags on RA TEST?
The game's server browser reads these tags from RA TEST: gmvanilla (Game mode): Game mode: vanilla survival; mp100 (Max players): The server lists 100 slots; ts16 (Group limit): The team cap is 16; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; 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; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^t (Tutorial on): Facepunch's tutorial is available to new players here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; oxidation (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. 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
How can I connect to RA TEST?
In Rust, F1 opens the console: type client.connect 195.18.27.46:35500. Launch Rust on this page does the same by opening the game through Steam and connecting. https://rustaria.tech/ is the website recorded for it.