Channel
@sharp_bubbles
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
127subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002216277924 |
|---|---|
| Type | Channel |
| Username | @sharp_bubbles |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 28 August 2026 |
| On Telegram | t.me/sharp_bubbles |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 21:32 | 127 | +1 |
| 14 Aug 2026, 12:56 | 126 | +2 |
| 9 Aug 2026, 03:02 | 124 | no change |
| 7 Aug 2026, 03:48 | 124 | first reading |
15 posts held, back to 8 March 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 15 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
126 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 63 | 50.0% | |
| custom 5391339916862975539 | 41 | 32.5% | |
| 🔥 | 11 | 8.73% | |
| custom 5249082765999098001 | 5 | 3.97% | |
| ⚡ | 3 | 2.38% | |
| 👍 | 1 | 0.794% | |
| 🕊 | 1 | 0.794% | |
| 🥴 | 1 | 0.794% |
Custom emoji. 2 of the rows above are 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 13 of the 15 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 126 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 8 March 2026 to 28 July 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.
Пузырьки теперь в каждом из вас...?!🤯 Мы сходили в центр сдачи крови и теперь частичка острых пузырьков может спасти чью-то жизнь❤️ Но несмотря на бесплатный выходной мы все продолжаем усердно работать и готовится к засекречено🤣 Заинтриговали? Тогда продолжайте следить за нашими соцсетями, скоро всё расскажем🤔 На здоровом🙈
❤7🕊1🥴1
Отец! Наша команда поздравляет тебя с днем рождения! 🎉🎉 Ты наша защита и опора, друг и старший, мама и папа. Желаем, чтоб все твои Наполеоновские планы исполнялись, чтоб твое здоровье было как у быка и чтоб твои близкие были всегда рядом и счастливы рядом с тобой! От всей любви, твои острые пузырьки😘
🔥7⚡3
Следующие на очереди «Острые пузырьки» г. Хабаровск 🫧 - на сцене команда сдвг - Степ, мы из ДВГУПС Новость про Иришку чики пики и Олега монгола - хорошо😅 - девчонки хватит нам писать.. - мы уже устали от секса - как можно устать СМОТРЕТЬ? Аналог бензина «Добрый бензин» ⛽️😂 Молодчики! Реакция зала - 🔥🔥🔥🔥🔥
❤6
Video message, posted without a caption
❤6
18 июля, 18:00 Дом Офицеров За билетами к нам🤫
❤4custom 52490827659990980012
Video message, posted without a caption
❤6custom 53913399168629755392
Наша команда сорвалась с летнего отдыха и Чемпионата Мира по футболу, чтобы смешить вас 17 и 18 июля! Где? В Доме офицеров Восточного военного округа ул. Шевченко 16 Теперь ваша очередь - залетайте к нам! Будет очень смешно. Ждём! ❤️
custom 53913399168629755398
Video message, posted without a caption
custom 539133991686297553910❤3custom 52490827659990980013
Острые приколы 🎩 Хотелось бы сказать словами классика: «Сафонов, зарегистрируйся!»
Мы уже во Владивостоке 🥳 Самым трудным была поездка в поезде, так как Степа еле поместился в чемодан 😮💨 На сэкономленные деньги мы купим второй чемодан, чтоб Степе было удобно 🥰 Совсем скоро "судный день". Поэтому, следите за нашим каналом и каналом Приморского КВНа👇 https://t.me/kvnprimorkaofficially На добром 🤚
custom 53913399168629755392👍1
Первая игра после победы 🤯 Наша команда отправляется в столицу Финансовой Культуры России - Владивосток!!! Сразимся с лучшими командами Дального Востока и привезем в Хабаровск: - 2 кг морепродуктов🐙 - 3-ёх старых Японцев 🚘 - Ну и какой-то Кубок КВНа🏆 Следите за нашим каналом, контент будет 😜
custom 539133991686297553915❤5🔥2
Это конец..? Мы уходим из КВНа...? 🙊 15 мая состоялся Финал лиги ДВГУПСа, где мы заняли 1 место!!!! (вместе с командой "Уголовный смех") Это была наша последняя игра в лиге ДВГУПСа и больше выступать там не будем. 😔 Но мы не расстраиваемся, ведь мы так же будем участвовать в Лиге ДВГУПСа, но уже косвенно.😏 Дальше нас ожидает 1/4 Тихоокеанской лиги, где мы будем нуждаться в вашей поддержке, приходите💋 ДВГУПС, спаси…
❤19
Showing the 12 most recent of 15 posts we hold for @sharp_bubbles. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“ОСТРЫЕ ПУЗЫРЬКИ” (@sharp_bubbles), 127 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/sharp_bubbles.
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.