Dragon Ball Fusion World FB10 July Meta Report 2026

Dragon Ball Fusion World FB10 July meta is best treated as a dated retrospective, not a live September tier list. This update separates the July evidence from later ST01 results and corrects a serious naming problem in the old copy: FB09 Son Gohan: SH is not the same Leader as the FB10 Son Gohan/Piccolo card.

TL;DR: The clearest independently published July result found for this audit is the Pomona Regional held July 19, 2026. Its Top 32 had FS11 Son Goku at 9 players, FB09 Son Gohan: SH and FB09 Gogeta: BR at 6 each, and FB10 Vegito at 4. FB09 Son Gohan: SH won the event. Those counts are a regional snapshot, not proof of one universal best deck.

Dragon Ball Fusion World FB10 July meta? (quick answer)

The verified Pomona result does not support the old headline that FB10 Vegito led every July event. FS11 Son Goku was the most common Leader in the Top 32, while FB09 Son Gohan: SH won after placing three players in the Top 8. FB10 Vegito had four Top 32 players, one Top 16 player, and no Top 8 player in that event.

That is a useful result, but it is not a complete format ranking. The source is an independent tournament report, not a Bandai global standings database. Keep its date, event, sample size, and Leader IDs attached whenever you cite it.

What this July report can and cannot prove

The previous version presented several tier placements as settled facts while also admitting that no centralized FB10 database had been independently verified. Those two ideas do not fit together. A report can discuss a community read, or it can report a defined tournament sample, but it should not turn an unmeasured impression into a precise S-tier and A-tier table.

For this audit, the hard evidence is a published breakdown of the July 19 Pomona Regional in California. The report was posted July 26 and lists the Top 32, Top 16, Top 8, finalist Leaders, and decklists. It identifies itself as an unofficial fan-made site, so it is useful event evidence rather than an official Bandai ranking.

Bandai's own Championship Wave 1 page confirms the official regional series and its Standard qualifying match structure. The Bandai page does not provide the Pomona standings used below. That distinction matters: the event series is official, while the detailed deck distribution comes from the independent report.

This article therefore keeps the Pomona counts, removes unsupported global tier claims, and avoids presenting the current September environment as if it were still the July field.

Dragon Ball Fusion World FB10 July meta: what Pomona actually showed

The source reports these Leader counts:

The percentages are rounded in the source. The counts are the safer way to cite the result, especially because the Top 32 percentages total 99.8 after rounding.

The event report names two FB09 Son Gohan: SH players as the finalists, with gvbhino taking the win. It also records FS11 Son Goku as the most represented Leader at every cut shown. The field was therefore not a simple FB10-only contest, even though Cross Force was the new expansion being discussed at the time.

What the result says about FB10 Vegito

FB10 Vegito was present, but the Pomona numbers are narrower than the old copy suggested. Four Vegito players reached the Top 32. One reached the Top 16, and none reached the Top 8. The report identifies SD1_Leo in ninth place as the best-performing Vegito pilot at that event.

That does not prove that Vegito was a bad choice in July. It shows that the deck's presence and conversion were different things in this sample. A Leader can appear often in a cut and fail to reach the final rounds, or have a small field presence and convert well. Use both measures when discussing tournament performance.

The source's Vegito list includes FB10-025 Son Goku/Vegeta, FB10-040 and FB10-041 Vegito, FB10-047 Potara, and FB10-121 Vegito, along with earlier-set support and promos. That composition is a better description of the deck than a generic claim that every competitive list was mostly FB10.

The Dragon Ball Fusion World FB10 Cross Force set guide covers the official card text and mechanics. A separate deck guide can explain sequencing, but its matchup claims still need their own date and evidence.

Do not merge the two Gohan Leaders

This was the most important factual correction in the old article. The Pomona winner played FB09-049 Son Gohan: SH. The event report lists the FB10 Son Gohan/Piccolo Leader separately, with one Top 32 appearance and no Top 16 or Top 8 appearance.

The winning list did include FB10-057 Son Gohan: Adolescence/Piccolo and FB10-070 Piccolo. That does not turn the Leader into an FB10 deck for reporting purposes. In a format with cross-set support, the Leader ID should be the first label, followed by the main product context if needed.

Use these labels consistently:

• FB09 Son Gohan: SH: the Leader that won Pomona and placed three players in the Top 8.
• FB10 Son Gohan/Piccolo: the Cross Force Leader that had one Top 32 appearance in the published Pomona table.
• FB10 support in an FB09 deck: cards from Cross Force can appear in an older Leader's list without changing the Leader's identity.

This correction also applies to tier lists, deck links, image captions, and FAQ answers. “Gohan” by itself is too vague for a tournament report.

Why one event should not become a tier list

The Pomona report gives enough information to discuss that event. It does not tell us the win rate of every deck across July, the strength of local events, or the performance of players who missed the Top 32. The old labels such as S-tier Vegito, A-tier Gohan/Piccolo, and B-tier Son Goku were not tied to a defined dataset in the article.

A more defensible July comparison has three layers:

1. Representation: how many copies of a Leader reached a cut.
2. Conversion: how many reached the next cut or the final.
3. Outcome: who won the event and which Leaders reached the final.

Pomona gives all three layers for one regional. It does not justify a global ranking. If a future report combines several events, it should name every event, avoid double-counting, and separate Top 32 share from win rate.

