Bot

抽奖机器人

@BlessingGuardian_bot

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

13,960monthly users

+949 since we began measuring on 6 August 2026

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

Register entry

Telegram ID	7987834255
Type	Bot
Username	@BlessingGuardian_bot
First recorded	19 August 2026
Last confirmed live	2 September 2026
Measurements held	19
Confirmed unchanged	1 time, most recently 2 September 2026
On Telegram	t.me/BlessingGuardian_bot

Growth

19 measurements spanning 27 days, net +949. 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 12,869–14,102 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
2 Sept 2026, 21:45	13,960	+247
1 Sept 2026, 21:45	13,713	+138
30 Aug 2026, 14:35	13,575	-124
29 Aug 2026, 12:33	13,699	+19
27 Aug 2026, 11:38	13,680	-67
26 Aug 2026, 08:07	13,747	-31
25 Aug 2026, 05:05	13,778	-8
22 Aug 2026, 06:26	13,786	+103
21 Aug 2026, 00:08	13,683	+50
20 Aug 2026, 00:44	13,633	+312
19 Aug 2026, 21:07	13,321	no change
19 Aug 2026, 00:53	13,321	-37
16 Aug 2026, 19:23	13,358	-62
15 Aug 2026, 08:55	13,420	-28
14 Aug 2026, 01:28	13,448	+3
11 Aug 2026, 18:21	13,445	-13
9 Aug 2026, 22:32	13,458	+25
8 Aug 2026, 21:11	13,433	+422
6 Aug 2026, 20:17	13,011	first 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.

Named by

Channels on the register whose posts name this channel's handle.

实用技巧与教程
@JngjiaoxuEpd · 411 post 黑车防骗指南大全
@kind216 · 2,7211 post

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.

“抽奖机器人” (@BlessingGuardian_bot), 13,960 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/BlessingGuardian_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.