Bot
福利小助手
@guan6jiabot
On this record: Growth · Engagement · Citations · Cite this entry
11,449monthly users
-3,727 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8430046034 |
|---|---|
| Type | Bot |
| Username | @guan6jiabot |
| First recorded | 21 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| On Telegram | t.me/guan6jiabot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 21 Aug 2026, 17:18 | 11,449 | no change |
| 19 Aug 2026, 13:03 | 11,449 | -1,658 |
| 14 Aug 2026, 14:27 | 13,107 | -2,069 |
| 13 Aug 2026, 10:31 | 15,176 | 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“福利小助手” (@guan6jiabot), 11,449 monthly users as measured 21 August 2026. Telegram Register, tgregister.com/channel/guan6jiabot.
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.