друзья, у Саши возникли некоторые проблемы с телефоном на неопределённый период, так что контент выкладывать она временно не сможет🌟
👀15🍓3💋2
Signed lita

Channel
@bugagashki11
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
57subscribers
-109 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004307261233 |
|---|---|
| Type | Channel |
| Username | @bugagashki11 |
| Created | Between 1 June 2026 and 15 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/bugagashki11 |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 11:04 | 57 | +1 |
| 3 Nov 2026, 12:08 | 56 | -108 |
| 14 Sept 2026, 12:41 | 164 | -1 |
| 12 Sept 2026, 18:22 | 165 | no change |
| 6 Sept 2026, 09:17 | 165 | -5 |
| 21 Aug 2026, 23:18 | 170 | +1 |
| 14 Aug 2026, 20:58 | 169 | +3 |
| 13 Aug 2026, 18:04 | 166 | first reading |
18 posts held, back to 15 August 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 18 posts for this entry, the most recent from 6 September 2026. An engagement rate over an empty window would be a number about nothing.
579 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 28.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5244790551777147233 | 166 | 28.7% | |
| 🍓 | 160 | 27.6% | |
| 👀 | 99 | 17.1% | |
| 💋 | 58 | 10.0% | |
| 🍾 | 51 | 8.81% | |
| 🙉 | 33 | 5.70% | |
| 🆒 | 12 | 2.07% |
Custom emoji. One 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 count beside it is 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 17 of the 18 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 579 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 15 August 2026 to 6 September 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.
друзья, у Саши возникли некоторые проблемы с телефоном на неопределённый период, так что контент выкладывать она временно не сможет🌟
👀15🍓3💋2
Signed lita
Video, posted without a caption
Ребята, тейк писала НЕ Я!! Не ведитесь, пожалуйста
🍓7
Я возможно поменяю ник на Финики,не теряйте Неанон Бугагашка #тейк
👀6
Следующий, скорее всего сегодняшний хэдканон со взрослыми неудачниками будет именно под эту песню. 🌟
🙉10🍓5custom 52447905517771472334
ты умрёшь кстати
👀9🍓3🍾3💋2
Signed lita
Дорогие, сейчас у меня выпускной класс, нужно гораздо больше стараться, готовиться к ОГЭ и прочее, поэтому, скорее всего хэдканоны будут лишь раз, ну, может два раза в неделю ;(( Мне сильно нужно подтянуть несколько предметов для хорошего аттестата и будущего поступления. Время будет уходить в основном на учёбу, ведь я боюсь, что просто ничего не сдам. Учица буду фу.
🍓25💋12🍾10👀2🙉1
🔐 || Небольшой спойлер. о-оу, кто же это у нас тут.. да это ведь сама бугагашка. в общем, мои хорошие, я выхожу из реста. снова с вами!! надеюсь, актив не сильно упадёт..
custom 524479055177714723332🍓12👀10🆒1
У меня тут щп свой появился
🍾6🙉5🍓4
🔐 || Небольшой спойлер ну.. страдать будут все. в ближайшее время веселого контента не ждите. если кто не понял, этот хэдканон что-то по типу тренда в тик токе "последние счастливые 7 минут перед смертью"
👀26🍓15custom 524479055177714723314💋1
🔐 || Небольшой спойлер подошла наша чудесная рубрика к концу. финальным дуо оказались Майк и Лукас. надеюсь, что эта, последняя часть залетит, а то с прошлым дуо не задалось ;((
custom 524479055177714723316🍓11💋8
🔐 || Небольшой спойлер а вот и дуо, к которому была отсылка в прошлой части!! Реджинальд и Нэнси - это, конечно, мило.. но вот только хэдканон будет не особо то весёлым. будет грустно.
👀13🍓8🙉7🆒3
Showing the 12 most recent of 18 posts we hold for @bugagashki11. 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.
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 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“𝗯𝘂𝗴𝗮𝗴𝗮𝘀𝗵𝗸𝗶 :𝗗” (@bugagashki11), 57 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/bugagashki11.
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.