Telegram RegisterThe public register of Telegram
Telegram profile photo for (рест на неопр.срок)ᏴᴀsᴋᴇᴛᏴunny ᏴᏞᏫᏀ

Channel

(рест на неопр.срок)ᏴᴀsᴋᴇᴛᏴunny ᏴᏞᏫᏀ

@BasketBunnyblog

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

128subscribers

-4 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002673618420
TypeChannel
Username@BasketBunnyblog
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live20 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 20 August 2026
On Telegramt.me/BasketBunnyblog

Previous handles

@BasketBunnyblog 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.

@BasketBunnyblog
held 9 August 20269 August 2026

Growth

1281321306 August 2026 — 132 subscribers7 August 2026 — 131 subscribers9 August 2026 — 131 subscribers13 August 2026 — 130 subscribers20 August 2026 — 128 subscribers6 August 202620 August 2026
5 measurements spanning 14 days, net -4. 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 127–133 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 21:07128-2
13 Aug 2026, 09:18130-1
9 Aug 2026, 00:46131no change
7 Aug 2026, 05:43131-1
6 Aug 2026, 21:46132first reading

Engagement

20 posts held, back to 6 July 2026the 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 20 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

6 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘350.0%
116.7%
👎116.7%
🔥116.7%

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 5 of the 20 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 July 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, 18:22 UTC6 viewsread 9 August 2026
Forwarded from @HyperlasercfVideo

🌟♥️🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤩 – Охх... Почему нету Гиперлазер кф? Почти все то есть...😑 🤩🤩⚡⚡⚡⚡⚡⚡⚡🤩🤩 🤩 – Хотелось бы найти отдельный канал с ним...😊 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🤩 – Хмм, знакомо не так ли? У всех есть кф а у Гиперлазера нету? И лишь блоги? Окей. Предлагаю вам свою помощь... 💫💫💫💫💫💫💫💫💫💫💫 💫💫💫🤍🤍🤍🤍🤍🤍🤍💫 😻 mp post / bot take / boost / rules / admin list / Honor Board 😻

5 Aug 2026, 08:44 UTC9 viewsread 9 August 2026
Forwarded from @AzureTimeblogAngst

ㅤⲏᥲⲇ𐔖ᥱ᥈υ ⳝ᥈𐔖𐔏υ 𐔏ⲇᥱ ᥲⳅ𐔤ρⲧᥲύⲙ ⲃᥴᥱ ᥱպᥱ ⲃ᥈юⳝ᥈ᥱⲏⲏᥲя ᥒᥲρ𐔖ɥⲕᥲ ᥒ𐔖ᥴ᥈ᥱ ᥒ𐔖ᥒᥲⲇᥲⲏυя ⲃ ⲉⲧ𐔖ⲧ ᥲⲇ? ꥟ ㅤΧⲟⲧⲉⲗυ ⳝы ⲩⲃυⲇⲉⲧь ⳝⲟⲗⲉⲉ "Κⲁⲏⲟⲏυɥⲏыⲉ" ⲟⲧⲏⲟⲱⲉⲏυя ⲙⲉⲿⲇⲩ ⲏυⲙυ ⲡⲟⲥⲗⲉ ⲥⲙⲉⲣⲧυ? ㅤ ㅤ ㅤ ㅤ ㅤㅤㅤ го к нам?

5 Aug 2026, 08:13 UTC11 viewsread 9 August 2026
Photo

݃ @.𝗺𝗼𝗼𝗻𝗯𝗲𝗿𝗿𝘆 𝗱𝗮𝗶𝗹𝘆𝗰𝗳 . 𝘄𝘄 𖥻 𝓌𝐡𝐚𝐭 ? ᛝ‌꯭ᛝ ⎯ׅ⎯ׄ необходимо больше контента по этим двум ? ּׅ ︶ִ⏝ 𝔀𝐞𝐥𝐥. . . ♡゙ ты пришел в нужное место ! 𝗻𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗼𝗻 | 𝗺𝗽 | join

29 Jul 2026, 17:02 UTC14 viewsread 9 August 2026
Forwarded from @HATEdoublefedora_confessionPhoto

🌟🌟✨✨✨✨✨✨✨✨ а у нас конкурс ! 🐇 - 🔠оже какие же конченные фанаты! 😭 - 🔠очему они такие тупые! 🐇 - 🔠то это за ХУЙНЯ?! 🐇 - 🔠еня сейчас вывернет от этой херни! 🐇 - 🔠выколите мне глаза, что я только что увидел. 𝓦𝒆𝒍𝒍, 𝓦𝒆𝒍𝒍. . . 🥹 🔠𝘦𝘭𝘤𝘰𝘮𝘦 𝘵𝘰 𝘏𝘈𝘛𝘌 𝘋𝘖𝘜𝘉𝘓𝘌𝘍𝘌𝘋𝘖𝘙𝘈 𝘊𝘍 👩‍❤️‍👨

28 Jul 2026, 20:16 UTC11 viewsread 9 August 2026
Forwarded from @rblxblogsgossip

🎤 🅰️тот блог Нуба такой скучный❗ 🎤 🅰️ этот Гость просто прелесть🥰 🎤 🅰️ы вообще видели 👻👻❓ > > 🅰️то такой позор💀 🖥️ Знакомо ? Тогда добро пожаловать в ... 🔹одслушку 🔹облокс 🔹логов 💬 Здесь вы можете анонимно высказать любое мнение по поводу любого блога , связанным с роблокс фд ❗️ Примечание : администрация не несёт ответственность за тейки в канале и не поддерживает мнение

28 Jul 2026, 16:39 UTC22 views1 reactionsread 9 August 2026

🪷 У тебя новое сообщение! Привет, @юзер дарит подарки🎁💍🚀🐻 ваще всем кто ей напишет в лс °{🪷✨}°—... А можно в анон не писать такое? Я Аш забыла от какого блога у меня анон

🔥1

28 Jul 2026, 03:36 UTC24 viewsread 9 August 2026

°{🪷✨}°—я ориентируюсь по мск времени,сама я не живу в Москве... Так что если у вас другое время,то знайте что сапп Бесси пишет про мск время...

Showing the 12 most recent of 20 posts we hold for @BasketBunnyblog. 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

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

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

“(рест на неопр.срок)ᏴᴀsᴋᴇᴛᏴunny ᏴᏞᏫᏀ” (@BasketBunnyblog), 128 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/BasketBunnyblog.

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.