Channel
Wedding Footage
@weddingfootage
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,223subscribers
+24 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001891622545 |
|---|---|
| Type | Channel |
| Username | @weddingfootage |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/weddingfootage |
Topic
Other / unclassifiable — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 75% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 22:57 | 1,223 | +6 |
| 4 Oct 2026, 03:06 | 1,217 | no change |
| 30 Sept 2026, 06:59 | 1,217 | -1 |
| 12 Sept 2026, 09:36 | 1,218 | +3 |
| 8 Sept 2026, 07:19 | 1,215 | +1 |
| 3 Sept 2026, 10:16 | 1,214 | +4 |
| 31 Aug 2026, 04:54 | 1,210 | +4 |
| 28 Aug 2026, 08:28 | 1,206 | +2 |
| 25 Aug 2026, 18:15 | 1,204 | +5 |
| 18 Aug 2026, 04:45 | 1,199 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@MansurbekRustamov · 20,120
Telegram ranks this channel #33 of 63 here — alongside 62 others — read 28 September 2026
@maiconedits · 19,690
Telegram ranks this channel #50 of 55 here — alongside 54 others — read 2 October 2026
@PremierePro_templates · 22,709
Telegram ranks this channel #61 of 66 here — alongside 65 others — read 20 September 2026
@PremTemp · 48,291
Telegram ranks this channel #62 of 77 here — alongside 76 others — read 26 August 2026
@Premiere023 · 35,101
Telegram ranks this channel #64 of 69 here — alongside 68 others — read 3 September 2026
@projects4ae · 21,636
Telegram ranks this channel #69 of 71 here — alongside 70 others — read 23 September 2026
@AEStorage · 87,328
Telegram ranks this channel #70 of 70 here — alongside 69 others — read 18 August 2026
@premiere_pro · 64,045
Telegram ranks this channel #72 of 75 here — alongside 74 others — read 21 August 2026
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“Wedding Footage” (@weddingfootage), 1,223 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/weddingfootage.
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.