Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝓫𝓾𝓽𝓽𝓮𝓻𝓯𝓵𝔂🦋

Channel

𝓫𝓾𝓽𝓽𝓮𝓻𝓯𝓵𝔂🦋

@Bluebutterfllllly

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

14,780subscribers

+1,307 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002254759307
TypeChannel
Username@Bluebutterfllllly
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Bluebutterfllllly

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

13,28714,89214,089.57 August 2026 — 13,473 subscribers8 August 2026 — 13,551 subscribers9 August 2026 — 13,768 subscribers10 August 2026 — 13,922 subscribers11 August 2026 — 14,173 subscribers12 August 2026 — 14,219 subscribers14 August 2026 — 14,114 subscribers15 August 2026 — 14,011 subscribers16 August 2026 — 13,885 subscribers17 August 2026 — 13,875 subscribers18 August 2026 — 13,870 subscribers19 August 2026 — 13,870 subscribers19 August 2026 — 13,757 subscribers20 August 2026 — 13,652 subscribers22 August 2026 — 13,629 subscribers23 August 2026 — 13,655 subscribers25 August 2026 — 13,547 subscribers26 August 2026 — 13,484 subscribers27 August 2026 — 13,673 subscribers28 August 2026 — 13,641 subscribers29 August 2026 — 13,551 subscribers30 August 2026 — 13,452 subscribers31 August 2026 — 13,395 subscribers1 September 2026 — 13,287 subscribers2 September 2026 — 13,320 subscribers3 September 2026 — 13,488 subscribers6 September 2026 — 13,290 subscribers9 September 2026 — 13,420 subscribers11 September 2026 — 14,290 subscribers13 September 2026 — 14,720 subscribers15 September 2026 — 14,892 subscribers17 September 2026 — 14,885 subscribers19 September 2026 — 14,780 subscribers14,7807 August 202619 September 2026
33 measurements spanning 43 days, net +1,307. 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 13,046–15,133 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 17:0014,780-105
17 Sept 2026, 02:1714,885-7
15 Sept 2026, 03:5714,892+172
13 Sept 2026, 16:1514,720+430
11 Sept 2026, 21:3514,290+870
9 Sept 2026, 12:0013,420+130
6 Sept 2026, 01:1713,290-198
3 Sept 2026, 20:2113,488+168
2 Sept 2026, 11:1213,320+33
1 Sept 2026, 07:5913,287-108
31 Aug 2026, 11:0813,395-57
30 Aug 2026, 08:2913,452-99
29 Aug 2026, 11:3313,551-90
28 Aug 2026, 10:2313,641-32
27 Aug 2026, 08:3513,673+189
26 Aug 2026, 05:4713,484-63
25 Aug 2026, 03:1813,547-108
23 Aug 2026, 21:5813,655+26
22 Aug 2026, 08:5513,629-23
20 Aug 2026, 23:1713,652first reading

Engagement

No public post preview. We read this entry on 19 August 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.

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

“𝓫𝓾𝓽𝓽𝓮𝓻𝓯𝓵𝔂🦋” (@Bluebutterfllllly), 14,780 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Bluebutterfllllly.

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.