Channel
@AYUSH_RANGDAR_HU
On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Citations Β· Cite this entry
1,455subscribers
-46 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
| Telegram ID | -1003832868967 |
|---|---|
| Type | Channel |
| Username | @AYUSH_RANGDAR_HU |
| Created | Between 1 February 2026 and 28 May 2026 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/AYUSH_RANGDAR_HU |
Hacking & security β 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 08:00 | 1,455 | +10 |
| 13 Sept 2026, 01:55 | 1,445 | -9 |
| 9 Sept 2026, 06:00 | 1,454 | +3 |
| 3 Sept 2026, 21:40 | 1,451 | -4 |
| 31 Aug 2026, 07:05 | 1,455 | -8 |
| 28 Aug 2026, 02:11 | 1,463 | -9 |
| 19 Aug 2026, 17:12 | 1,472 | -2 |
| 16 Aug 2026, 18:37 | 1,474 | -14 |
| 13 Aug 2026, 15:56 | 1,488 | -7 |
| 10 Aug 2026, 21:53 | 1,495 | -6 |
| 7 Aug 2026, 21:47 | 1,501 | no change |
| 7 Aug 2026, 19:11 | 1,501 | first reading |
20 posts held, back to 28 May 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 1 page of Telegramβs post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute β we hold 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
50 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 54.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| β€ | 27 | 54.0% | |
| π€£ | 9 | 18.0% | |
| π‘ | 3 | 6.00% | |
| π€¬ | 3 | 6.00% | |
| π€ | 2 | 4.00% | |
| π₯° | 2 | 4.00% | |
| π | 1 | 2.00% | |
| π | 1 | 2.00% | |
| π₯ | 1 | 2.00% | |
| π€ | 1 | 2.00% |
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 12 of the 20 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 50 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 20 most recent posts we hold, published 28 May 2026 to 6 August 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.
πππ ππππππ πππππ ππππ π ππππππππ ππππππ πππππ π πππ - πππππ ππππ πππ ππ πππ - πππππ πππππ ππ - @AYUSH_HU_BABU // @Obitosir786
β€2
πππ πππ πππππ π π ππππ ππππππ πππ // π. ππππ π - π. ππππ - πππππ ππππ π- πππ πππππ πππππ ππππ πππππ ππ - @AYUSH_HU_BABU
π€2
πππ πππ πππππ ππ ππππ π πππ ππππππ // πππ , πππ, πππππππ - πππππ π πππ - πππππ ππππ ππ - @AYUSH_HU_BABU
β€1
@AYUSH_VIDEO_DOWNLOADbot @AYUSH_VIDEO_DOWNLOADbot @AYUSH_VIDEO_DOWNLOADbot @AYUSH_VIDEO_DOWNLOADbot π±πππ πππππ ππππππππ πππ ππ πππππ π±πππππ //π± π πππππππ// πππππππ πππ. π± β€οΈβπ₯πππ ππ πππ - πππππ ππ ππππ ππππ πππ πππππ ππππππππ πππ ππ ππππ ππππ πππ π
π±π‘ππͺ π ππ§π πͺπππ§πππ¦π§ ππ¬π£ππ¦π¦ π ππ§ππ’π ππ πππ¬ππ± π₯π ππ§ππ’π - πππππ πππππ π₯ β€οΈβπ₯ππ‘π¬ π£π₯π’ππππ ππ - @AYUSH_HU_BABUπ
ππππππ πππ πππππ ππ ππππ ππππ ππππππ π₯² π«£πππππ -ππππ-ππππ π πππππ - π-ππ. β€οΈβπ₯ βοΈπ ππππππππ π-πππβ€οΈβπ₯ π πππ - π©π£π‘πππ¬ π©π£π‘β ππ πππ π¬ πππππ ππππ πππππ ππππ πππππ ππππ ππππππ ππ - @AYUSH_HU_BABUπ
β€1π₯1π€£1π₯°1
ππππππ ππππππππππ ππ πππ π πππππ ππ πππππ«£ πππππ ππππππβ ππ- πππππ β‘οΈ πππππ β βοΈπβͺοΈπππππβ‘οΈπππππβ βοΈπ β‘οΈπππππβͺοΈβ‘οΈπππππ βοΈ β€οΈπππ ππ ππππππππ - β€οΈβπ₯HAPPY BIRTHDAY AYUSHβοΈ πTOOLS BY π¦@AYUSH_HU_YAARπ π±πππππππππ πππ ππππππ ππ πππ πππππππ± π€©ππππππ - ππππππ€© π±πππππ ππππ - ππππππ
β€5
β‘οΈπππ πππ πππππ π β€οΈβπ₯πππ π©π£π‘πππ¬ π©π£π‘ - πππ π.ππ ππ ππππ ππππππ πππππ βοΈπ πππππππππ ππππβ οΈ ππππππ ππ - @AYUSH_HU_BABUπ
β€2π1π€¬1π₯°1
ππππ πππππ πππ π πππ ππππππ ππππ π« π - πππππ ππ π πππ - πππππ π- πππππ ππ π πππ - πππππ ππππππ ππ - ππππ
β€4
β€οΈβπ₯πππ ππππ ππππππ π πππ ππ ππππ β‘οΈ ππππππ - πππππ π ππππ β οΈπππ ππ ππππππ ππππππ πππ ππππ ππππ ππππ ππ π π + ππππ πππ ππππ ππ πππππ π πππ π πππ πππ π ο»Ώ β€οΈβπ₯π πππ β‘οΈπππππ πππππ½ πππππππ ππ ~ @AYUSH_HU_YAARπ
β€4π1π€1π€£1
βοΈπππππ πππ πππ // π. ππππ πππππ ππ ππππ ππππ-ππππβ ππππ ~ πππππππ πππ πππ πππππππ π. ππ β€οΈβπ₯ β€οΈβπ₯π πππ π£ πππππ ππππ π πππ π @ts_comm_ruler_ayushπ
β€οΈβπ₯πππππ π ππππ ππππππ π πππ ππ πππππ βοΈππππ ππππ πππ ππππ π πππππππππ₯ π»π πππ β‘οΈπππππ πππππ± ππ« πͺΆ@ts_comm_ruler_ayushπͺΆ π©βπ» β‘οΈ @ayan_talkkbot π±
β€3
Showing the 12 most recent of 20 posts we hold for @AYUSH_RANGDAR_HU. 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.
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.
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.
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 17 September 2026 β this entry's latest reading, not the date you are reading this.
βππ¬π¨π¦πβ (@AYUSH_RANGDAR_HU), 1,455 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/AYUSH_RANGDAR_HU.
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.