я снова в питере решила поступать в магистратуру, готовлюсь к вступительным активно хочу в итмо🤓
custom 545873931392572306117custom 54563419877351506299custom 54566200353279559265

Channel
@bubiknoise
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
316subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003316096556 |
|---|---|
| Type | Channel |
| Username | @bubiknoise |
| Created | Between 1 November 2025 and 28 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bubiknoise |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 07:34 | 316 | no change |
| 7 Aug 2026, 18:15 | 316 | first reading |
7 posts held, back to 17 July 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 7 (17 July 2026 – 7 August 2026) |
| Views total | 1,683 |
| Reactions total | 157 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07:34 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 8 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.
157 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 58.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5458739313925723061 | 91 | 58.0% | |
| custom 5456341987735150629 | 50 | 31.8% | |
| custom 5456620035327955926 | 16 | 10.2% |
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 areTelegram’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 7 of the 7 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 157reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 17 July 2026 to 7 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.
я снова в питере решила поступать в магистратуру, готовлюсь к вступительным активно хочу в итмо🤓
custom 545873931392572306117custom 54563419877351506299custom 54566200353279559265
мир так прекрасен займусь ка я программным обеспечением радиоэлектронных средств
custom 545634198773515062924custom 54587393139257230616
интервью со мной😇
custom 545662003532795592610custom 54587393139257230615
В Лаборатории электричество — ключевой материал для исследования звука, а у каждого инженера — свой способ работать с ним. Мы поговорили с тремя инженерами ЛЭЗ, чьи подходы к разработке устройств заметно отличаются друг от друга. Полина Филиппова собирает синтезаторы и микрофоны своими руками, от макетной платы до печатной. Сергей Суховик склоняется к художественной стороне процесса, свои устройства часто привязывае…
custom 545873931392572306114
сейчас такие дела
custom 545634198773515062917
первый день лета
custom 545873931392572306128custom 54566200353279559261
Video message, posted without a caption
custom 545873931392572306121
Showing the 7 most recent of 7 posts we hold for @bubiknoise. 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“бубик и маленькие шумы” (@bubiknoise), 316 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/bubiknoise.
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.