Online 138.255.7.181:28015 checked 13m ago
JMS
Connect
srv = rust.server("138.255.7.181:28016")
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 11 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 43% 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 2, 26 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 11 Oct, 18:06 UTC16d ago | 2 | NaN | running | 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
4250 · seed 477406466
- map
- Procedural Map
- size
- 4250
- seed
- 477406466
Server
srv.info()- address
- 138.255.7.181:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 18:06 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 · 543 on average | 679/725 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 429/475 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 308 on average | 40/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 308 on average | 52/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 268 on average | 228/250 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 266 on average | 134/175 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does JMS rank?
Rank #9,483 on seven-day player hours for JMS, within the top 43% of all ranked servers.
How many players does JMS hold at once?
JMS reports 0 players at this refresh, with 20 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 00:00 UTC is the busiest, at 1 players.
Server data
How smoothly does JMS run?
Averaged over 48 hours: 97 server fps, never under 81. The entity count peaked at 106,817, covering buildings, deployables and the rest of the world. A high of 4,035 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does JMS run?
Rust network protocol 2635 and build 168909 on Windows is what JMS runs. The protocol has to match before you can join, and Steam does the updating.
Is JMS up, and what does its uptime show?
JMS reports itself online at the current refresh. Count back 4 days 18 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is JMS hosted?
For JMS, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 138.255.7.181:28015.
Rules, settings, map
What rules and settings are recorded for JMS?
No gather rate appears in the name: JMS. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: 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. VAC, Valve's anti-cheat, is enabled.
What is the map on JMS?
JMS runs a procedural map of size 4,250 with seed 477406466, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
On what schedule does JMS wipe?
A rhythm cannot be read from the wipes of JMS on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 16 days 19 hours ago.
On JMS, what happens on wipe day?
The average peak over recent wipes is 2 players. 26 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold JMS, and which filters?
These Rust Data lists include JMS: 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.
Which meanings do the tags on JMS hold?
These tags are published by JMS and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. 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.
Connecting
What is the way into JMS?
In Rust, F1 opens the console: type client.connect 138.255.7.181:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.