Разрыв с проэктом WOOF Причина: Закрытие #Разрыв_Bb
😱2💔1
Signed Любитель чак чака

Channel
@BlueberryLifech
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002209056819 |
|---|---|
| Type | Channel |
| Username | @BlueberryLifech |
| Description | Info - https://t.me/BlueberryInfoCh Owner - @bybeeeb |
| Created | Between 1 June 2024 and 11 July 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BlueberryLifech |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 06:17 | 4 | no change |
| 11 Aug 2026, 13:46 | 4 | first reading |
14 posts held, back to 11 July 2024 — 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 pageof 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 14 posts for this entry, the most recent from 16 July 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
20 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 35.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💔 | 7 | 35.0% | |
| 😭 | 6 | 30.0% | |
| 😱 | 3 | 15.0% | |
| ❤ | 1 | 5.00% | |
| ❤🔥 | 1 | 5.00% | |
| 🔥 | 1 | 5.00% | |
| 😢 | 1 | 5.00% |
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 6 of the 14 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 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 11 July 2024 to 16 July 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Разрыв с проэктом WOOF Причина: Закрытие #Разрыв_Bb
😱2💔1
Signed Любитель чак чака
#Acheron ~какой ужас, так много разрывов.. #Ayaka Да вообще капец. А еще я хотела это написать и случайно жалобу на сообщение отправила.😔 #Щп_Bb
❤1❤🔥1🔥1
Signed mazz #дт(!)
Разрыв с 𝐏𝐫𝐢𝐚𝐩𝐢𝐜 𝐥♡𝐯𝐞 ৎ˚˖ Причина: закрытие #Разрыв_Bb
😭2💔1
Signed Любитель чак чака
Разрыв с actor's dreams!! Причина: закрытие #Разрыв_Bb
💔1😱1
Signed Любитель чак чака
Разрыв с ✧˚ · . .𝐒𝐓𝐀𝐑𝐋𝐈𝐆𝐇𝐓 𝐍𝐈𝐆𝐇𝐓 Разрыв с ғʟᴏᴡᴇʀs ᴏғ ʟɪғᴇ Причина: закрытие #Разрыв_Bb
💔4😭1
Signed Любитель чак чака
Channel name was changed to «[РЕСТ] Blueberryᶫᶦᶠᵉ»
#Ayaka Ну а теперь насчет реста, лайф уходит в рест на некоторое время. Я уезжаю из города и вряд ли будет возможность его вести, за флудом я постараюсь сделать. Мы не: Участвуем в чистках союзов. Делаем репосты. Принимаем союзы. Надеюсь без разрывов. Насчет союзов вы можете писать, но союз заключим только тогда когда рест закончится и я вернусь в город. #Важно_Bb #Репост_Bb
😭3😢1
Signed Любитель чак чака
Ну и вот еще. #Репост_Bb
Signed Любитель чак чака
#Ayaka И так.. Перед тем как лайф уйдет в рест мне бы хотелось сказать, что нам нужны активные участники, админ-пиарщик, и... Сорол для замечательной Люмин - Кэйа, Дайнслейф. Писать - @bybeeeb #Важно_Bb
Signed Любитель чак чака
° 🤍🤍🌟🌟🌟🌟🌟🌟🤍🤍 🪽🪽🪽🪽🪽🪽🪽🪽🪽🪽🪽🪽 📌с этого дня 10.07.2024. наше название •𝑝𝑟𝑖𝑡𝑜𝑛 𝑎𝑙𝑙𝑖𝑎𝑛𝑐𝑒• запатентован на любых шрифтах и языках, оформление в том числе. прошу понять нас, ведь мы хотим избежать плагиата и копирования. в случае плагиата, вы будете обязаны поменять название и оформление.🌟
Signed Любитель чак чака
😮💨:: можете писать по поводу союзов мне в лс @darling_airis. есть много мест в семейном союзе, так и в дружеских. #репост𝑝𝑟
Signed Любитель чак чака
[ просто я очень рада ] — 𝙡𝙪𝙢𝙞𝙣𝙚 — :: хей, я опоздала на один день, но ничего страшного ~ Моему огромному дитя Комореби уже целых пять месяцев. Я сожалею, что не могу устроить что-то, совсем нет сил.. Я так рада что мы все вместе с вами уже пять месяцев. Время так быстро летит, вот вроде недавно только Миха открыл его вместе со мной, а сейчас я стою перед ста двадцати подписчиков на инфо канале, с двадцатью с ч…
Signed Любитель чак чака
Showing the 12 most recent of 14 posts we hold for @BlueberryLifech. 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.
Named by 3 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“[РЕСТ] Blueberryᶫᶦᶠᵉ” (@BlueberryLifech), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/BlueberryLifech.
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.