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 the other topics.
Growth
64 measurements spanning 97 days, net -12,998. 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 20,428–37,326 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)
Subscribers
Change
12 Nov 2026, 20:39
22,378
-18
10 Nov 2026, 17:41
22,396
-14
9 Nov 2026, 07:44
22,410
-9
7 Nov 2026, 20:01
22,419
-17
6 Nov 2026, 20:59
22,436
-5
5 Nov 2026, 22:56
22,441
-12
5 Nov 2026, 02:09
22,453
-6
4 Nov 2026, 05:16
22,459
-11
3 Nov 2026, 05:16
22,470
-4
2 Nov 2026, 05:50
22,474
-95
1 Nov 2026, 07:04
22,569
-107
31 Oct 2026, 10:11
22,676
-12
30 Oct 2026, 07:55
22,688
-12
29 Oct 2026, 04:28
22,700
-14
27 Oct 2026, 23:40
22,714
-35
26 Oct 2026, 21:09
22,749
-44
26 Oct 2026, 00:04
22,793
-25
24 Oct 2026, 22:01
22,818
-22
23 Oct 2026, 21:06
22,840
-6
23 Oct 2026, 00:37
22,846
first reading
Engagement
105 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 119 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.30%
avg views ÷ 22,378 subscribers
Avg views / post
291
15 posts measured
Reaction rate
0.782%
reactions ÷ views · ER floor
Posts in window
15
of 105 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 11 of 15 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 14 November 2026
Posts held
105 (23 July 2026 – 14 November 2026)
Views total
4,372
Reactions total
23
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
16 Nov 2026, 03:29 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
241
Videos
23
Links
265
Lifetime counters from Telegram’s own channel header, read 16 November 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
368 reactions across 89 posts, in 12 distinct kinds. The most used accounts for 51.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
188
51.1%
🔥
91
24.7%
💩
46
12.5%
👍
27
7.34%
🥰
4
1.09%
👏
3
0.815%
👨💻
3
0.815%
🍌
2
0.543%
✍
1
0.272%
👎
1
0.272%
😁
1
0.272%
🤡
1
0.272%
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 91 of the 105 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 368 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 105 most recent posts we hold, published 23 July 2026 to 14 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.
Recent posts
Telegram’s own ‘edited’ marker: 2 of 15 posts held from the last 30 days (13.3%) 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).
🚨Gemini 4 Hydrogen is already available on DGrid AI.
@Google's model for everyday coding and agentic work — fast, efficient, and strong enough to stand on its own.
🔸 2.5X faster than 3.8 Flash
🔸 Four thinking levels (low / medium / high / xhigh) 🔸 Surpasses Argon on the Artificial Analysis Intelligence Index at high thinking
Try it now:
https://x.com/dgrid_ai/status/2121553103153725878
📣 $DGAI STAKING UPDATE: NEW 360-DAY PLAN AT 80% APY
An update to DGrid’s 360-day staking plans will take effect on Monday, Nov 16 at 08:00 (UTC). From that time, the 90% APY plan will no longer accept new stakes. A new 360-day plan at 80% APY will be introduced.🆕
Existing stakes in the 90% APY plan will remain unchanged and continue earning rewards under their original terms. Only new participation in the 90% plan …
📊 Introducing DGrid Model Rankings: A searchable leaderboard to help you find the right model for your needs from multiple dimensions.👇
One overall ranking can’t answer every model-selection question. #DGrid Model Rankings brings together practical signals to help you compare models and make a more informed choice.
✅ Category leaders: Top 3 DGrid-supported models in each task category
✅ Capability profiles: Compare…
💡Gemini 4 Carbon just dropped on DGrid AI.
@Google’s strongest model — for the problems that push past Argon.
🔹 Built for long-horizon and multi-step reasoning
🔹 Checks its code and the screen as it builds, from complete apps to 3D worlds
🔹 Flags missing or flawed data instead of guessing
🔹 Same intro pricing as Argon: $2 / $10 per 1M tokens
Try it now:
https://x.com/dgrid_ai/status/2120721719292039475
🎉 Excited to team up with @Didotxyz_!
Built on a crypto-native model, DI's AI + crypto intelligence ecosystem connects market data, event research, quant products and interoperable agents. ⚡️
DGrid'll support DI’s Agent Network with an efficient, low-cost #AI API for model access and verifiable inference.
Full post:
https://x.com/dgrid_ai/status/2120063922711507374
⚡️Claude Fable 5.2 from @claudeai is now on DGrid AI.
Built for the most ambitious technical work. A step above Opus 5.5 on nearly every capability Anthropic tested, and up to 30% faster than Fable 5.1.
🔸 Improvements in coding, reasoning, and vision
🔸 Clearer communication than previous Fable models
🔸 On FrontierCode 2.0, High effort matches Opus 5.5 Max at roughly half the cost per task
Try it now:
https://x.com/…
📢 Announcement: DGrid AI Arena Cracks Down on Bulk Registration and Abusive Activity
At its core, DGrid AI Arena was created to collect authentic human preference data on AI content and applications. These insights help us continuously improve our AI products and infrastructure while contributing to the development of a more user-driven AI ecosystem.
To thank community members who participate consistently and contr…
🚨 AI is booming, but trust remains a core issue — users still can’t easily verify they’re getting the model and quality they were promised.
🫡 Anthropic’s FlashProve is an important step toward verifiable AI, cryptographically proving that a response came from the claimed model.
In multi-model, multi-provider environments, we take a complementary path with PoQ(Proof of Quality): multi-dimensional quality assessment …
✨New image models from @OpenAI just landed on DGrid AI.
GPT-Image-2.6 Flare and Sunburst — 50% faster generation overall.
🔸 Flare generates images in as little as six seconds
🔸 Sunburst delivers higher quality and better consistency across edits
Image markup and SVG exports also included.
Try them now:
https://x.com/dgrid_ai/status/2118606012991336451
💡 Our sixth paper is out!
FIDES-Live: Evaluating Behavioral Concordance in Sequential Trading Agents A
n AI trading agent can submit a valid order, have it rejected, and still report that the trade was completed. A correct account balance alone would not reveal this discrepancy.
In this paper, we examine whether an agent’s decisions, proposed orders, execution outcomes, and subsequent reports agree with one anothe…
🚨DGrid Model Marketplace Now Processes 60B Tokens and 2M+ API Calls Every Day
A shared achievement for everyone building with us.🥳
DGrid Model Marketplace now handles production-scale AI workloads every day. Behind these numbers are providers making their models available, developers building them into products, and #AI Agents running real tasks around the clock.
🔸2M+ API calls per day
🔸60B tokens processed per da…
Claude Code × DGrid #AI Gateway ⚡️
From your #DGrid API key to your first successful response—every step, documented. Our integration guide covers CLI and desktop setup, with configuration examples and troubleshooting along the way.
👇Connect your workflow.
https://x.com/dgrid_ai/status/2117531743557447973
👍1
Showing the 12 most recent of 105 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
3
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
3
vacant every time we have ever looked
@dgrid_ai_ann named 3 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.
@openai named in 10 posts, 27 September 2026 – 15 November 2026
@didotxyz_ named in 4 posts, 11 November 2026 – 15 November 2026
@token2049 named in 4 posts, 9 October 2026 – 13 October 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 12 November 2026 — this
entry's latest reading, not the date you are reading this.
“DGrid Announcement” (@dgrid_ai_ann), 22,378 subscribers as measured 12 November 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.