Later results should stay in their own window. The official site lists ST01 as an August 21 release, and current September regional results include decks from that product era. Adding those later events to a July table would make the historical comparison look larger while changing the card pool.

What to take into testing

The useful lesson from the July evidence is not a permanent purchase order. It is a better testing question.

If you are studying FB10 Vegito, compare its Top 32 presence with its Top 16 and Top 8 conversion in each dated event. If you are studying Gohan, record whether the result belongs to FB09 Son Gohan: SH or FB10 Son Gohan/Piccolo. If you are studying a newer Leader such as FS11 Son Goku, note whether the tournament occurred before or after Story Booster 01 became available.

For a deck list, record:

• the event name and date;
• the Leader card number;
• the product window;
• the cut reached;
• the source URL;
• whether the list is complete or only a featured deck.

That record makes it possible to update the report without rewriting old results as if they were current. It also prevents a single regional win from being used as a promise about the next tournament.

Step-by-Step: Reading a dated Fusion World result

1. Check the event date. July 19, August 8, and September events belong to different snapshots and may have different products available.

2. Confirm the event type. A Championship Regional, store event, release event, and digital limited battle do not represent the same sample.

3. Record the exact Leader ID. FB09 Son Gohan: SH and FB10 Son Gohan/Piccolo are not interchangeable labels.

4. Separate representation from conversion. Count Top 32, Top 16, Top 8, and finalists instead of quoting only the largest early cut.

5. Read the complete list when available. A Leader can use support from several products, so do not infer set identity from one card.

6. Cite the source's status. Mark whether the page is a Bandai announcement, organizer result, or community report.

7. Date any recommendation. A July result should remain labeled as July when later products or events change the environment.

For broader legality context, the Dragon Ball Fusion World FB10 format and rotation guide explains how to check the current rules and event notice. This page should remain the historical result record.

Frequently Asked Questions

What did the July 19 Pomona Regional show?

The published Pomona breakdown lists FS11 Son Goku as 9 of 32 Top 32 players, FB09 Son Gohan: SH and Gogeta: BR at 6 each, and FB10 Vegito at 4. Two FB09 Son Gohan: SH players met in the final, with gvbhino winning. The event is one dated snapshot, not a complete global ranking.

Did FB10 Vegito win the July 2026 Pomona Regional?

No. The Pomona report names gvbhino's FB09 Son Gohan: SH deck as the winner. FB10 Vegito reached the Top 32 and Top 16, but the source lists no Vegito player in the Top 8. That result does not make Vegito weak overall, but it does rule out calling it the Pomona champion.

Is FB09 Son Gohan: SH the same deck as FB10 Gohan/Piccolo?

No. They are different Leaders from different products. The Pomona winner used FB09-049 Son Gohan: SH, while the event list separately records FB10 Son Gohan/Piccolo. The winning list did use some FB10 cards, so identify the Leader ID before describing the archetype or citing the result.

Can one regional event establish the July meta tier list?

No. Pomona gives a useful Top 32, Top 16, and Top 8 distribution, but it does not cover every region, store event, online result, or local field. A tier label needs a defined sample, date range, and method. This report keeps the verified event counts and avoids turning one result into a universal ranking.

What should I use for current Fusion World tournament advice?

Use a current event result or tracker dated near your tournament, then check the official event format and banned or restricted rules. This page is a July retrospective updated for source accuracy, not a September tier list. Later ST01 events belong to a different evidence window and should not be folded into the July table.

Did the July field contain only FB10 decks?

No. The Pomona Top 32 included FS11 Son Goku, FB09 Son Gohan: SH, FB09 Gogeta: BR, FB09 Gogeta: GT, FB10 Vegito, FB09 yellow Gogeta, and FB10 Son Gohan/Piccolo. The mix shows why a product-only label can hide the actual competitive field during the Cross Force period.

Is there an official Bandai July meta ranking?

Bandai's official pages publish product information, event schedules, rules, and card data, but the sources checked for this update do not publish a global July tier ranking. Community reports can still document individual events. Cite the organizer, date, sample size, and Leader IDs instead of presenting a community placement as an official Bandai ranking.

Related Reading

• Dragon Ball Fusion World FB10 Tier List: 5 Leaders Ranked: a separate dated community analysis that should not be read as official standings.
• Dragon Ball Fusion World FB10 Cross Force Set Guide: official product details, card IDs, Leaders, and SCRs.
• Dragon Ball Fusion World FB10 Format and Rotation Guide: current legality checks and the difference between Standard and limited events.
• Dragon Ball Fusion World Standard Format Guide 2026: broader deck-building and rules context.
• Dragon Ball Fusion World FB10 Six-Week Meta Settle: another dated analysis that needs to be read with its evidence window.

References

• 2026 Pomona Regional results and decklists: July 19 event counts, Top 32 through Top 8 tables, finalist Leaders, and decklists.
• Championship 26-27 Regionals Wave 1: official regional series and Standard qualifying event structure.
• FB10 Cross Force product page: official release date, five Leaders, and set details.
• Official Fusion World card database: card IDs and card text for distinguishing FB09, FB10, and FS11 Leaders.
• Official Fusion World rules: current rules and banned or restricted card policy.
• Dragon Ball Fusion World news archive: later tournament coverage that should not be merged into this July snapshot.