There are five enabled badges in FATHOM’s public Roblox catalog on October 30, 2026. Collect them in this order: Welcome, Chapter 1 Complete plus one ending, the opposite ending, then Untouchable. That order turns a blind run into route knowledge before asking for a no-life-loss clear.
Badge statistics change continuously. Use the IDs and official developer descriptions to identify each badge, and treat award totals only as a dated rarity snapshot.
Complete badge list
Welcome
ID: 1512075721262168
You came to the park. It noticed.
Join the official FATHOM experience.
Chapter 1 Complete
ID: 2751310314657059
You climbed out of Chapter 1.
Finish the current Chapter 1 Story route.
Go Home
ID: 342709045766631
You chose to go home. Nobody leaves for long.
Select the Go Home branch.
Go Deeper
ID: 2216237297532
You chose to go deeper. He is glad you stayed.
Select the Go Deeper branch.
Untouchable
ID: 3343823445780188
Finish Chapter 1 without losing a life.
Complete the story with no life lost.
First run: entry, completion and one ending
Join Place ID 106632886527873 and confirm the creator is 「The Crimson Crusaders」. Welcome is the entry badge. If it does not appear, check that the official API still marks it enabled before troubleshooting an unrelated game.
Choose Story Mode and follow the Chapter 1 objectives. Use the grapple, camera flash, and lockers deliberately, but do not turn a first run into an Untouchable attempt unless you accept a restart. The useful outcome is learning the route and reaching the final choice.
At the branch, read the prompt and choose either Go Home or Go Deeper. A normal finish should target Chapter 1 Complete and the selected branch. Public descriptions do not prove the exact award moment, so let the ending sequence finish before leaving.
Second run: collect the other ending
Check your badge inventory first. If the opposite ending badge is missing, return to Story and plan for that choice. Do not assume an automatic save offers a direct ending replay; checkpoint behavior is not documented publicly.
Use the known route to conserve tools and avoid unnecessary sound. Near the final choice, confirm the target with the party. The Endings guide explains how to keep the two branches separate without claiming unsupported story results.
If a teammate controls the prompt, make sure every player understands the selection. The public catalog does not state whether one branch awards the whole party or only qualifying players.
Final run: attempt Untouchable
Treat any lost life as ending the attempt. Infinite Lives may allow Story to continue, but the badge condition still says “without losing a life.” There is no official public exception for passes, revives, or reconnects.
Choose a party size that minimizes unpredictable deaths. Solo gives control over sound and movement. A disciplined group adds route watching and objective reading. In either case, reserve defensive tools for known danger points and use one silence signal.
After every objective, regroup before moving. Do not let a successful escape become a second chase because the team immediately sprints back. The Untouchable guide provides a strict run checklist.
Read the October 30 rarity snapshot
The official API recorded 1,719,731 Welcome awards, 97,813 Chapter 1 Complete awards, 40,510 Go Home awards, 66,021 Go Deeper awards, and 4,712 Untouchable awards. Displayed rates were approximately 100%, 13.4%, 5.8%, 9.4%, and 0.7%.
Those figures show that Untouchable is currently the rarest, but they do not prove why. Do not infer that Go Home is mechanically harder than Go Deeper just because it has fewer awards. Choice preference and route timing can explain the difference.
Fix a missing badge
Confirm the badge is enabled, the account joined the correct Place ID, and the run fulfilled the exact developer description. For an ending badge, check the selected branch. For Chapter 1 Complete, make sure the full ending finished. For Untouchable, review every lost life in the run.
Rejoining can refresh the interface, but it cannot replace an unfulfilled condition. Avoid repeating a long run until the exact missing badge and likely failure point are identified.
Dynamic Roblox statistics can lag or update between checks. Use the badge inventory on your account as the final confirmation rather than a third-party rarity table.
Official source
- FATHOM badge API
- Chapter 1 Guide for the Story route plan.