Channel
@tonushub
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,642subscribers
-25 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003168900117 |
|---|---|
| Type | Channel |
| Username | @tonushub |
| Created | Between 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/tonushub |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 58% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. They sit inside a group of 377 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @toncommunitychannel/118024 Apr 2026, 20:45 UTC | @tonushub/142 · this entry24 Apr 2026, 20:45 UTC | 1.00 | under a minute |
| @toncommunitychannel/118130 Apr 2026, 13:42 UTC | @tonushub/144 · this entry30 Apr 2026, 14:06 UTC | 1.00 | 24 minutes |
| @tonushub/151 · this entry11 May 2026, 19:33 UTC | @toncommunitychannel/118611 May 2026, 20:00 UTC | 1.00 | 27 minutes |
| @toncommunitychannel/118711 May 2026, 20:06 UTC | @tonushub/152 · this entry11 May 2026, 20:06 UTC | 1.00 | under a minute |
| @toncommunitychannel/119015 May 2026, 18:38 UTC | @tonushub/156 · this entry15 May 2026, 18:38 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @toncommunitychannel | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @toncommunitychannel (5–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 8 April 2026 to 15 May 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:03 | 2,642 | -12 |
| 9 Aug 2026, 18:12 | 2,654 | -12 |
| 6 Aug 2026, 14:26 | 2,666 | -1 |
| 6 Aug 2026, 05:19 | 2,667 | no change |
| 5 Aug 2026, 22:00 | 2,667 | first reading |
19 posts held, back to 8 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 19 posts for this entry, the most recent from 15 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
237 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 43.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 103 | 43.5% | |
| 🔥 | 55 | 23.2% | |
| 👍 | 49 | 20.7% | |
| 👏 | 20 | 8.44% | |
| 🥰 | 4 | 1.69% | |
| 👾 | 2 | 0.844% | |
| 🤝 | 2 | 0.844% | |
| 🫡 | 2 | 0.844% |
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 19 of the 19 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 237reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 8 April 2026 to 15 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
$100,400 just went to the 15 winners of the TON Consensus Challenge. 🧠 The smartest engineers on the planet — some armed with loyal AI sidekicks — helped us maximize the security of the new consensus mechanism. 🏆 Telegram contests offer generous prize money — and the only path to joining our engineering team.
❤10👍4🔥1
🕵️♂️ Now you can search 100M+ Telegram stickers and emoji by keyword — in 36 languages. Telegram’s AI scans and labels millions of public stickers so you can finally find the exact suspicious frog you need. 🤔
👍8❤2👾2🤝2
🌍 With 400 validators across 6 continents, TON is one of the most decentralized blockchain networks on the planet. 🧑💻 Telegram becoming the largest validator opened the door for major exchanges and custodians to stake TON without increasing centralization risk.
🔥6❤1
Introducing Acton — a new, modern toolchain for developing smart contracts on TON Acton covers the full development lifecycle: project creation, testing, debugging, dApp integration, deployment, and verification. CLI-first by design, it works naturally for both developers and AI agents. 1. One toolchain, not a bunch of utilities Create, build, test, lint, format, deploy, and verify TON contracts in a single cohere…
❤8
🛠 Developing for TON just became 10x faster. The new toolchain makes smart contracts easy to create, test, and deploy. Most importantly, fully AI-ready. It replaces TON’s fragmented tooling stack with one developer flow. Start building!
❤6🔥3👏2
🫴 TON is #1 in annual staking rewards among the 50 largest cryptocurrencies. And that’s on top of the coin’s price growth — which doubled over the past week.
❤5🔥2
🏁 TON leads Layer-1 blockchains in finality time. 🔗 Sources: https://telegra.ph/Comparison-of-Layer-1-blockchains-by-finalization-time-05-01
❤11
💎 Telegram becoming TON’s largest validator strengthens decentralization. ✅ It lets other major players join the validator pool without centralizing the network — with Telegram as the counterbalance. 📈 More and more TON gets locked in validation as everyone competes for 20%+ APR.
❤9🔥5👏4
⚡️ Fees in TON have dropped 6× — to nearly zero. Next step — Telegram replaces the TON Foundation as the driving force behind TON and becomes its largest validator. ⚙️ The focus shifts to tech superiority. 🧩 New ton.org, new dev tools, new performance upgrades. 🧭 Timeline — 2-3 weeks. 🪙 This is step 3 of 7 to Make TON Great Again.
👏11❤4
4 public TON dashboards worth watching right now: 🌸 TON Staking Staking yield recently spiked toward ~20% APY in TON terms after higher emission. Track validators, liquid staking, inflation and real yield. https://dune.com/ton_foundation/staking 🌻 Fragment TON’s core utility protocol: usernames, numbers, gifts. TVL matters, but real on-chain revenue matters more. https://dune.com/ton_foundation/fragment 🏦 TON on C…
❤13👏2🥰1
How MCP enables on-chain actions for agents on TON We publicly announced Agentic Wallets on TON — an open, self-custodial standard that lets agents manage assets through dedicated wallets. But just having a wallet isn’t enough. For an agent to use TON, it needs to be able to find and connect tools for interacting with the blockchain. That’s why we built mcp.ton.org — a simple entry point for connecting AI agents to…
👍6🫡2❤1🔥1
Voting by validators on reducing network fees has begun Validators, please participate in the vote. Follow the voting progress here.
❤6👏1🔥1
Showing the 12 most recent of 19 posts we hold for @tonushub. 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.
Citation-graph rank — 180,706 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 4 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“TON US Hub” (@tonushub), 2,642 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/tonushub.
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.