Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔱 MoviewaveTv 🔱

Channel

🔱 MoviewaveTv 🔱

@MoviewaveTv

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

948subscribers

+231 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003698824582
TypeChannel
Username@MoviewaveTv
Created2 May 2026 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live26 October 2026
Measurements held12
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/MoviewaveTv

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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

717948832.57 August 2026 — 717 subscribers8 August 2026 — 717 subscribers8 August 2026 — 722 subscribers15 August 2026 — 748 subscribers23 August 2026 — 761 subscribers31 August 2026 — 771 subscribers9 September 2026 — 788 subscribers18 September 2026 — 830 subscribers2 October 2026 — 888 subscribers12 October 2026 — 916 subscribers20 October 2026 — 935 subscribers26 October 2026 — 948 subscribers7 August 202626 October 2026
12 measurements spanning 80 days, net +231. 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 682–983 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 20:17948+13
20 Oct 2026, 00:58935+19
12 Oct 2026, 22:58916+28
2 Oct 2026, 09:37888+58
18 Sept 2026, 06:20830+42
9 Sept 2026, 14:37788+17
31 Aug 2026, 07:17771+10
23 Aug 2026, 10:46761+13
15 Aug 2026, 17:14748+26
8 Aug 2026, 16:24722+5
8 Aug 2026, 02:16717no change
7 Aug 2026, 18:23717first reading

Engagement

1 post held, back to 2 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 1 post for this entry, the most recent from 2 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 1 most recent of 1 post we hold for @MoviewaveTv. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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

“🔱 MoviewaveTv 🔱” (@MoviewaveTv), 948 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/MoviewaveTv.

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.