Hit a Golf Ball Worlds

Roblox’s official Universe record for ⛳ Hit a Golf Ball contains five clearly named destination Places: Candy, Rainbow, Ocean, Moon, and Mecha. Those records verify that the destinations belong to Tiny Loop’s Universe 10529067596. They do not prove a player-facing order, unlock cost, portal location, shop, reward, or current public access.

Currently documented world index

What the official Place list proves

Each record has a numeric Place ID, Universe ID 10529067596, and a public name. The root experience is Place 138363592957250. Roblox’s thumbnail service also returns completed public icons for the five named Places. These facts are enough to verify identity and prevent a destination from being confused with another game’s area.

The API response order is not a progression order. It can reflect internal data ordering rather than how players travel. Alphabetical or numeric sorting would also create a false route. Follow the live experience’s portal, menu, or requirement text.

What the list does not prove

The records have blank descriptions. They do not publish a world entrance, Power threshold, currency cost, Club requirement, recommended distance, shop inventory, landing target, multiplier, reward, or return method. A guide should not fill those fields using the world’s theme or a different simulator.

One additional Place is named antonin51400's Place: 08252026_1. Its development-style name and lack of a confirmed player route make it unsuitable for the public world list. Do not attempt to treat it as a secret world or required progression step.

How to travel safely from the root experience

Start at the official root Place and inspect only travel controls the game presents: a portal, world selector, teleport prompt, or requirement panel. Read the destination name before confirming. If the game shows a locked state, record the exact requirement and return to the Power-Clubs-distance loop.

Avoid direct third-party teleport links and script executors. A public Place record does not guarantee that entering it directly preserves account state, completes the intended gate, or is currently supported. Use Roblox’s normal experience flow.

Record a world entrance

A useful entrance note includes the source area, visible landmark, control label, destination text, requirement, confirmation step, load transition, and return path. Capture the date and current game identity. Leave any field blank when the live UI does not show it.

After arriving, confirm the place name through the interface if possible. Record displayed Power, equipped Club, and distance baseline again. A different destination may change context, but the public Place record alone does not say how.

Decide when to leave the starting area

Travel when the live gate is satisfied and the destination offers a clear next action. If the requirement is above your current state, continue upgrading Power or unlocking Clubs rather than guessing a bypass. The Progression hub provides a controlled upgrade loop.

If no world control is visible, finish any current on-screen introduction, reset the ball state, and inspect the main menu. Do not assume that every official Place is public to every account at all times.

Compare worlds without a false tier list

Use fields players can observe: access requirement, arrival method, available upgrades, Club entries, visible boosts, distance context, and exit method. A world can be useful for a specific account without being universally “best.” Do not rank themes or Place IDs as difficulty.

The Worlds list provides a compact identity table. Individual guides focus on confirming the correct destination and collecting the current route details without claiming unsupported mechanics.

Handle a failed transfer

If a confirmed travel control fails, wait for the current ball result and any purchase prompt to close. Read the gate again, confirm the destination name, and try once more through the normal interface. If Roblox reports a teleport or server error, rejoin the root experience rather than opening an unverified URL.

Record the source Place, target name, time, device, and visible error. That distinguishes a platform transfer problem from an unmet in-game requirement.

World updates and change tracking

The Universe list is a snapshot checked September 2, 2026. A new Place record can indicate a destination under development, but it does not prove a player update. Wait for a live entrance or creator announcement before adding it to the public navigation.

Likewise, an existing Place can remain in the Universe when access changes. Recheck current entrances and requirements after a game update rather than assuming the Place record guarantees availability.

Worlds FAQ

How many worlds are confirmed?

Five player-facing named Places are currently documented in addition to the root experience: Candy, Rainbow, Ocean, Moon, and Mecha.

What order are the worlds in?

No official public source establishes an order. The API response order must not be used as progression.

Can I join a Place directly?

Use the in-experience travel flow. A direct Place record proves identity, not that bypassing the normal gate is supported.

Is the development-style Place a secret world?

There is no evidence for that. It is excluded until Tiny Loop provides a clear player-facing identity and route.

Source

• Roblox Universe Places record for Universe 10529067596 — official, checked September 2, 2026.