Telegram RegisterThe public register of Telegram

Bot

紧的相册

@jindexiangcebot

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

12,307monthly users

+427 since we began measuring on 8 August 2026

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

Register entry

Telegram ID8360736665
TypeBot
Username@jindexiangcebot
First recorded20 August 2026
Last confirmed live8 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/jindexiangcebot

Growth

11,88012,96912,424.58 August 2026 — 11,880 monthly users9 August 2026 — 12,532 monthly users13 August 2026 — 12,969 monthly users14 August 2026 — 12,888 monthly users16 August 2026 — 12,940 monthly users17 August 2026 — 12,836 monthly users19 August 2026 — 12,755 monthly users20 August 2026 — 12,755 monthly users22 August 2026 — 12,717 monthly users24 August 2026 — 12,794 monthly users28 August 2026 — 12,962 monthly users29 August 2026 — 12,860 monthly users31 August 2026 — 12,904 monthly users3 September 2026 — 12,591 monthly users8 September 2026 — 12,307 monthly users12,3078 August 20268 September 2026
15 measurements spanning 31 days, net +427. 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 11,717–13,132 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
8 Sept 2026, 04:2112,307-284
3 Sept 2026, 08:1812,591-313
31 Aug 2026, 06:4412,904+44
29 Aug 2026, 07:1612,860-102
28 Aug 2026, 08:3312,962+168
24 Aug 2026, 23:3412,794+77
22 Aug 2026, 03:5212,717-38
20 Aug 2026, 10:3412,755no change
19 Aug 2026, 15:5612,755-81
17 Aug 2026, 11:4812,836-104
16 Aug 2026, 02:5312,940+52
14 Aug 2026, 12:0612,888-81
13 Aug 2026, 02:2312,969+437
9 Aug 2026, 23:3612,532+652
8 Aug 2026, 05:2011,880first 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 1 registered channel — 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.

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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“紧的相册” (@jindexiangcebot), 12,307 monthly users as measured 8 September 2026. Telegram Register, tgregister.com/channel/jindexiangcebot.

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.