Put the facts players filter by into the name
Rust players scan the server browser for a few facts. If they have to join to find them out, most will not.
- Region, for example EU or US East.
- Group limit: solo, duo, trio, quad or no limit.
- Rates: vanilla, 2x, 3x, 5x and so on.
- Wipe schedule: weekly, every two weeks, or monthly with the forced update.
- Last or next wipe, if you have room.
Keep the rest of the name short. A clean name such as “Northline EU | 2x | Solo/Duo | Wipe Thu” is easier to trust than one packed with symbols.
Choose a wipe schedule and keep it
Facepunch releases the monthly forced update on the first Thursday of each month, and every server wipes the map then. Many players start fresh on that day, so it is the biggest opportunity for a new server.
Between forced wipes, pick a rhythm that fits your audience and do not change it on short notice. Players plan their week around wipe day. Announce whether a wipe includes blueprints, and post the exact time in your time zone and in UTC.
Be specific about your rules and plugins
A modded server with kits, teleports and stack changes attracts a different player from a vanilla-like one. Neither is better; mixing up what you are costs players.
- List the plugins that change gameplay in your description and in Discord.
- State your group-limit rules and how you enforce them, including what counts as teaming.
- Explain how cheating reports are handled and how fast admins respond.
Make wipe day count
Your population at the start of a wipe decides the rest of the cycle. Treat wipe day as a launch every time.
- Post the wipe announcement in your Discord a day early and again an hour before.
- Have admins online in the first hours. A quick ban of an obvious cheater keeps honest players.
- Keep server performance stable when the map is fresh and busy. Lag on wipe day sends players to the next server.
Keep a population through the cycle
Most Rust servers lose players as large groups take over the map. You cannot prevent that completely, but you can slow it.
- Enforce group limits consistently, especially against large groups on a small-group server.
- Consider a shorter wipe cycle if your server empties after a few days.
- Run small events late in the cycle, such as a raid night or an arena, so there is a reason to log in.
Be findable outside the game
A free ServerRoam draft stays private until every address has accepted control evidence and the community passes independent moderation. Hostnames can use gated DNS-TXT; bare IP addresses need independent manual proof. Verification is not an endorsement or a guarantee of live monitoring.
What to avoid
Inflated player counts, misleading “high pop” claims and fake wipe times bring players who leave angry and talk about it. In a game where reputation travels through clans and streamers, an honest server name and a reliable schedule are the most effective promotion you have.
A wipe calendar players can actually use
- Publish a rolling four-week calendar. Give the next map reset and blueprint reset separately, the time zone, team-size limit and any exceptions. Do not infer a server’s schedule from the game’s update cycle.
- Ask consenting pilot players: “Do I lose blueprints?”, “Can a fourth friend join our team?” and “What happens if the update is delayed?” These are interview prompts, not reported research.
Next map wipe: [date, time, zone]
Next blueprint wipe: [date, time, zone or no reset]
Team limit: [ ]
Update delay policy: [ ]
Last confirmed by owner: [date]
