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 8 August 2026 and assigned it the closest of 31 fixed categories, at 72% 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 the other topics.
Growth
68 measurements spanning 103 days, net -24,071. 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 239,803–271,096 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 68
Measured (UTC)
Subscribers
Change
16 Nov 2026, 11:11
243,414
-752
13 Nov 2026, 01:38
244,166
-491
10 Nov 2026, 21:10
244,657
-317
9 Nov 2026, 05:50
244,974
-257
7 Nov 2026, 22:46
245,231
-244
6 Nov 2026, 21:57
245,475
-215
5 Nov 2026, 22:50
245,690
-176
5 Nov 2026, 01:46
245,866
-223
4 Nov 2026, 04:09
246,089
-203
3 Nov 2026, 02:11
246,292
-186
2 Nov 2026, 05:11
246,478
-209
1 Nov 2026, 06:36
246,687
-224
31 Oct 2026, 08:06
246,911
-199
30 Oct 2026, 11:40
247,110
-240
29 Oct 2026, 14:00
247,350
-316
28 Oct 2026, 10:46
247,666
-237
27 Oct 2026, 09:34
247,903
-235
26 Oct 2026, 10:38
248,138
-137
25 Oct 2026, 10:28
248,275
-161
24 Oct 2026, 11:50
248,436
first reading
Engagement
85 posts held, back to 13 July 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 209 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.865%
avg views ÷ 243,414 subscribers
Avg views / post
2,110
12 posts measured
Reaction rate
1.50%
reactions ÷ views · ER floor
Posts in window
12
of 85 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 12 November 2026
Posts held
85 (13 July 2026 – 12 November 2026)
Views total
25,260
Reactions total
380
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 14:27 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈1,170
Videos
≈6
Links
≈1,200
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
4m 06s
Average length
1m 02s
Measured directly from 4 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.
Reaction mix
2,538 reactions across 84 posts, in 17 distinct kinds. The most used accounts for 27.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
708
27.9%
👍
634
25.0%
🔥
418
16.5%
👏
186
7.33%
😁
119
4.69%
💩
113
4.45%
😢
61
2.40%
🏆
55
2.17%
🤯
55
2.17%
🤔
50
1.97%
🎉
40
1.58%
💯
40
1.58%
🍌
26
1.02%
🤬
14
0.552%
💔
10
0.394%
🤩
5
0.197%
👌
4
0.158%
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 85 of the 85 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 2,554 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 85 most recent posts we hold, published 13 July 2026 to 12 November 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.
Telegram Stars
Stars received
209
across the posts below
Posts paid on
41
of 85 we hold a reading for · 48%
Most on one post
102
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @thedailyton. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 85 most recent posts we hold for this entry, published 13 July 2026 to 12 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 1 of 12 posts held from the last 30 days (8.33%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
💀 Telegram Widgets still aren’t safe to use
⚫️ Just days after Durov announced Telegram Widgets, researchers from V12 demonstrated a vulnerability in the Android client. In the video, a user launches a bot and the widget then opens the calculator app on the phone by itself. The calculator was harmless, of course — but an attacker could potentially use the same vulnerability to execute other code on the device. Teleg…
🍌 JUST IN: Is Telegram building its own prediction market?
Today, Marat Kharrasov, whose early Telegram Wallet concepts we’ve covered before, transferred the @telemarkets username to Pavel Durov. The associated bot, @telemarkets_bot, previously featured the description: “Trade the future with TeleMarkets.”
All signs point to Telegram preparing its own Polymarket-style prediction market on TON. Interestingly, back i…
🍌 JUST IN: Tonnel Network launches a widget for betting on GRAM's price
Users can bet on whether GRAM's price will go up or down. Each round lasts two minutes, and bets can be placed in advance for the next one. Everything happens directly inside a Telegram message, with GRAM in your Money wallet required to place a bet.
Not surprising one of the first widgets with on-chain support had to be a gambling app.
@theda…
🐤 Could Telegram widgets spark the next Notcoin?
⚫️ Telegram recently introduced widgets — small interactive interfaces that run directly inside messages. Pavel Durov showcased the new feature on his personal channel, demonstrating everything from weather forecasts and shopping for electronics to simple games. There are some significant limitations, though: widget code must fit within just 4 KB when compressed, and …
🐤 Telegram Gifts now have perps
⚫️ While DeFi on TON is going through a rough patch, Telegram Gifts remain one of the few markets in the ecosystem that still feels genuinely active. Interest picked up again in October after upgrades launched for Resistance Dog, but so far, nobody has really managed to bring that activity into TON DeFi.
⚫️ There have been attempts before. Some projects tried tokenizing Gifts into tr…
🍌 JUST IN: Telegram is testing a full-fledged AI agent harness
⚫️ Back in late October, we showed what Telegram’s planned AI integration could look like through a dedicated chat — at least, that was the functionality found in one of the beta builds at the time. But Telegram’s AI experiments apparently go much further. A macOS client developer is now testing a full-fledged AI agent harness — a system that lets an AI …
📒 Where is Telegram actually heading?
⚫️ If you’ve been following the latest Telegram betas, you’ve probably noticed just how many new features keep showing up. In the past few weeks alone, we’ve seen a recommendation feed based on user interests, interactive widgets with Gram Wallet support, and most recently, built-in AI agents. The feature list keeps growing — but what is Telegram actually trying to build toward?…
💀 Who will take responsibility for the Affluent hack?
⚫️ Almost two weeks ago, around $1 million was drained from the DeFi protocol Affluent in an exploit. Yet affected users are still waiting for a public explanation. Today, sd, the creator of @ghwnd, called on the community to draw more attention to the incident and push the Affluent team for answers. He had previously published a detailed onchain investigation in…
📒 Fix Telegram yourself
⚫️ Last Friday, we wrote about how deeply Telegram has embraced vibe coding. Comments from developer Mike (@vihor), who said that AI now writes almost all of Telegram’s code, quickly spread across the internet. The reaction was mixed: users pointed to Telegram’s increasingly frequent bugs and blamed at least some of them on vibe coding.
⚫️ Meanwhile, alongside its latest update, Telegram fin…
💡 Telegram is going all-in on AI
⚫️ In the latest Telegram beta for macOS, traces of a built-in AI agent were found — we already showed it in action on video earlier today. The feature is still hidden, and it’s unclear whether it will make it into the stable release. Interestingly, Cocoon was not mentioned among the available AI providers.
⚫️ Built-in AI agents are also starting to appear in other services inside T…
🍌 JUST IN: What Telegram’s built-in AI agent may look like
Users will be able to connect a third-party AI provider — such as ChatGPT, Claude, Grok, or OpenRouter — via an API key and chat with the model in a separate conversation with @agent.
For now, the feature is hidden in the Telegram beta for macOS and disabled by default. The demo uses test data, and the way the feature works may still change before release.
…
🍌 JUST IN: The intern behind Telegram’s X account asked “TON trenchers” to drop their Telegram usernames
Notably, this is the first time Telegram’s account has addressed traders within the TON ecosystem this directly.
As a reminder, the previous attempt didn’t go too well — this summer, the account’s author shared his TON wallet, received memecoins from the community, and then sold almost all of them.
@thedailyton
😁10❤5🏆4🍌2👍2💩1🤔1
Showing the 12 most recent of 85 posts we hold for @thedailyton. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@thedailyton edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
18 September 2026
Most recent edit
10 October 2026
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
Named by 45 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Handles this channel named that no longer answer
Dead references
2
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
2
vacant every time we have ever looked
@thedailyton named 2 handles 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.
@telemarkets named in 3 posts, 14 November 2026 – 17 November 2026
@agent named in 1 post, 24 October 2026 – 24 October 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 10 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Ton Post @tonpost · 68,688 Telegram ranks this channel #1 of 89 here — alongside 88 others — read 19 August 2026
TON Dev News @tondev_news · 40,394 Telegram ranks this channel #2 of 87 here — alongside 86 others — read 29 August 2026
Orbs Announcements 🌐 @OrbsAnnouncements · 72,058 Telegram ranks this channel #2 of 88 here — alongside 87 others — read 19 August 2026
GRAM Content English @TONContentEnglish · 506,058 Telegram ranks this channel #3 of 91 here — alongside 90 others — read 23 August 2026
TON Diamonds NFT @tondiamonds · 127,568 Telegram ranks this channel #3 of 89 here — alongside 88 others — read 13 August 2026
xRocket News @xrocketnews · 217,493 Telegram ranks this channel #3 of 82 here — alongside 81 others — read 11 August 2026
CashFlow‘s Calls @CashFlowsCalls · 458,198 Telegram ranks this channel #3 of 88 here — alongside 87 others — read 9 August 2026
TON Jobs @tonhunt · 62,711 Telegram ranks this channel #4 of 92 here — alongside 91 others — read 21 August 2026
TON Status @tonstatus · 150,770 Telegram ranks this channel #4 of 88 here — alongside 87 others — read 12 August 2026
Battles @battlesjam · 368,826 Telegram ranks this channel #4 of 86 here — alongside 85 others — read 10 August 2026
TonDreamer Eng @TonDreamerEng · 649,785 Telegram ranks this channel #4 of 88 here — alongside 87 others — read 8 August 2026
TON Tech @tontech · 23,396 Telegram ranks this channel #5 of 49 here — alongside 48 others — read 16 September 2026
Tonnel Network @tonnel_en · 169,856 Telegram ranks this channel #6 of 80 here — alongside 79 others — read 30 August 2026
Блокчейн Барышня @blockchain_baryshnya · 21,974 Telegram ranks this channel #7 of 75 here — alongside 74 others — read 11 September 2026
bemo | TON Staking | Liquid Staking | bmTON @bemofinance · 26,872 Telegram ranks this channel #8 of 88 here — alongside 87 others — read 9 September 2026
ULTRADE Announcements @ULTRADE_Announcement · 29,222 Telegram ranks this channel #8 of 82 here — alongside 81 others — read 6 September 2026
Fasttoken News @fasttoken_news · 118,705 Telegram ranks this channel #8 of 87 here — alongside 86 others — read 13 August 2026
The Shadow Order @theshadoworder · 272,257 Telegram ranks this channel #8 of 88 here — alongside 87 others — read 11 August 2026
Investment kingyru 💎 EN @investkingyru_en · 18,901 Telegram ranks this channel #9 of 80 here — alongside 79 others — read 30 September 2026
Kirill Malev @kirill_malev · 22,933 Telegram ranks this channel #9 of 81 here — alongside 80 others — read 17 September 2026
Alphas n Betas @alphasnbetas · 42,194 Telegram ranks this channel #10 of 79 here — alongside 78 others — read 3 October 2026
Anatoly Makosov @anatoly_makosov · 39,901 Telegram ranks this channel #10 of 81 here — alongside 80 others — read 28 August 2026
Forward Protocol @ForwardProtocol · 43,561 Telegram ranks this channel #10 of 80 here — alongside 79 others — read 27 August 2026
<\> Sharding, TON's, two Jetons </>. @ton2keng · 537,504 Telegram ranks this channel #10 of 89 here — alongside 88 others — read 17 August 2026
This channel appears in 64 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“The Daily TON | News” (@thedailyton), 243,414 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/thedailyton.
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.