Data Report

Which Blox Bulletin hints actually shipped: a 24-issue data report

We track the outcome of every developer hint in the Blox Fruits “Blox Bulletin” newsletter at the hint level. This report aggregates that record: of 94 hints across 24 issues, how many shipped, how many still sit open, and how rarely a hint was ever contradicted.

Blox Fruits Calculator Team

What this report measures

The Blox Bulletin is the official Blox Fruits newsletter. Each issue teases what might be coming next in deliberately vague language. Fan wikis archive the issues and trackers summarise each new one, but nobody keeps a record of which of those teases actually came true. This site does — at the level of the individual hint, not the issue — and this report turns that record into aggregate numbers anyone can check.

Scope: 24 issues, published March 20, 2025 to July 31, 2026, carrying 94 tracked hints in total. Every figure below is computed at build time from the same data file that powers the public issue pages, so the report and the issue badges can never disagree.

The headline finding

Blox Bulletin hints are almost never wrong — they over-tease. Only 1 of 94 hints (1.1%) was ever contradicted by what shipped. The uncertainty in a bulletin is not that it misleads you; it is that it teases far more than it delivers on any near timeline: 49 hints (52.1%) shipped and 43 (45.7%) still sit open. The practical risk to a reader is reading a tease as a promise, not being told something false.

Blox Bulletin hint outcomes, all 94 tracked hints A single horizontal bar of 94 developer hints split by outcome: 49 shipped (52.1%), 43 still open (45.7%), 1 partial (1.1%), and 1 contradicted (1.1%). 49 52.1% 43 45.7% Shipped — 49 (52.1%) Open — 43 (45.7%) Partial — 1 (1.1%) Contradicted — 1 (1.1%)
Every one of the 94 hints tracked across 24 Blox Bulletin issues, by outcome. Contradicted hints — cases where what shipped disproved the tease — make up a 1.1% sliver. Computed at build time from the site's bulletin data.

Method

The data lives in the site's Blox Bulletin dataset. Each issue records its publication date and a list of hints; each hint carries one of four statuses:

  • Shipped — the teased thing arrived in a named update or event.
  • Partial — part of it arrived, or it arrived in a weaker form than the tease implied.
  • Contradicted — what shipped actively disproved the tease.
  • Open — nothing matching it has shipped yet.

Statuses are assigned by checking each hint against the official patch notes and the update or event it maps to, recorded on the hint as the delivering update (for example “Update 27”). Where a hint was ambiguous it was left open rather than counted as shipped — the counts lean conservative on purpose. The issue-level badge on each public page is derived from these hint statuses in code, so it is the same source this report aggregates. Percentages are of the 94-hint total unless stated otherwise; every figure here is recomputed from the data at build time.

One thing the dataset deliberately does not contain is the real-world release date of each update. Because of that, this report does not quote a bulletin-to-release “lag” in days: that number cannot be computed from the data without importing dates from outside it, so it is left out rather than estimated. What the data does support — the span of issue dates whose hints each update absorbed — is shown in the delivery chart below.

The raw figures

OutcomeHintsShare
Shipped4952.1%
Open4345.7%
Partial11.1%
Contradicted11.1%
Total94100%

The findings

1. Being contradicted is vanishingly rare

