Telegram RegisterThe public register of Telegram
Telegram profile photo for BlueBunny

Channel

BlueBunny

@BLUE_BUNNY7

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

53subscribers

+12 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003924071630
TypeChannel
Username@BLUE_BUNNY7
CreatedBetween 1 April 2026 and 21 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/BLUE_BUNNY7

Growth

4153479 August 2026 — 41 subscribers10 August 2026 — 41 subscribers17 August 2026 — 43 subscribers1 September 2026 — 47 subscribers11 September 2026 — 49 subscribers19 September 2026 — 53 subscribers9 August 202619 September 2026
6 measurements spanning 41 days, net +12. 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 39–55 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 11:5853+4
11 Sept 2026, 04:1949+2
1 Sept 2026, 13:5647+4
17 Aug 2026, 12:1943+2
10 Aug 2026, 18:3141no change
9 Aug 2026, 12:4541first reading

Engagement

11 posts held, back to 21 June 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 11 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

193 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54453577892642433415729.5%
custom 53283132732489254745428.0%
custom 52895411259991908804422.8%
custom 52830003160091363423819.7%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 11 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 193 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 21 June 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

5 Aug 2026, 23:28 UTC100 views17 reactionsread 10 August 2026
Photo

Все по синему пошли) 🤩💽🪂 #work_BlueBunny

custom 52895411259991908808custom 53283132732489254744custom 54453577892642433413custom 52830003160091363422

2 Aug 2026, 12:02 UTC194 views22 reactionsread 10 August 2026
Photo

Многострвдальческий выход из черного, длиной в почти год!) 🟦🧊🪟🪟🪟 #work_BlueBunny

custom 544535778926424334110custom 52830003160091363425custom 53283132732489254744custom 52895411259991908803

1 Aug 2026, 21:42 UTC134 views19 reactionsread 10 August 2026
Photo

Стрижка + окрашивание 💔🥤🥤 #work_BlueBunny

custom 532831327324892547410custom 54453577892642433414custom 52895411259991908803custom 52830003160091363422

27 Jul 2026, 18:59 UTC156 views19 reactionsread 10 August 2026
Photo

Актуальный прайс 🤩 Пишите в чат канал Отвечу на все вопросы и напишу диапазон стоимости под ваш запрос *стоимость может быть больше, если волосы экстра густые/длинные #price Воронеж. Левый берег BlueBunny🐰🚬

custom 53283132732489254748custom 54453577892642433416custom 52830003160091363424custom 52895411259991908801

27 Jul 2026, 13:26 UTC195 views22 reactionsread 10 August 2026
Photo

Стрижечка, малетик😂 #work_BlueBunny

custom 52830003160091363428custom 52895411259991908806custom 54453577892642433416custom 53283132732489254742

21 Jul 2026, 17:59 UTC167 views18 reactionsread 10 August 2026
Photo

Сделали моей любимой постояннице скрытое белое окрашивание, обновили цвет, подстриглись 🍀🤩🌿🪷🤩 #work_BlueBunny

custom 54453577892642433419custom 52895411259991908804custom 53283132732489254744custom 52830003160091363421

10 Jul 2026, 13:52 UTC267 views23 reactionsread 10 August 2026
Photo

👅🪷🪷🐇 #work_BlueBunny

custom 532831327324892547414custom 52830003160091363424custom 54453577892642433414custom 52895411259991908801

7 Jul 2026, 18:15 UTC228 views17 reactionsread 10 August 2026
Photo

☺️🌑🚬 #work_BlueBunny

custom 52895411259991908807custom 54453577892642433414custom 52830003160091363423custom 53283132732489254743

6 Jul 2026, 15:28 UTC238 views13 reactionsread 10 August 2026
Photo

Я безумно довольна этой работой) 🚬🪷🥤 #work_BlueBunny

custom 52830003160091363426custom 53283132732489254743custom 54453577892642433413custom 52895411259991908801

21 Jun 2026, 18:08 UTC388 views23 reactionsread 10 August 2026
Photo

🎀сегодня нежнятинка🪷 #work_BlueBunny

custom 528954112599919088010custom 54453577892642433418custom 52830003160091363423custom 53283132732489254742

Showing the 11 most recent of 11 posts we hold for @BLUE_BUNNY7. 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.

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.

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.

“BlueBunny” (@BLUE_BUNNY7), 53 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/BLUE_BUNNY7.

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.