Telegram RegisterThe public register of Telegram
Telegram profile photo for LOPYCUTEE

Bot

LOPYCUTEE

@lopycute_bot

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

37,315monthly users

-534 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8756257774
TypeBot
Username@lopycute_bot
First recorded13 August 2026
Last confirmed live15 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/lopycute_bot

Growth

37,31538,28937,8027 August 2026 — 37,849 monthly users8 August 2026 — 37,912 monthly users9 August 2026 — 38,100 monthly users10 August 2026 — 37,722 monthly users11 August 2026 — 38,169 monthly users12 August 2026 — 38,289 monthly users13 August 2026 — 38,289 monthly users14 August 2026 — 38,223 monthly users15 August 2026 — 37,315 monthly users7 August 202615 August 2026
9 measurements spanning 8 days, net -534. 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 37,169–38,435 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
15 Aug 2026, 20:1437,315-908
14 Aug 2026, 08:0838,223-66
13 Aug 2026, 02:4238,289no change
12 Aug 2026, 23:5938,289+120
11 Aug 2026, 22:2338,169+447
10 Aug 2026, 02:1137,722-378
9 Aug 2026, 04:2138,100+188
8 Aug 2026, 04:2737,912+63
7 Aug 2026, 19:3337,849first 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 4 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“LOPYCUTEE” (@lopycute_bot), 37,315 monthly users as measured 15 August 2026. Telegram Register, tgregister.com/channel/lopycute_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.