Channel
@yabuket
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
1,810subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002491481594 |
|---|---|
| Type | Channel |
| Username | @yabuket |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/yabuket |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 22:14 | 1,810 | +2 |
| 24 Aug 2026, 18:57 | 1,808 | -3 |
| 20 Aug 2026, 17:15 | 1,811 | +2 |
| 17 Aug 2026, 11:17 | 1,809 | +1 |
| 13 Aug 2026, 11:57 | 1,808 | -2 |
| 10 Aug 2026, 21:02 | 1,810 | -4 |
| 7 Aug 2026, 05:31 | 1,814 | no change |
| 7 Aug 2026, 05:18 | 1,814 | first reading |
9 posts held, back to 5 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 2 pagesof 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 6 August 2026 |
|---|---|
| Posts held | 9 (5 August 2026 – 6 August 2026) |
| Views total | 1,269 |
| Reactions total | 85 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:28 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.
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.
85 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 27.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5460984027043348122 | 23 | 27.1% | |
| custom 5195338074992688290 | 17 | 20.0% | |
| custom 5312413944269268597 | 15 | 17.6% | |
| custom 5325879839268299226 | 8 | 9.41% | |
| custom 5357449828873823721 | 7 | 8.24% | |
| custom 5384192060490274511 | 7 | 8.24% | |
| custom 5433798159664949452 | 6 | 7.06% | |
| custom 5197571694209817065 | 2 | 2.35% |
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 9 of the 9 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 85reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 5 August 2026 to 6 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 546098402704334812210custom 54337981596649494526custom 51953380749926882905
Вы наверное уже спите…🥱💤 (А мы нет🤭) Но… не показать Вам такое роскошество мы просто не можем 🧡💚💖 💓💓💓💓💓💓📎
custom 51953380749926882907custom 54609840270433481224custom 53124139442692685973
УГАДЫВАЕМ ЦВЕТ💌
The shares total 119%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
custom 53258798392682992262
Снова большая корзина и снова после нашего рабочего дня 🙂 Но мы так обожаем делать вас счастливыми, что для нас это в радость 💕
custom 53258798392682992262
Video message, posted without a caption
custom 53258798392682992262
💗💗💗 💗💗💗💗 Есть букеты, к которым возвращаются снова и снова 🩷 Именно они стали Вашими фаворитами за июль! 🎀 Мы собрали их в одной подборке, чтобы вдохновить Вас и, возможно, помочь найти «тот самый» букет! 🤩А если какой-то из них особенно запал Вам в сердце — с удовольствием повторим его, бережно собрав с тем же настроением и любовью. ❤️Для заказа: @privet_ya_buket_bot
custom 51953380749926882905custom 53124139442692685973custom 53841920604902745112
С этими цветами получаются невероятные фреш-букеты ❤️ 🌸гладиолусы — вытянутые, эффектные и с огромным выбором оттенков 🤩 георгины — звёздочки августа: от нежных пастельных до глубоких и насыщенных 🤩подсолнухи — чтобы добавить в дом немного солнца даже в самый обычный день 🤩и самое приятное — каждый из них совершенно разный, поэтому подобрать цветы можно под любой интерьер и настроение. ⭐️📨📨📨📨 если тоже любите соби…
custom 53574498288738237217custom 53258798392682992261
🎉 Результаты розыгрыша: 🏆 Победитель: 1. Наталия (@Af_Nataly) ✔️Проверить результаты
custom 54609840270433481229custom 53841920604902745112custom 53258798392682992261
Video message, posted without a caption
custom 53124139442692685979custom 53841920604902745113custom 51975716942098170652
Showing the 9 most recent of 9 posts we hold for @yabuket. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
УГАДЫВАЕМ ЦВЕТ💌
The shares total 119%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 9 most recent posts we hold, published 5 August 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 1,021,571 of 1,626,935entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“YABUKET | Цветы Самара” (@yabuket), 1,810 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/yabuket.
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.