Offline 185.181.220.138:28015 checked 12h ago
Local Custom Map Test
Connect
srv = rust.server("185.181.220.138: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, measured since 21 Oct. 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 44% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 21:47 UTC13h ago | NaN | NaN | running | 1 |
| 1 | Tue 27 Oct, 20:08 UTC1d ago | NaN | NaN | NaN | 1 |
| 2 | Wed 21 Oct, 19:03 UTC7d ago | 2 | NaN | 6 days | 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
4000 · seed 1337
- map
- Custom Map
- size
- 4000
- seed
- 1337
Server
srv.info()- address
- 185.181.220.138:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Oct 2026, 21:47 UTC
- hostname
- –
- first seen
- 21 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 · 516 on average | 463/475 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 409/375 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 49/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 37/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 55/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 243 on average | 152/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Local Custom Map Test rank?
Over the last seven days Local Custom Map Test sits at #9,796 on player hours, in the top 44% of ranked servers.
How full does Local Custom Map Test run?
The current row shows Local Custom Map Test offline; the last response was 12 hours ago. Over the last seven days it averaged 1 players and peaked at 2. The 48-hour sample puts the busiest hour at 22:00 UTC, averaging 2 players.
About the server
What does performance look like on Local Custom Map Test?
Server fps over the last 48 hours averages 149; the floor is 149. Entity numbers reached 94,500, and that includes buildings, deployables and the rest. Memory peaked at 1,666 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Local Custom Map Test on?
Rust network protocol 2635 and build 168909 on Windows is what Local Custom Map Test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local Custom Map Test, and is it online now?
Offline now for Local Custom Map Test, last seen 12 hours ago. The uptime it reports puts the last restart about 15 minutes ago. 3 of 168 hours up over the last 7 full days, or 2%. Its earliest recorded date in Rust Data is 21 October 2026.
Where does Local Custom Map Test sit?
There is no region published for Local Custom Map Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 185.181.220.138:28015 is its address.
Rules, settings, map
What rules and settings are recorded for Local Custom Map Test?
You will not find a gather rate in the string Local Custom Map Test. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
Which map has Local Custom Map Test selected?
The game generates the map on Local Custom Map Test: procedural, size 4,000, seed 1337. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.
Wipe data
When does Local Custom Map Test wipe, and how often?
Local Custom Map Test wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 13 hours ago, and that is the one in play.
On Local Custom Map Test, what happens on wipe day?
The average peak over recent wipes is 2 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does Local Custom Map Test appear among Rust Data lists and filters?
These Rust Data lists include Local Custom Map Test: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.
Which meanings do the tags on Local Custom Map Test hold?
The game's server browser reads these tags from Local Custom Map Test: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): 4 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; 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. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to Local Custom Map Test?
In Rust, F1 opens the console: type client.connect 185.181.220.138:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.