J Rust Server
Online NA 66.51.98.57:28020 checked 7m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 10 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 69% of all ranked servers, top 83% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Saturday 31 October, 17:38 UTC, in 3d 19h. Every Saturday at 17:38 UTC · low confidence
- usual gap
- 7 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
Coming wipes
- in 3d 19hSat 31 Oct, 17:38 UTC
- in 8d 20hThu 5 Nov, 19:00 UTCFW
- in 10d 19hSat 7 Nov, 17:38 UTC
- in 17d 19hSat 14 Nov, 17:38 UTC
- in 24d 19hSat 21 Nov, 17:38 UTC
- in 31d 19hSat 28 Nov, 17:38 UTC
- in 36d 20hThu 3 Dec, 19:00 UTCFW
- in 38d 19hSat 5 Dec, 17:38 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
24 OCT 2026Sat 24 Oct, 17:38 UTC3d ago |
0 | – | running | 0 |
17 OCT 2026Sat 17 Oct, 17:24 UTC10d ago |
0 | – | 7 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Map and rules
Where can you read the rules and settings that apply on J Rust Server?
You will find no gather rate in the name of J Rust Server. The default group limit of 8 players applies. Filed under survival, gather, build and raid: the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on J Rust Server?
J Rust Server runs a procedural map of size 3,000 with seed 418060900, generated by the game. The map can be seen on RustMaps from this page, because the same size and seed give the same map.
Lists and filters
Where does J Rust Server appear among the Rust Server Index lists and filters?
The Rust Server Index lists that include J Rust Server are Modded Rust servers, filed by play style and North American Rust servers. Filed under these filters on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.
How should you read the tags listed for J Rust Server?
The server's own tags are listed here, and the game's server browser reads them: J Rust Server gives gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): The queue ceiling sits at 50; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): Joining needs you on game protocol 2635; cs168909 (Build): The game build here is 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^m (Monthly): It wipes monthly with the force wipe from Facepunch; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings; NA (North America): Server browser region: North America. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe schedule
What should you expect on J Rust Server when wipe day comes?
Its recent wipes averaged 0 players at peak. The latest wipe peaked 0 hours in.
Which wipe timetable does J Rust Server follow?
every Saturday at 17:38 UTC is how J Rust Server wipes. On Saturday 31 October at 17:38 UTC the next wipe is due. Its present world dates from 3 days 4 hours. Its tags state a wipe schedule of once a month.
Players and ranking
What position does J Rust Server hold among Rust servers?
On seven-day player hours, J Rust Server takes #15,404 overall and #1,550 in North America, within the top 69% of ranked servers.
What does the player count on J Rust Server look like?
The live count for J Rust Server stands at 0 players, out of 50 slots. 0 players is the average over the past seven days.
Server details
What version does J Rust Server use?
Rust network protocol 2635 and build 168909, on Linux, is what J Rust Server runs. The protocol must match before you can join, and Steam takes care of updating it.
Is J Rust Server reachable, and does it stay up?
The server is live at this moment: J Rust Server. Its reported uptime gives the last restart as roughly 3 days 3 hours ago. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. It was first recorded by Rust Server Index on 9 October 2026.
How well does J Rust Server perform?
The last 48 hours give an average of 5 server fps and a floor of 5. The entity count reached 45,875, covering buildings, deployables and all else in the world. Up to 2,154 MB of memory was in use. A climbing entity count and low fps are felt by players as lag.
Which region is J Rust Server in?
The NA tag places J Rust Server, by its own listing, in North America. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 66.51.98.57:28020.
Connecting
What is the way onto J Rust Server?
Two ways in. Type client.connect 66.51.98.57:28020 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp50
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^m
Mods and access
^o
^z
Region
NA
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
