Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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
33 measurements spanning 50 days, net -11,624. 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 22,008–37,120 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
26 Sept 2026, 17:15
23,752
-1,359
17 Sept 2026, 12:38
25,111
-244
15 Sept 2026, 11:58
25,355
-418
13 Sept 2026, 19:54
25,773
-413
12 Sept 2026, 00:37
26,186
-615
9 Sept 2026, 14:36
26,801
-640
6 Sept 2026, 07:40
27,441
-855
4 Sept 2026, 01:57
28,296
-280
2 Sept 2026, 15:10
28,576
-374
1 Sept 2026, 12:08
28,950
-278
31 Aug 2026, 12:02
29,228
-129
30 Aug 2026, 13:15
29,357
-337
29 Aug 2026, 11:48
29,694
-356
28 Aug 2026, 11:17
30,050
-368
27 Aug 2026, 10:05
30,418
-232
26 Aug 2026, 07:33
30,650
-419
25 Aug 2026, 10:55
31,069
-384
24 Aug 2026, 09:37
31,453
-651
22 Aug 2026, 20:16
32,104
-682
21 Aug 2026, 06:55
32,786
first reading
Engagement
77 posts held, back to 23 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 64 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.19%
avg views ÷ 23,752 subscribers
Avg views / post
519
22 posts measured
Reaction rate
0.743%
reactions ÷ views · ER floor
Posts in window
22
of 77 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. It is computed over the 20 of 22 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 29 September 2026
Posts held
77 (23 July 2026 – 29 September 2026)
Views total
11,420
Reactions total
80
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Sept 2026, 07:52 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
213
Videos
23
Links
237
Lifetime counters from Telegram’s own channel header, read 30 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 10s
Average length
14s
Measured directly from 5 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
321 reactions across 69 posts, in 9 distinct kinds. The most used accounts for 49.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
160
49.8%
🔥
82
25.5%
💩
46
14.3%
👍
24
7.48%
👨💻
3
0.935%
🍌
2
0.623%
👏
2
0.623%
✍
1
0.312%
🥰
1
0.312%
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 70 of the 77 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 321 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 77 most recent posts we hold, published 23 July 2026 to 29 September 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.
🇰🇷 Seoul, Day 1.
GWDC 2026 KOREA is live — and DGrid AI is in the room.
Here to meet people, spark conversations, and share how a decentralized #AI smart network can actually work.✨
Find us on site.
Full post: https://x.com/dgrid_ai/status/2104753879967809563?s=46
⚡️More room to build with DGrid AI.
Premium users receive monthly credits to explore Claude, GPT, Gemini, and more. And when your ideas go further, your credits can too.
Join the @dgrid_ai Creator Rewards Program. Share how you use DGrid AI, publish your work, and submit it for review.
Once approved, you’ll receive Add-on Credits directly in your DGrid account.
Full post:
https://x.com/dgrid_ai/status/21044687614…
2/ How to Top Up Your DGrid Balance with $DGAI
✔️Log in to your DGrid account and open Billing from the account menu. dgrid.ai
✔️In the Deposit section, enter the amount you want to deposit and select $DGAI.
✔️Click Purchase and confirm the transaction in your wallet.
Your $DGAI deposit will be added to your #DGrid balance once the transaction is confirmed.
🚀 $DGAI is now powering new ways to access DGrid AI.
$DGAI deposits are now live on DGrid AI. Users can now top up their accounts with $DGAI on BNB Chain and use their balance across DGrid’s products and services.
This integration brings $DGAI closer to DGrid’s product layer, creating new ways for users to participate in the DGrid AI ecosystem and experience what it has to offer.
More utility. More possibilities. …
🚨 New models just dropped on DGrid. We keep shipping.
Two new options, two different bets:
🔸@claudeai Opus 5.5 — Fable 5.1-level on most tasks, 40% less than Opus 5. Stronger agentic coding, computer use, and knowledge work, with 30%+ faster output.
🔸@OpenAI GPT-6 Sol & Luna — Astra’s strengths at scale. Sol for complex coding and agents, Luna for high-volume work, both 50% cheaper than GPT-5.6 promo pricing.
Try t…
⚡️ @XiaomiMiMo V2.6 series is now on DGrid.
Frontier intelligence, all the modalities — Pro, Flash, and Pro UltraSpeed.
🔸 Pro: on par with Claude Opus 5 and GPT-5.6 Sol on most agent benchmarks; 46 on the AA Intelligence Index, highest among open-source models
🔸 Flash: same V2.6 generation, built for speed and cost
🔸 Pro UltraSpeed: Pro-level quality at up to 20× faster generation
Try them now:
https://x.com/dgrid…
🔥@typesafeai Jev 1.13 is available on DGrid.
TypeSafe’s flagship System One model. Built for routing, classification, scoring, and real-time automation. Multiple typed questions, one request, structured outputs your app can use directly.
Full post:
https://x.com/dgrid_ai/status/2102231668040040687
🔴 LIVE: @dgrid_ai AMA on Binance Square
Already 1.9K in the room. Questions + $500 red packets still open.
Join:
https://x.com/dgrid_ai/status/2102024718664777815
Tomorrow, we're taking the stage on Binance Square. 🎤
Our CEO is stepping up for an exclusive AMA with the DGrid AI community 👀
📅 Sept 21 | ⏰ 13:00 UTC
💰 $500 in red packets — come grab yours
🔥Bring your questions. Watch the showdown. See who comes out on top.
See you there. 👇
https://x.com/dgrid_ai/status/2101696615677657538?s=46
🔡 Points-to-$DGAI is now live on DGrid AI Arena.
→ https://dgrid.ai/arena?code=EL6FBK
The future of AI routing should not rely on static leaderboards alone.
It should be shaped by real performance, real tasks, and real human judgment.
In DGrid AI Arena, you compare blind battles between Model A and Model B, choosing the better output without knowing which AI is behind it.
Each vote becomes a real preference sign…
⚡️ $DGAI is now live on Binance Alpha!
A decentralized #AI smart network for cost-effective, reliable & verifiable AI.🚀
Full post:
https://x.com/dgrid_ai/status/2100133293278761074
https://x.com/BinanceWallet/status/2100132637553914364
🔥 DeepSeek-V4.1-Flash from is now on DGrid.
Smarter, faster, more efficient — the smallest model in DeepSeek’s new architecture family, with native visual understanding.
✅ 552B MoE, with just 8B active on input and 16B on output
✅ Native multimodal support
✅ Benchmark results ahead of flagship models, including DeepSeek-V4-Pro
✅ Smaller KV cache: 1/4 the HBM and 1/8 the SSD vs the previous generation
Full post:
htt…
🔥3
Showing the 12 most recent of 77 posts we hold for @dgrid_ai_ann. 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.
Posts edited after publishing
@dgrid_ai_ann edited 1 post 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
29 September 2026
Most recent edit
29 September 2026
Forward network
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.
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
@dgrid_ai_ann 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.
@openai named in 2 posts, 27 September 2026 – 30 September 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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“DGrid Announcement” (@dgrid_ai_ann), 23,752 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/dgrid_ai_ann.
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.