Telegram RegisterThe public register of Telegram
Telegram profile photo for 乐趣频道 投稿&搜索

Bot

乐趣频道 投稿&搜索

@kejiqubot

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

15,759monthly users

-518 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 ID5702907160
TypeBot
Username@kejiqubot
First recorded18 August 2026
Last confirmed live5 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/kejiqubot

Growth

15,75916,32116,0406 August 2026 — 16,277 monthly users8 August 2026 — 16,137 monthly users10 August 2026 — 16,212 monthly users12 August 2026 — 16,321 monthly users15 August 2026 — 16,101 monthly users16 August 2026 — 15,879 monthly users18 August 2026 — 15,879 monthly users19 August 2026 — 16,082 monthly users23 August 2026 — 16,106 monthly users26 August 2026 — 16,007 monthly users26 August 2026 — 16,182 monthly users28 August 2026 — 16,062 monthly users31 August 2026 — 15,932 monthly users1 September 2026 — 15,960 monthly users3 September 2026 — 15,874 monthly users5 September 2026 — 15,759 monthly users6 August 20265 September 2026
16 measurements spanning 29 days, net -518. 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 15,675–16,405 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
5 Sept 2026, 09:0015,759-115
3 Sept 2026, 08:5315,874-86
1 Sept 2026, 03:3615,960+28
31 Aug 2026, 01:1715,932-130
28 Aug 2026, 00:2716,062-120
26 Aug 2026, 21:4516,182+175
26 Aug 2026, 00:1616,007-99
23 Aug 2026, 15:1416,106+24
19 Aug 2026, 20:5216,082+203
18 Aug 2026, 10:3115,879no change
16 Aug 2026, 18:0515,879-222
15 Aug 2026, 07:3416,101-220
12 Aug 2026, 20:3416,321+109
10 Aug 2026, 03:2116,212+75
8 Aug 2026, 06:5816,137-140
6 Aug 2026, 22:3716,277first 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 12 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“乐趣频道 投稿&搜索” (@kejiqubot), 15,759 monthly users as measured 5 September 2026. Telegram Register, tgregister.com/channel/kejiqubot.

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.