Telegram RegisterThe public register of Telegram
Telegram profile photo for H89 Hujan Angpao

Bot

H89 Hujan Angpao

@H89_resmi_bot

On this record: Growth · Engagement · Citations · Cite this entry

38,504monthly users

-2,548 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID8755905614
TypeBot
Username@H89_resmi_bot
First recorded12 August 2026
Last confirmed live27 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/H89_resmi_bot

Growth

38,50441,05239,7787 August 2026 — 41,052 monthly users7 August 2026 — 40,832 monthly users8 August 2026 — 40,665 monthly users10 August 2026 — 40,538 monthly users11 August 2026 — 40,342 monthly users12 August 2026 — 40,342 monthly users12 August 2026 — 40,147 monthly users14 August 2026 — 39,943 monthly users15 August 2026 — 39,765 monthly users17 August 2026 — 39,317 monthly users19 August 2026 — 39,524 monthly users20 August 2026 — 39,078 monthly users22 August 2026 — 38,886 monthly users23 August 2026 — 38,707 monthly users25 August 2026 — 38,667 monthly users27 August 2026 — 38,504 monthly users7 August 202627 August 2026
16 measurements spanning 19 days, net -2,548. 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 38,122–41,434 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
27 Aug 2026, 02:2438,504-163
25 Aug 2026, 01:4638,667-40
23 Aug 2026, 16:3738,707-179
22 Aug 2026, 04:3738,886-192
20 Aug 2026, 17:2339,078-446
19 Aug 2026, 14:5739,524+207
17 Aug 2026, 10:2439,317-448
15 Aug 2026, 18:0639,765-178
14 Aug 2026, 08:2739,943-204
12 Aug 2026, 23:0340,147-195
12 Aug 2026, 20:3340,342no change
11 Aug 2026, 22:2640,342-196
10 Aug 2026, 23:5140,538-127
8 Aug 2026, 23:0340,665-167
7 Aug 2026, 23:3540,832-220
7 Aug 2026, 16:0241,052first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“H89 Hujan Angpao” (@H89_resmi_bot), 38,504 monthly users as measured 27 August 2026. Telegram Register, tgregister.com/channel/H89_resmi_bot.

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.