Fixed spawn coordinates
No location list or map exists from a confirmed source. The recorded player travelled the map rather than visiting known points, so nothing here can tell you where a ball will be.
A grounded walkthrough of the Dragon Ball collection step in Speedsters Beyond on Roblox. Follow the search route recorded on August 27, 2026, use the Mystery Orb fallback when a sweep stalls, and see exactly which parts of this task are confirmed and which are still player reports.
Start by equipping Goku and opening the evolution card. That card is the authority on your progress: a dated August 31, 2026 thumbnail showed it reading 0/7 for Dragon Balls, and the same field tells you how many are still missing on your account.
Goku's evolution is a multi-part objective, and the Dragon Balls are one part of it. In a dated August 31, 2026 thumbnail from Wave YT, the card was recorded showing Points To Evolve 25,000,000, 35x → 45x and a 0/7 Dragon Ball counter, which is where the count of seven comes from. Points and EXP multipliers are separate fields from the Dragon Ball count, so a points total that is not moving does not block this collection task.
The requirement list also has a version boundary worth knowing. An earlier recorded session (ExyRBLX, August 27, 2026) opened the same Goku evolution screen and found it marked Soon with 0/0 tasks and the message This evolution arrives in a future update! The Dragon Ball objective belongs to a later build than that recording. If your own card still shows the future-update state, the collection task has not started on your account yet.
The full evolution picture, including the quest-list step that is separate from delivery Jobs, is tracked on Dio & Goku evolution status.
The card carries the Dragon Ball counter. Note the number before you start, so you can tell whether a sweep actually added a ball.
In the recorded session, the player travelled the outermost perimeter at speed and watched for a ball to appear around him rather than heading to a fixed landmark.
The recorded route was continuous travel, not a stationary camp. If nothing appears, complete the lap before changing your approach.
The recorded player said he was stuck on the 6th and 7th, then found them beside a Mystery Orb he passed on the way to a claim, and suggested checking the nearest orb if a sweep stalls after roughly three minutes.
The counter is the only progress signal documented here. If it moved, the ball counted; if it did not, keep searching rather than assuming a hidden step.
Unequipping Goku and equipping him again was described in the same recording as ineffective and a waste of time. It is not part of this route.
| Item | What has been recorded | Evidence status |
|---|---|---|
| Seven-ball counter | Goku's evolution card showed a 0/7 Dragon Ball count on a dated August 31, 2026 thumbnail. | Dated thumbnail |
| Outer-edge sweep | The recorded player narrated finding the earlier balls while running the map's outermost perimeter (August 27, 2026 session). | Creator narration |
| 6th and 7th near a Mystery Orb | The same session found the last two beside a Mystery Orb the player was already travelling towards; a viewer comment agrees the final two are slow. | Single session |
| Roughly three-minute stall rule | Suggested by the recorded player as a point at which to change tactic. No stopwatch measurement or repeat test is available. | Player suggestion |
| Server hop for a fast set | One viewer reported all seven in about 20 minutes by leaving and rejoining; the video's author replied that the same tactic did not work for him. | Disputed |
| Morph reset (unequip and re-equip) | Described in the recorded session as having no effect on spawns. | Creator narration |
| Coordinates, spawn timer, drop rate | No published or recorded source. Nothing confirmed about how often the balls spawn or whether they are random per server. | Unconfirmed |
Work through these in order. Each one is a real action taken in a recorded session or reported by a player, and none of them requires a resource.
Server hopping is left out of this list on purpose. One player reported it as a fast route and the video's own author reported the opposite result, so there is no agreement to build a routine on. If you try it, compare your own counter before and after instead of trusting either report.
No location list or map exists from a confirmed source. The recorded player travelled the map rather than visiting known points, so nothing here can tell you where a ball will be.
Whether balls spawn on a timer, on laps completed, or at random is unknown. That is why this page gives a fallback action instead of a waiting time.
Reports about leaving and rejoining conflict, and one session cannot show whether two players in the same server see the same balls. Check your own counter across sessions before forming a routine.
No reviewed material shows two players racing for the same Dragon Ball. Whether a ball is claimable by one player only, as Dio's Bone is, has not been recorded for this objective.
A dated August 31, 2026 video thumbnail showed Goku's evolution card with a 0/7 Dragon Ball counter alongside a 25,000,000 Points requirement. The same counter is the one to read in your own client: open the evolution card while Goku is equipped and it states how many of the seven are still missing.
The only search route recorded so far is a sweep of the map's outer edge. In an August 27, 2026 community recording, the player narrated finding the earlier balls while sprinting along the outermost perimeter, then found the sixth and seventh next to a Mystery Orb. Those are one player's observations from that session, not published spawn coordinates.
Players describe a long stall on the final balls: one viewer of the same recording wrote that the 6th and 7th "do take years". No spawn interval, spawn location list or drop rate has been published by the developer, so there is no confirmed number of attempts to expect. Treat the stall as normal and use the Mystery Orb fallback rather than assuming your game is broken.
Reports disagree. One viewer commented that by looking around the spawn point and leaving and rejoining the server, all seven Dragon Balls took about 20 minutes. The creator of that video replied that the same approach did not work for him when he collected them for his own Goku. That makes server hopping a disputed player report, not an established shortcut.
Not from a confirmed source. No fixed coordinates have been published by the developer, and the recorded session located them while moving across the map rather than by following fixed points. If a location list is published or a second independent recording confirms the same spots, this page will record it.
Not confirmed either way. Dragon Ball collection is a Goku evolution objective rather than a Mystery Orb claim, and no recording reviewed here shows two players contesting the same ball. Mystery Orbs themselves are shared world entities and can be claimed by whoever reaches them first.
No. In the recorded August 27, 2026 session the player saw the later Dragon Balls next to one Mystery Orb he passed on the way to a claim, and suggested checking the nearest orb if a sweep stalls for roughly three minutes. That is a recovery suggestion from a single session, not a rule that every orb produces a ball.