Telegram RegisterThe public register of Telegram
Telegram profile photo for Blox Fruits • News | ENG

Channel

Blox Fruits • News | ENG

@BloxFruitsEU

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

84subscribers

-5 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002108752349
TypeChannel
Username@BloxFruitsEU
Created12 November 2023measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live4 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/BloxFruitsEU

Growth

848986.514 August 2026 — 89 subscribers14 August 2026 — 89 subscribers28 August 2026 — 87 subscribers4 September 2026 — 84 subscribers14 August 20264 September 2026
4 measurements spanning 21 days, net -5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 83–90 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 11:2284-3
28 Aug 2026, 17:0887-2
14 Aug 2026, 16:4589no change
14 Aug 2026, 16:3289first reading

Engagement

12 posts held, back to 12 November 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 4 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
33s
Average length
33s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

176 reactions across 10 posts, in 13 distinct kinds. The most used accounts for 38.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6838.6%
👎5330.1%
🤡169.09%
137.39%
🗿95.11%
🔥42.27%
💩31.70%
🤮31.70%
🕊21.14%
😁21.14%
🍌10.568%
🍓10.568%
👌10.568%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 12 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 176 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 12 November 2023 to 4 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Sept 2025, 05:17 UTC≈1,340 views93 reactionsread 14 August 2026

Yo. Should I keep developing this channel, or do you no longer need it? 👍 - yes 👎 - no

👎49👍39🤡5

10 May 2025, 15:02 UTC≈2,750 views23 reactionsread 14 August 2026
Photo

📣 The first works on Creation Build Submission are here! ℹ️ The players started publishing their buildings for the competition, and here is one of the first ones with the inscription: “I❤️ Blox” ❓ Are you feeling inspired already? ❗️ You can try yourself in the competition by following the link: 📩 Form for the sale of work BF News 📰 RU Channel 🇪🇺 BF Shop 🛍 Cheap Robux 💵

👍12🤡63🍌1👎1

8 May 2025, 02:56 UTC≈2,460 views20 reactionsread 14 August 2026
Photo

📢 New leaks of the upcoming update! ℹ️ One of the developers of Blox Fruits, Shafi_dev (responsible for fruits), shared a small sneak peak. The image shows a black and white tornado. ❗️ The community has already come up with several versions of what it could be: - a rework of Blizzard fruit — new Tornado fruit — Fruit Control rework — rework of the Smoke fruit ❓ What do you think? Blox Fruits News. RU Channel

👍8🤡3🤮3💩2🔥21👌1

13 Apr 2025, 07:31 UTC≈2,340 viewsread 14 August 2026
Poll

What’s your opinion about “Update 26”?

  1. Very good update! I’m hyped!!!75%
  2. I think update is going to be boring…25%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

24 Mar 2025, 18:21 UTC≈2,690 views16 reactionsread 14 August 2026
Photo

📣 Two more community theories! ℹ️ We found two new Bulletin interpretations from players, both involving Gravity Fruit and Falcon Fruit. 🤔 But do they make sense? 🔠 Gravity Fruit – Its rework is already officially confirmed, so including it in the bulletin breakdown seems unnecessary. 🔠 Falcon Fruit – This one's trickier. We know it might get an update (according to this post), but the hidden fruits in the bulletin

5👎3🕊2🤡2👍1💩1🔥1😁1

24 Mar 2025, 18:20 UTC≈1,760 views1 reactionsread 14 August 2026
Photo

📣 Gravity Fruit rework — it's official! ❗️ A new video just dropped on Uzoth's channel: Watch here ℹ️ In the video, he breaks down the Gravity Fruit rework, showcases its new model, and goes over Bulletin #001 from the devs. Go check it out! Blox Fruits News. RU Channel

👍1

24 Mar 2025, 18:19 UTC≈1,560 views1 reactionsread 14 August 2026
Photo

📣 Yo, will there be a Fourth Sea in the game? 💡 In Bulletin #001, the devs dropped a Q&A section with some spicy details. 🔥 One of the questions was: Q: Will there ever be a Fourth Sea in the game? Mr. 43: "Not right now! Before even thinking about a new sea, we wanna polish, balance, and perfect the existing ones. Any major expansion needs a solid foundation!" ✅ So yeah, Fourth Sea ain’t in the plans yet, but the

👍1

21 Mar 2025, 10:10 UTC≈1,270 views4 reactionsread 14 August 2026
Photo

📣 New Fruits & Reworks Coming in the Next Blox Fruits Update! ℹ️ The Bulletin #001 featured a Q&A section with the developers, where they shared some exciting details. ❗️ One of the questions was: Q: Which Blox Fruits will be added or reworked in this update? Indra: "If you've been keeping up with the news... you probably already know. And yes, we hear you about the Control rework, but that's a topic for another da

🍓1👍1🗿1😁1

21 Mar 2025, 10:09 UTC≈1,050 views3 reactionsread 14 August 2026
Photo

📣 The Blox Fruits Bulletin #001 ❗️ Today, the official Blox Fruits X account posted about the brand-new Blox Fruits Bulletin Board! ℹ️ The first issue, Bulletin #001, covers three major topics: • Gravity Rework — "TURTLE ISLAND UNDER SIEGE BY FALLING STARS?!" • Fruit Showdown — "POACHERS GET DEFEATED" • Why the Dragon Update Took So Long — "THE LONG ROAD TO DRAGON: WHY THE UPDATE TOOK SO LONG" ✅ The next bulletin

🗿2👍1

19 Mar 2025, 04:02 UTC852 views7 reactionsread 14 August 2026
Video

📣 Artificial Intelligence in Roblox? ℹ️ Roblox has introduced a new API — Text Generation API, which will allow place creators to generate AI-powered dialogues. ❗️ Sounds really exciting! Can’t wait to test this feature in Blox Fruits! Blox Fruits News. RU Channel

4👍2🔥1

18 Mar 2025, 11:21 UTC817 views8 reactionsread 14 August 2026
Photo

📣 New message from mygame43! ❗️ A new message from one of the main developers of the game appeared on the Blox Fruits Discord channel today .: Hello everyone After the release of the Dragon update, we had to reconsider our plans for future updates. We don't want players to wait a whole year for a new update — it's not fair. Therefore, we decided to change the approach and expand the team by adding new fruit designer

🗿6👍2

Showing the 12 most recent of 12 posts we hold for @BloxFruitsEU. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

13 Apr 2025, 07:31 UTCAnonymous Poll211 voters

What’s your opinion about “Update 26”?

  1. Very good update! I’m hyped!!!75%
  2. I think update is going to be boring…25%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 12 most recent posts we hold, published 12 November 2023 to 4 September 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 4 September 2026 — this entry's latest reading, not the date you are reading this.

“Blox Fruits • News | ENG” (@BloxFruitsEU), 84 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/BloxFruitsEU.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.