Telegram RegisterThe public register of Telegram
Telegram profile photo for Бутылка мусора 🎰

Channel

Бутылка мусора 🎰

@buffle_ff

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

72subscribers

+7 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002557658152
TypeChannel
Username@buffle_ff
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 16 September 2026
On Telegramt.me/buffle_ff

Growth

6573698 August 2026 — 65 subscribers10 August 2026 — 65 subscribers14 August 2026 — 72 subscribers22 August 2026 — 73 subscribers29 August 2026 — 71 subscribers8 September 2026 — 72 subscribers728 August 20268 September 2026
6 measurements spanning 31 days, net +7. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 64–74 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 03:1972+1
29 Aug 2026, 01:4871-2
22 Aug 2026, 12:2773+1
14 Aug 2026, 22:3872+7
10 Aug 2026, 02:4665no change
8 Aug 2026, 03:4665first reading

Engagement

17 posts held, back to 17 April 2026the 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 17 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 15s
Average length
1m 08s

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.

Reaction mix

262 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 44.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 532819188029326736411744.7%
5621.4%
❤‍🔥4617.6%
🔥218.02%
😢176.49%
💯51.91%

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 17 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 262 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 17 April 2026 to 27 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 17 we hold a reading for · 12%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @buffle_ff. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 17 most recent posts we hold for this entry, published 17 April 2026 to 27 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

27 Jul 2026, 17:27 UTC75 views16 reactionsread 10 August 2026
Photo

One more простенький гифт

❤‍🔥16

12 Jul 2026, 11:55 UTC144 views14 reactionsread 10 August 2026
Photo

NOW It's your turn

custom 53281918802932673648🔥42

7 Jul 2026, 11:20 UTC173 views13 reactionsread 10 August 2026
Photo

Короче превращать этот канал в стримы не буду поэтому кому интересно инфа будет там @buffle_f

custom 532819188029326736413

6 Jul 2026, 20:15 UTC175 views17 reactionsread 10 August 2026
Video

ВЫХВЫВХ СМОТРИТЕ КАКОЙ ХАЙП СДЕЛАЛА

🔥14custom 53281918802932673643

4 Jul 2026, 09:45 UTC183 views12 reactionsread 10 August 2026
Photo

ОНО ДОМА!! Я просто невероятно рада я так их ждала это просто лучшее что случалось со мной за последнее время Мне никогда не отправляли посылки которые прям от рук тех людей и спасибо огромное @RACCOONVILL и @ktotoeshee за такую имбу вы просто лучшие

❤‍🔥12

3 Jul 2026, 16:32 UTC149 views12 reactionsread 10 August 2026
Photo

Fears to fathom и подобные игры такие типа:

❤‍🔥9custom 532819188029326736421

27 Jun 2026, 16:32 UTC≈1,190 views21 reactionsread 10 August 2026
Photo

Vsem privet Это гифтик моему любимому бро @RACCOONVILL Ты лапочка

18🔥3

25 Jun 2026, 12:46 UTC166 views20 reactionsread 10 August 2026
File

КОЛЛЕДЖ ВСЕ!! Точнее я наконец сдала практику, портфолио и экзамены. Теперь и я могу поздравить с первым днем лета и началом каникул, до этого дня кстати лета не было

custom 532819188029326736414❤‍🔥51

15 Jun 2026, 15:16 UTC317 views17 reactionsread 10 August 2026
Photo

Короче не гнобите пж я впервые занимаюсь чем-то подобным и за пару часов наваляла аву для майнкрафт сервера моих друзей @ourworlds2 Кстати реально мб кому-то будет интересно там говорят крутая сборочка будет🤙🤙

14❤‍🔥3

28 May 2026, 21:01 UTC238 views20 reactionsread 10 August 2026
Photo

Вы не ждали я приперся

custom 532819188029326736416💯4

20 May 2026, 17:08 UTC252 views16 reactionsread 10 August 2026
Photo

Буэээ короче у меня умер ссд и то что я рисовала ушло вместе со всеми файлами

😢16

8 May 2026, 13:35 UTC247 views22 reactionsread 10 August 2026
Photo

Ну лааадно так уш и быт пора рисовать да?

custom 532819188029326736420❤‍🔥1💯1

Showing the 12 most recent of 17 posts we hold for @buffle_ff. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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.

Cite this entry

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 September 2026 — this entry's latest reading, not the date you are reading this.

“Бутылка мусора 🎰” (@buffle_ff), 72 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/buffle_ff.

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.