Telegram RegisterThe public register of Telegram
Telegram profile photo for Горящие туры от ht.kz

Bot

Горящие туры от ht.kz

@htsubscribtionBot

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

18,047monthly users

-10,141 since we began measuring on 15 August 2026

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

Register entry

Telegram ID8820786598
TypeBot
Username@htsubscribtionBot
First recorded15 August 2026
Last confirmed live30 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/htsubscribtionBot

Growth

18,04728,18823,117.515 August 2026 — 28,188 monthly users15 August 2026 — 28,188 monthly users16 August 2026 — 27,493 monthly users17 August 2026 — 27,290 monthly users20 August 2026 — 23,576 monthly users22 August 2026 — 21,533 monthly users24 August 2026 — 20,239 monthly users25 August 2026 — 19,633 monthly users26 August 2026 — 19,338 monthly users27 August 2026 — 19,269 monthly users30 August 2026 — 18,047 monthly users15 August 202630 August 2026
11 measurements spanning 15 days, net -10,141. 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 16,526–29,709 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
30 Aug 2026, 09:0818,047-1,222
27 Aug 2026, 06:5819,269-69
26 Aug 2026, 03:4319,338-295
25 Aug 2026, 05:2719,633-606
24 Aug 2026, 01:1820,239-1,294
22 Aug 2026, 08:3721,533-2,043
20 Aug 2026, 21:1323,576-3,714
17 Aug 2026, 20:4327,290-203
16 Aug 2026, 20:2827,493-695
15 Aug 2026, 19:2428,188no change
15 Aug 2026, 19:1528,188first 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 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.

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

“Горящие туры от ht.kz” (@htsubscribtionBot), 18,047 monthly users as measured 30 August 2026. Telegram Register, tgregister.com/channel/htsubscribtionBot.

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.