Across 24 issues, exactly 1 hint was contradicted by what shipped (in issue #008). A reader treating a bulletin as a source of false information has the wrong worry: the bulletins rarely say a thing that later turns out untrue. The gap between a bulletin and reality is almost entirely omission — things teased that have not (yet) happened — not error.

2. “Open” is mostly “not yet”, not “never” — but not entirely

Raw, 45.7% of all hints are open, which looks like a low delivery rate. But that number is dominated by recent issues that simply have not had their update yet. Splitting the issues by whether they are old enough to judge makes the difference clear. Taking issue #019 as the cutoff — the last issue whose hints reached a numbered update — the 19 mature issues (March 20, 2025 to February 8, 2026) shipped 59.5% of their hints, with 37.8% still open. The 5 most recent issues (all July 2026) shipped just 25%, with 75% open — because their update largely has not landed.

The honest reading sits in the middle: give a bulletin a full update cycle and roughly six in ten hints land — but even among mature issues, about 37.8% of hints never materialised at all. So a hint is a real signal, not a promise: most mature teases ship, a substantial minority quietly never do.

Share of each Blox Bulletin issue's hints that shipped, over time One bar per issue from #001 to #024. Bars left of the divider are mature issues (through #019); bars right of it are the 5 most recent issues, whose lower shipped share largely reflects that their update has not happened yet rather than inaccurate hints. 0% 50% 100% #001 #004 #007 #010 #013 #016 #019 #022 #024 recent — mostly unresolved mature issues (≤ #019) recent issues (5)
Percentage of each issue's hints that shipped, oldest (#001) to newest (#024). The recent cluster's low bars are dominated by open hints whose update has not arrived — read them as “not yet”, not “never”.

3. Delivery clusters around a few big updates

Hints do not trickle out evenly; they land in bursts when a major update ships. The single biggest was Update 27, which delivered 22 tracked hints — teases collected across issues dated May 23, 2025 through July 25, 2025. That is the shape of the release cadence: a run of bulletins seeds expectations, then one update clears much of the backlog at once.

Hints delivered by each Blox Fruits update, in delivery order Horizontal bars: for each update or event that delivered hints, the number of hints it delivered, ordered by the earliest contributing issue. Update 27 delivered the most at 22 hints. The dataset holds no update release dates, so bulletin-to-release lag is not computed; the issue-date span each update absorbed is shown instead. Update 26 2025-03 → 2025-05 15 Update 27 2025-05 → 2025-07 22 Update 28 2025-10 → 2025-10 3 Update 29 2025-12 → 2025-12 1 Update 30 2026-02 → 2026-02 4 Dog House event 2026-07 → 2026-07 3 Balance Patch 001 2026-07 → 2026-07 2 numbered update in-game event / patch
Hints delivered by each update or event, in delivery order, with the range of issue months whose hints it absorbed. The dataset records no update release dates, so exact bulletin-to-release lag is not shown — only the issue window each update cleared.

What this means for players

If you are reading a Blox Bulletin to decide what to hold, save, or grind for:

  • Trust the direction, not the timing. A hint is very unlikely to be outright false (1.1% contradicted), but roughly 37.8% of even mature teases never arrive — so “it was hinted” is not “it is coming”.
  • Do not act on a fresh hint as if it is confirmed. Recent issues sit mostly open until their update lands. Wait for the patch notes before you trade on a tease.
  • Value moves on release, not on the hint. For anything you are trading, watch the value list and grade the trade with the calculator; a bulletin tease is not yet a price mover. Our methodology explains how values and demand are set.

Limitations

This is one site's dataset over a limited period, and it should be read as such. Specifically:

  • Only 24 issues are covered (March 20, 2025 to July 31, 2026); 94 hints is a small sample, and single-issue rates swing a lot on a handful of hints.
  • Open is not the same as never shipping — some open hints will land in a future update, which will raise the shipped rate over time.
  • Status assignments are a judgement call for ambiguous hints; borderline cases were kept open, so the shipped figures are conservative rather than generous.
  • Some statuses rely on secondary sources (community patch-note write-ups) where official notes were thin.
  • No bulletin-to-release lag in days is reported, because update release dates are not part of the dataset.
  • Hints carry no theme or category field, so this report makes no claim about which kinds of hint ship more often — the data cannot support that split.

The underlying data

Every figure here traces back to the public issue pages. Browse the full record on the Blox Bulletin hub, or check individual issues — for example the fully-delivered #003, #004, #016, #019 (100% shipped), or issue #008, which holds the one contradicted hint. The value list and the methodology cover how the trade values referenced across the bulletins are set.