Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 51% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
5 measurements spanning 42 days, net -7. 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 508–517 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Sept 2026, 01:38
509
-3
1 Sept 2026, 07:06
512
-1
16 Aug 2026, 08:25
513
-2
7 Aug 2026, 19:15
515
-1
7 Aug 2026, 01:02
516
first reading
Engagement
20 posts held, back to 12 January 2024 — the 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 20 posts for this entry, the most recent from 5 April 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
236 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 43.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
103
43.6%
❤
55
23.3%
👍
38
16.1%
👏
29
12.3%
💯
3
1.27%
😁
2
0.847%
🤣
2
0.847%
✍
1
0.424%
🍾
1
0.424%
🎉
1
0.424%
🤝
1
0.424%
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 18 of the 20 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 236 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 January 2024 to 5 April 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.
If you need support with the Merge, please join Rujira’s official Telegram chat https://t.me/Rujira_Community
Make sure to only interact with team members and admins (with a tag in their name), and never answer to any DM's. None of the team members and admins will DM you first, so anyone who does is most likely a scammer.
All official updates, links, and announcements will come exclusively from the official Rujira…
The Merge is officially live! ⚡️
Use the link in the article for a step by step guide for every type of user
https://x.com/RujiraNetwork/status/1908565381314195865
Now that the merge is underway and the migration approved, all future announcemetns related to Rujira and the migration to $RUJI will be made via the Rujira Chat.
It's recommended that you join to stay abreast of all developments:
@team_kujira
Other Rujira communication channels are
X : https://x.com/TeamKujira
Discord : https://discord.com/invite/ddWCkJjD4u
Web : https://rujira.network/
The Gov prop considering the merge of Fuzion with the Rujira Alliance is live on the Dashboard. If you're staking $FUZN please go and cast your vote.
https://dashboard.fuzion.app/
If you know of a team exiting the bootstrapping phase and preparing to raise seed capital, please urge them to give this short intro to Ignition a read:
https://winkhub.app/posts/launching-with-ignition
https://x.com/Fuzion_App/status/1807703870094688500
Gov prop 4, regarding the unmigrated tokens, is live.
You can vote on the Govern Tab on https://dashboard.fuzion.app/
All the docs regarding the prop are linked in the prop description and the discussion is happening in the "Community Discussion 1 : Unmigrated Tokens" channel in our Discord.
The prop will be live for the standard 48 hours.
A community driven gov prop regarding the unmigrated tokens will be posted on May 2. All $FUZN stakers are encouraged to vote and be heard. The contents of the Prop can be viewed here:
https://t.co/nOhgpYoYfZ
The prop discussion is taking place on Discord.
Showing the 12 most recent of 20 posts we hold for @fuzion_announcements. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@fuzion_announcements named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@team_kujira named in 1 post, 8 August 2026 – 8 August 2026
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“Fuzion Announcements” (@fuzion_announcements), 509 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/fuzion_announcements.
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.