Telegram RegisterThe public register of Telegram
Telegram profile photo for Firefly Wedding Mmsub

Channel

Firefly Wedding Mmsub

@fireflyweddingmm

Has discussion group

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

25,532subscribers

+21,895 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003892719084
TypeChannel
Username@fireflyweddingmm
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live28 October 2026
Measurements held32
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/fireflyweddingmm

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

Previous handles

@fireflyweddingmm was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@sparksoftomorrowmmsub
held 4 September 2026 – 4 September 2026

Growth

3,63725,53214,584.511 August 2026 — 3,637 subscribers12 August 2026 — 3,648 subscribers15 August 2026 — 3,707 subscribers18 August 2026 — 3,796 subscribers21 August 2026 — 3,851 subscribers24 August 2026 — 3,898 subscribers27 August 2026 — 3,952 subscribers30 August 2026 — 4,005 subscribers2 September 2026 — 4,232 subscribers4 September 2026 — 4,232 subscribers8 September 2026 — 4,604 subscribers12 September 2026 — 4,830 subscribers16 September 2026 — 4,974 subscribers28 September 2026 — 5,436 subscribers3 October 2026 — 5,619 subscribers3 October 2026 — 5,619 subscribers7 October 2026 — 5,769 subscribers13 October 2026 — 14,417 subscribers14 October 2026 — 15,685 subscribers15 October 2026 — 17,000 subscribers16 October 2026 — 18,059 subscribers18 October 2026 — 20,015 subscribers19 October 2026 — 21,120 subscribers19 October 2026 — 21,860 subscribers21 October 2026 — 22,376 subscribers22 October 2026 — 23,020 subscribers23 October 2026 — 23,507 subscribers24 October 2026 — 24,301 subscribers25 October 2026 — 24,931 subscribers26 October 2026 — 25,179 subscribers27 October 2026 — 25,407 subscribers28 October 2026 — 25,532 subscribers11 August 202628 October 2026
32 measurements spanning 78 days, net +21,895. 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 353–28,816 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
28 Oct 2026, 07:1625,532+125
27 Oct 2026, 09:5425,407+228
26 Oct 2026, 10:4125,179+248
25 Oct 2026, 08:2824,931+630
24 Oct 2026, 07:4924,301+794
23 Oct 2026, 09:1623,507+487
22 Oct 2026, 06:5523,020+644
21 Oct 2026, 02:4122,376+516
19 Oct 2026, 23:4621,860+740
19 Oct 2026, 00:2821,120+1,105
18 Oct 2026, 01:1920,015+1,956
16 Oct 2026, 23:0618,059+1,059
15 Oct 2026, 23:0717,000+1,315
14 Oct 2026, 23:5915,685+1,268
13 Oct 2026, 19:5914,417+8,648
7 Oct 2026, 21:565,769+150
3 Oct 2026, 17:005,619no change
3 Oct 2026, 14:175,619+183
28 Sept 2026, 15:005,436+462
16 Sept 2026, 07:024,974first reading

Engagement

No public post preview. We read this entry on 23 October 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Firefly Wedding Mmsub” (@fireflyweddingmm), 25,532 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/fireflyweddingmm.

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.