Telegram RegisterThe public register of Telegram
Telegram profile photo for MovieLuuv

Bot

MovieLuuv

@MovieLuuvBot

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

22,597monthly users

-9,035 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 ID6918939120
TypeBot
Username@MovieLuuvBot
First recorded13 August 2026
Last confirmed live30 October 2026
Measurements held42
Confirmed unchanged2 times, most recently 30 October 2026
On Telegramt.me/MovieLuuvBot

Topic

Film & TV — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

22,59731,84727,2226 August 2026 — 31,632 monthly users7 August 2026 — 31,542 monthly users8 August 2026 — 31,481 monthly users11 August 2026 — 31,221 monthly users13 August 2026 — 31,279 monthly users13 August 2026 — 31,279 monthly users14 August 2026 — 31,680 monthly users16 August 2026 — 31,685 monthly users17 August 2026 — 31,815 monthly users18 August 2026 — 31,847 monthly users20 August 2026 — 31,039 monthly users22 August 2026 — 31,655 monthly users23 August 2026 — 31,814 monthly users25 August 2026 — 31,741 monthly users26 August 2026 — 31,609 monthly users27 August 2026 — 31,480 monthly users29 August 2026 — 31,511 monthly users30 August 2026 — 31,519 monthly users1 September 2026 — 31,538 monthly users2 September 2026 — 30,519 monthly users3 September 2026 — 31,051 monthly users8 September 2026 — 30,375 monthly users11 September 2026 — 29,809 monthly users13 September 2026 — 29,999 monthly users14 September 2026 — 29,631 monthly users16 September 2026 — 29,182 monthly users18 September 2026 — 28,531 monthly users1 October 2026 — 27,527 monthly users6 October 2026 — 26,581 monthly users10 October 2026 — 26,541 monthly users13 October 2026 — 26,031 monthly users16 October 2026 — 25,493 monthly users17 October 2026 — 25,431 monthly users19 October 2026 — 24,964 monthly users21 October 2026 — 25,249 monthly users22 October 2026 — 25,034 monthly users23 October 2026 — 24,880 monthly users24 October 2026 — 24,683 monthly users25 October 2026 — 24,565 monthly users27 October 2026 — 24,222 monthly users28 October 2026 — 23,647 monthly users29 October 2026 — 22,597 monthly users6 August 202629 October 2026
42 measurements spanning 84 days, net -9,035. 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 21,210–33,235 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 42
Measured (UTC)Monthly usersChange
29 Oct 2026, 08:1722,597-1,050
28 Oct 2026, 08:3823,647-575
27 Oct 2026, 05:4624,222-343
25 Oct 2026, 06:4624,565-118
24 Oct 2026, 09:3024,683-197
23 Oct 2026, 11:0024,880-154
22 Oct 2026, 11:2025,034-215
21 Oct 2026, 06:3025,249+285
19 Oct 2026, 06:2724,964-467
17 Oct 2026, 02:5025,431-62
16 Oct 2026, 02:2525,493-538
13 Oct 2026, 22:5926,031-510
10 Oct 2026, 20:3626,541-40
6 Oct 2026, 19:3826,581-946
1 Oct 2026, 23:3827,527-1,004
18 Sept 2026, 11:5928,531-651
16 Sept 2026, 07:1629,182-449
14 Sept 2026, 12:1929,631-368
13 Sept 2026, 01:5929,999+190
11 Sept 2026, 05:4129,809first 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.

Mentions

Named by 5 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“MovieLuuv” (@MovieLuuvBot), 22,597 monthly users as measured 29 October 2026. Telegram Register, tgregister.com/channel/MovieLuuvBot.

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.