Other / unclassifiable — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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
37 measurements spanning 63 days, net +12,080. 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 13,086–28,790 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 37
Measured (UTC)
Subscribers
Change
9 Nov 2026, 09:18
26,978
+503
7 Nov 2026, 21:47
26,475
+339
6 Nov 2026, 21:19
26,136
+62
5 Nov 2026, 23:36
26,074
+21
4 Nov 2026, 21:17
26,053
-17
3 Nov 2026, 19:47
26,070
+71
2 Nov 2026, 20:45
25,999
+65
1 Nov 2026, 21:39
25,934
+67
31 Oct 2026, 18:40
25,867
+64
30 Oct 2026, 18:56
25,803
+72
29 Oct 2026, 18:57
25,731
+58
28 Oct 2026, 22:21
25,673
+152
27 Oct 2026, 21:01
25,521
+94
26 Oct 2026, 21:26
25,427
+166
25 Oct 2026, 21:06
25,261
+359
24 Oct 2026, 20:07
24,902
+227
23 Oct 2026, 22:05
24,675
+211
23 Oct 2026, 00:57
24,464
+157
22 Oct 2026, 00:36
24,307
+345
20 Oct 2026, 18:51
23,962
first reading
Engagement
17 posts held, back to 19 March 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 50 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
59.8%
avg views ÷ 26,978 subscribers
Avg views / post
16,100
3 posts measured
Reaction rate
0.61%
reactions ÷ views · ER floor
Posts in window
3
of 17 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 3 November 2026
Posts held
17 (19 March 2026 – 3 November 2026)
Views total
48,360
Reactions total
295
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Nov 2026, 20:16 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
3
Videos
4
Lifetime counters from Telegram’s own channel header, read 9 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
10m 13s
Average length
2m 33s
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
1,883 reactions across 16 posts, in 23 distinct kinds. The most used accounts for 43.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
822
43.7%
👎
425
22.6%
🤬
220
11.7%
👍
95
5.05%
🖕
83
4.41%
🥰
30
1.59%
👏
29
1.54%
🔥
27
1.43%
😁
25
1.33%
😭
20
1.06%
🤔
20
1.06%
😢
18
0.956%
💩
12
0.637%
🍌
11
0.584%
🤡
11
0.584%
🙏
8
0.425%
💯
7
0.372%
🏆
6
0.319%
😡
6
0.319%
🐳
3
0.159%
3 further kinds
5
0.266%
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 16 of the 17 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 1,883 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 19 March 2026 to 3 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: 0 of 3 posts held from the last 30 days (0%) 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).
【Dhan Pay Important Notice ⚠️】
BharatPe Business has been updated today 📢. Please re-bind your BharatPe Business account on the Dhan Pay dashboard 🔗.
Failure to re-bind in time will cause withdrawal errors ❌. Kindly complete the operation as soon as possible ⏳ to avoid disruption to your fund withdrawal 💰
📢 Platform Supported Wallets Announcement
Dear Users,
To provide you with a faster and more convenient experience, our platform supports the following business payment wallets:
✅ Google Pay Business
✅ Paytm Business
✅ PhonePe Business
⚡️ Fast & Convenient Payments!
If you haven't activated any of these business wallets yet, please contact your agent for assistance with the setup process.
Thank you for your continued …
📢 Dhan Pay Platform Update Completed
Dear Dhan Pay Users,
We are pleased to announce that the latest platform update has been successfully completed! 🎉
Thank you for your patience and continued support.
Please log in to your account and continue using the platform as usual.
If you encounter any issues or need assistance, please contact our customer support team.
🙏 Thank you for being part of Dhan Pay!
Dhan Pay Team
⚠️【Dhan Pay Important Notice】
🔔 Paytm service has been upgraded.
Please uninstall the existing Paytm App on your mobile. Download the Dhan Pay custom Paytm and complete binding.
✅ You need to re-bind your Paytm wallet on Dhan Pay platform.
❗If you do not re-bind, you will face payment & withdrawal issues: failed transactions, stuck orders etc.
⏰ Kindly complete this at the earliest to keep your fund operations runni…
📢 Business Wallet Limit Increase Assistance
Are you using Paytm Business or BharatPe Business and finding your current wallet limits insufficient for your business needs?
Our platform can provide assistance with wallet limit increase requests through designated personnel.
✅ Support for Paytm Business
✅ Support for BharatPe Business
✅ Assistance with wallet limit inquiries
If you need help increasing your wallet limit…
📢 Dhan Pay Platform Upgrade Successfully Completed!
🚀 The Dhan Pay platform has completed its comprehensive upgrade, bringing you a smoother and better working experience!
⚡️ Fast Withdrawals – Enjoy a faster and smoother withdrawal process.
💎 Instant Points Credit – Points are credited instantly.
📦 Plenty of Orders Available – More order opportunities to keep you active.
🌟 Better Experience, Greater Efficiency!
Than…
📢 Dhan Pay Platform Upgrade Successfully Completed!
After comprehensive system optimization and technical upgrades, the Dhan Pay platform has now completed its full update.
✨ Smoother withdrawal process
⚡️ Faster withdrawal speed
🌐 More stable system performance
💎 Better overall user experience
✅ Plenty of‑tasks available, no need to rush to grab them
✅ Bind your Google Business and Paytm Business wallets to get th…
📢 Dhan Pay Platform Update
Dear users,
The Dhan Pay platform issue has been successfully resolved. All services are now operating normally.
Thank you for your patience and support. You can continue using the platform as usual.
If you experience any issues, please contact our support team.
📢 USDT Points Recharge & Priority Service Announcement
Dear users, you can now use USDT to purchase points quickly and conveniently.
💎 Points Exchange Rate:
1 USDT = 109 Points
💰 Binance USDT Purchase Rate:
1 USDT ≈ 103 INR
(Users can purchase USDT through Binance for a convenient recharge experience.)
🚀 Recommended Network:
For faster transactions and lower fees, we recommend using the BEP20 network.
⚡️ Network Fee:…
📢 USDT Points Recharge Announcement
You can use USDT to purchase points.
💎 Exchange Rate: 1 USDT = 109 Points
For faster and more cost-effective transfers, we recommend using the BEP20 network.
⚡️ Network fee as low as 0.1 USDT
Choose BEP20 for a smoother and more economical recharge experience.
📢 Binance USDT Purchase Tutorial
The USDT purchase tutorial video is now available.
Please watch the video and follow the steps to complete your USDT purchase.
For any questions, please contact us.
📢 Binance Registration Tutorial
The Binance registration tutorial video is now available.
Please watch the video and follow the steps to complete your account registration.
If you have any questions, feel free to contact us.
❤14🤬14
Signed VIP8
Showing the 12 most recent of 17 posts we hold for @dhan_pay. 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 recorded as deleted after publishing
We recorded 1 post on @dhan_pay as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
7 October 2026
Most recent seen missing
7 October 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
0
Mentions
Named by 1 registered channel — 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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“Dhan Official” (@dhan_pay), 26,978 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/dhan_pay.
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.