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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
63 measurements spanning 95 days, net -809. 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 10,784–11,835 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)
Subscribers
Change
10 Nov 2026, 09:06
10,905
-9
8 Nov 2026, 20:28
10,914
-3
7 Nov 2026, 11:00
10,917
-6
6 Nov 2026, 11:35
10,923
-8
5 Nov 2026, 09:06
10,931
-12
4 Nov 2026, 10:49
10,943
-15
3 Nov 2026, 07:54
10,958
-12
2 Nov 2026, 09:36
10,970
-6
1 Nov 2026, 11:57
10,976
-5
31 Oct 2026, 10:50
10,981
-5
30 Oct 2026, 08:06
10,986
-5
29 Oct 2026, 05:28
10,991
-4
28 Oct 2026, 06:31
10,995
-4
27 Oct 2026, 07:56
10,999
-8
26 Oct 2026, 07:56
11,007
-6
25 Oct 2026, 08:05
11,013
-4
24 Oct 2026, 07:16
11,017
-12
23 Oct 2026, 07:44
11,029
-8
22 Oct 2026, 11:00
11,037
-4
21 Oct 2026, 02:37
11,041
first reading
Engagement
43 posts held, back to 25 June 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 61 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
21.9%
avg views ÷ 10,905 subscribers
Avg views / post
2,380
7 posts measured
Reaction rate
3.15%
reactions ÷ views · ER floor
Posts in window
7
of 43 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 4 November 2026
Posts held
43 (25 June 2026 – 4 November 2026)
Views total
16,680
Reactions total
526
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 09:56 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
96
Links
98
Lifetime counters from Telegram’s own channel header, read 11 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.
Reaction mix
3,534 reactions across 43 posts, in 12 distinct kinds. The most used accounts for 25.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
908
25.7%
👍
738
20.9%
🔥
715
20.2%
🎉
237
6.71%
❤🔥
191
5.40%
👏
183
5.18%
💯
143
4.05%
🤩
142
4.02%
😍
141
3.99%
🥰
118
3.34%
😁
17
0.481%
🤯
1
0.028%
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 43 of the 43 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 3,534 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 43 most recent posts we hold, published 25 June 2026 to 4 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: 1 of 7 posts held from the last 30 days (14.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).
Earn $5 for every qualified referral 🇺🇸🇨🇦
Hive Calls now pays a $5 referral reward when you invite a new eligible user from the US or Canada.
To qualify:
🔵You must be based in the US or Canada
🔵Your invited user must also be based in the US or Canada
🔵They need to complete 60 minutes of approved Hive Calls
🔵Once those minutes are reviewed and approved, you receive $5
Invite people you know, help them get started, …
Hive Calls now works beyond the app 📞🐝
You can now start a call in Hive Calls and invite someone to join directly from their browser using a link.
They don’t need to install Hive Calls first. Just send the link, they open it on the web, and you can start talking.
One important note: participants who join through the web do not earn points. Points are available only to eligible users participating through the Hive C…
We’re looking for Hive Calls users in the US 🇺🇸
Call friends, earn rewards, and help improve AI voice technology. Conversations are recorded with both participants’ consent.
👉 Join here: https://dhive.app
Some users were unable to withdraw their earned USDC due to an issue on a third-party provider's side.
The problem has now been resolved, and withdrawals are working normally.
We apologize for the inconvenience and appreciate your patience ❤️🐝
🐝 DataHive AI keeps delivering strong Vote Rank results on 🪙 Solana.
We're now part of ⚙️ Shinobi Performance Pool, where validators earn their place through performance.
Stake SOL with DataHive AI and earn staking rewards!
🐝 Install Hive Calls. Complete the quest. Become a Buzzer!
Our Hive Calls quest is live on Galxe! Complete it to unlock the Buzzer role in the DataHive Discord.
How to participate:
1. Open the quest on Galxe.
2. Install Hive Calls on Android or iPhone and connect your DataHive account.
3. Complete the quest tasks and claim your Buzzer role.
📞 Keep talking, earn points together
Invite a friend and call each other …
Ukrainian Mission Payouts Are Ready 🇺🇦
If you completed one of our Ukrainian paid missions, approved earnings are now available for withdrawal in your DataHive AI Wallet.
You can choose between:
🔵USDC — sent directly to your crypto wallet
🔵Tremendous — with payout options available for supported countries and locations
Important information about Tremendous
If you are currently located in Ukraine, we strongly reco…
Hive Calls is now available on iOS! 🍎📞
Download the app, call your friends, have real conversations, and earn points together.
Now available on the App Store:
https://apps.apple.com/us/app/hive-calls/id6812719492
A quick note to the DataHive community 🐝
We’re continuing to build real speech and conversation datasets, expanding Hive Calls, and preparing more ways for contributors to earn through actual data work.
That includes more paid missions in USD, new languages, and language-specific dialogue tasks inside Hive Calls.
Hive Calls for iOS is also coming very soon, opening the app to even more users and conversations.
Ke…
Thank you for all the conversations you’ve been having through Hive Calls. 🐝📞
One small update: starting from now, calls focused mainly on Hive Calls, DataHive, points, rewards, or how to earn may no longer be eligible, because these topics are less useful for the real-world conversational datasets AI companies are looking for.
Don’t worry — calls you’ve already completed before this update can still be eligible.
…
Romanian & Hungarian Mission Payouts Are Ready 💰
If you completed one of our Romanian or Hungarian paid missions, your submission may now be approved and ready for withdrawal.
Log in to your DataHive AI dashboard, open your Wallet, and check your available balance.
You can now cash out using:
🔵Tremendous — choose from available payout options in your country, such as gift cards, prepaid cards, PayPal, bank transfer…
What Makes a Call Eligible? 📞
For a Hive Call to qualify, it should meet a few simple requirements:
• Two real people must join the call
An eligible call is a conversation between two different participants.
• Both people should actively participate
The call should include a real back-and-forth dialogue, not one person doing all the talking.
• The conversation should be meaningful
You can talk naturally, but the dia…
🔥26❤18👍13🎉9👏8
Showing the 12 most recent of 43 posts we hold for @DataHiveAI. 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.
Mentions
Named by 2 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.
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.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“DataHive AI” (@DataHiveAI), 10,905 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/DataHiveAI.
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.