Telegram RegisterThe public register of Telegram
Telegram profile photo for Александр HR

Bot

Александр HR

@Alexandr_hr_bot

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

10,098monthly users

-7,197 since we began measuring on 12 August 2026

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

Register entry

Telegram ID8362736007
TypeBot
Username@Alexandr_hr_bot
First recorded17 August 2026
Last confirmed live4 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/Alexandr_hr_bot

Growth

10,09817,43113,764.512 August 2026 — 17,295 monthly users14 August 2026 — 17,431 monthly users17 August 2026 — 17,134 monthly users17 August 2026 — 17,134 monthly users19 August 2026 — 16,163 monthly users20 August 2026 — 15,785 monthly users21 August 2026 — 15,610 monthly users23 August 2026 — 15,188 monthly users24 August 2026 — 14,484 monthly users26 August 2026 — 12,831 monthly users27 August 2026 — 12,445 monthly users28 August 2026 — 12,018 monthly users29 August 2026 — 11,371 monthly users30 August 2026 — 10,844 monthly users1 September 2026 — 10,330 monthly users2 September 2026 — 10,098 monthly users12 August 20262 September 2026
16 measurements spanning 21 days, net -7,197. 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 8,998–18,531 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
2 Sept 2026, 20:5310,098-232
1 Sept 2026, 18:1410,330-514
30 Aug 2026, 16:2910,844-527
29 Aug 2026, 18:0411,371-647
28 Aug 2026, 20:4312,018-427
27 Aug 2026, 22:3812,445-386
26 Aug 2026, 23:2512,831-1,653
24 Aug 2026, 22:2614,484-704
23 Aug 2026, 10:4415,188-422
21 Aug 2026, 21:5715,610-175
20 Aug 2026, 19:1615,785-378
19 Aug 2026, 19:0416,163-971
17 Aug 2026, 19:4717,134no change
17 Aug 2026, 15:4617,134-297
14 Aug 2026, 16:3517,431+136
12 Aug 2026, 10:0517,295first 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 3 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“Александр HR” (@Alexandr_hr_bot), 10,098 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/Alexandr_hr_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.