Telegram RegisterThe public register of Telegram
Telegram profile photo for IMSPanel

Bot

IMSPanel

@IMSPanel_BOT

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

19,515monthly users

-81 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 ID8447068033
TypeBot
Username@IMSPanel_BOT
First recorded16 August 2026
Last confirmed live27 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/IMSPanel_BOT

Growth

18,94119,63119,2867 August 2026 — 19,596 monthly users9 August 2026 — 19,604 monthly users10 August 2026 — 19,543 monthly users11 August 2026 — 19,162 monthly users13 August 2026 — 19,225 monthly users14 August 2026 — 19,459 monthly users16 August 2026 — 19,281 monthly users16 August 2026 — 19,281 monthly users17 August 2026 — 19,074 monthly users19 August 2026 — 19,026 monthly users21 August 2026 — 18,941 monthly users22 August 2026 — 19,031 monthly users24 August 2026 — 19,160 monthly users25 August 2026 — 19,454 monthly users26 August 2026 — 19,631 monthly users27 August 2026 — 19,515 monthly users19,5157 August 202627 August 2026
16 measurements spanning 20 days, net -81. 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 18,838–19,735 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
27 Aug 2026, 10:1619,515-116
26 Aug 2026, 07:4719,631+177
25 Aug 2026, 09:3719,454+294
24 Aug 2026, 09:1319,160+129
22 Aug 2026, 16:0819,031+90
21 Aug 2026, 09:3518,941-85
19 Aug 2026, 13:1419,026-48
17 Aug 2026, 12:3819,074-207
16 Aug 2026, 20:2819,281no change
16 Aug 2026, 02:5719,281-178
14 Aug 2026, 13:0419,459+234
13 Aug 2026, 02:4619,225+63
11 Aug 2026, 05:0819,162-381
10 Aug 2026, 02:5219,543-61
9 Aug 2026, 04:2119,604+8
7 Aug 2026, 18:4519,596first 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 3 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“IMSPanel” (@IMSPanel_BOT), 19,515 monthly users as measured 27 August 2026. Telegram Register, tgregister.com/channel/IMSPanel_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.