Telegram RegisterThe public register of Telegram
Telegram profile photo for 76号档案室

Bot

76号档案室

@DT76Hbot

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

21,702monthly users

+485 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8269609172
TypeBot
Username@DT76Hbot
First recorded15 August 2026
Last confirmed live2 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/DT76Hbot

Growth

21,21723,50422,360.57 August 2026 — 21,217 monthly users9 August 2026 — 21,589 monthly users11 August 2026 — 21,628 monthly users14 August 2026 — 22,905 monthly users15 August 2026 — 22,905 monthly users16 August 2026 — 23,160 monthly users17 August 2026 — 23,237 monthly users20 August 2026 — 23,397 monthly users22 August 2026 — 23,384 monthly users23 August 2026 — 23,389 monthly users25 August 2026 — 23,504 monthly users26 August 2026 — 23,076 monthly users27 August 2026 — 23,324 monthly users29 August 2026 — 23,135 monthly users31 August 2026 — 22,152 monthly users2 September 2026 — 21,702 monthly users21,7027 August 20262 September 2026
16 measurements spanning 27 days, net +485. 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 20,874–23,847 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
2 Sept 2026, 23:0421,702-450
31 Aug 2026, 20:0822,152-983
29 Aug 2026, 21:2423,135-189
27 Aug 2026, 20:0223,324+248
26 Aug 2026, 01:4223,076-428
25 Aug 2026, 01:2423,504+115
23 Aug 2026, 14:0823,389+5
22 Aug 2026, 00:3723,384-13
20 Aug 2026, 17:2223,397+160
17 Aug 2026, 16:1823,237+77
16 Aug 2026, 07:2323,160+255
15 Aug 2026, 19:4222,905no change
14 Aug 2026, 16:3922,905+1,277
11 Aug 2026, 08:3621,628+39
9 Aug 2026, 07:1121,589+372
7 Aug 2026, 03:1521,217first 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 9 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.

“76号档案室” (@DT76Hbot), 21,702 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/DT76Hbot.

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.