Telegram RegisterThe public register of Telegram
Telegram profile photo for Бустер Нарезки

Channel

Бустер Нарезки

@NarezkiBuster

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

8,663subscribers

-269 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003306145614
TypeChannel
Username@NarezkiBuster
Created16 February 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live29 October 2026
Measurements held22
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/NarezkiBuster

Topic

Marketing & affiliate — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

8,6639,1448,903.57 August 2026 — 8,932 subscribers7 August 2026 — 8,932 subscribers8 August 2026 — 8,942 subscribers10 August 2026 — 9,033 subscribers14 August 2026 — 9,079 subscribers17 August 2026 — 9,123 subscribers20 August 2026 — 9,144 subscribers24 August 2026 — 9,000 subscribers27 August 2026 — 8,976 subscribers2 September 2026 — 8,971 subscribers6 September 2026 — 8,953 subscribers11 September 2026 — 8,964 subscribers14 September 2026 — 8,972 subscribers25 September 2026 — 8,941 subscribers4 October 2026 — 8,844 subscribers11 October 2026 — 8,791 subscribers14 October 2026 — 8,787 subscribers17 October 2026 — 8,767 subscribers20 October 2026 — 8,747 subscribers23 October 2026 — 8,720 subscribers26 October 2026 — 8,692 subscribers29 October 2026 — 8,663 subscribers7 August 202629 October 2026
22 measurements spanning 83 days, net -269. 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 8,591–9,216 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
29 Oct 2026, 21:188,663-29
26 Oct 2026, 14:368,692-28
23 Oct 2026, 09:368,720-27
20 Oct 2026, 08:518,747-20
17 Oct 2026, 13:418,767-20
14 Oct 2026, 22:108,787-4
11 Oct 2026, 20:018,791-53
4 Oct 2026, 21:428,844-97
25 Sept 2026, 07:178,941-31
14 Sept 2026, 23:588,972+8
11 Sept 2026, 13:388,964+11
6 Sept 2026, 23:578,953-18
2 Sept 2026, 05:288,971-5
27 Aug 2026, 04:048,976-24
24 Aug 2026, 07:349,000-144
20 Aug 2026, 23:539,144+21
17 Aug 2026, 15:479,123+44
14 Aug 2026, 00:189,079+46
10 Aug 2026, 21:189,033+91
8 Aug 2026, 07:248,942first reading

Engagement

15 posts held, back to 16 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 30 pages 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 15 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 51s
Average length
17s

Measured directly from 10 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

2,320 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 65.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,52165.6%
🤪36815.9%
👍24210.4%
🏆1898.15%

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

Measured over the 15 most recent posts we hold, published 16 February 2026 to 22 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.

Recent posts

22 Aug 2026, 12:53 UTC≈4,360 views55 reactionsread 28 August 2026

Здравия желаю 🫡 Форма для подачи заявки для попадания в команду нарезчиков 🙏 https://forms.gle/QN31DM8mPxcmnmKX8

🤪34👍12❤7🏆2

21 Aug 2026, 13:42 UTC≈5,750 views102 reactionsread 28 August 2026

Здравия желаю 🫡 Выплаты за нарезки не продлеваются, 31.08 последний день для подачи видео на выплату. Но есть шанс остаться в команде, в эти последние дни будем наблюдать и отберем несколько ребят на постоянную основу Главное правило: 🟢Канал должен быть посвящен Славе (аватарка + название канала должны быть связаны с Бустером, нейтральные тоже не пройдут) Посты о выплатах скоро будут 🙏

🤪79❤17👍6

31 Jul 2026, 17:42 UTC≈16,400 views85 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 22.07 (включительно) - были оплачены 💰 Следующая выплата будет за период 23.07- 05.08 (включительно) Обновлен список правил ❗️

❤69🏆7👍7🤪2

19 Jul 2026, 15:31 UTC≈17,900 views70 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 08.07 (включительно) - были оплачены 💰 Следующая выплата будет за период 09.07- 22.07 (включительно)

❤55👍9🏆6

3 Jul 2026, 12:21 UTC≈20,100 views93 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 24.06 (включительно) - были оплачены 💰 Следующая выплата будет за период 25.06- 08.07 (включительно) 🗓

❤70🏆12👍7🤪4

16 Jun 2026, 14:27 UTC≈20,500 views114 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 11.06 (включительно) - были оплачены 💰 Следующая выплата будет за период 12.06- 24.06 (включительно) 🗓 ‼️ ПРОДЕЛЕВАЕМ ВЫПЛАТЫ ДО 01.09 😱

❤88👍11🤪8🏆7

2 Jun 2026, 14:51 UTC≈21,000 views65 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 28.05 (включительно) - были оплачены 💰 Следующая выплата будет за период 29.05- 11.06 (включительно) 🗓

❤38👍15🤪11🏆1

28 May 2026, 19:19 UTC≈21,100 views82 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 14.05 (включительно) - были оплачены 💰 Ближайшие выплаты будут за периоды 15.05-28.05 включительно 🗓 и 29.05- 11.06 включительно 🚀 По всем вопросам — в лс @f00rsberg

❤63👍12🏆7

23 Apr 2026, 12:55 UTC≈26,400 views95 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 16.04 (включительно) - были оплачены 💰 Следующая выплата будет за период 17.04-30.04 🗓 🚀 По всем вопросам — в лс @f00rsberg

🏆54❤31👍9🤪1

5 Apr 2026, 12:25 UTC≈27,700 views103 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 02.04 (включительно) - были оплачены 💰 Следующая выплата будет за период 03.04-16.04 🗓 🚀 По всем вопросам — в лс @f00rsberg

❤80🏆14👍9

23 Mar 2026, 16:43 UTC≈31,100 views100 reactionsread 28 August 2026
Video

Здравия желаю 🫡 Видео отправленные на выплату до 19.03 (включительно) - были оплачены 💰 Не забывайте что видео опубликованные с 20.03 попадают под новые выплаты 💵 🚀 По всем вопросам — в лс @f00rsberg

❤74🏆18👍8

18 Mar 2026, 15:52 UTC≈48,800 views265 reactionsread 28 August 2026

ТЕСТОВЫЙ МЕСЯЦ ПОДХОДИТ К КОНЦУ, НО ЭТО НЕ ВСЕ 🚨 ПРОДЛЕВАЕМ НА 3 МЕСЯЦА (до 20.06) ТАК ЖЕ ПОДНИМАЕМ ВЫПЛАТЫ 😳 ❗️Новая стоимость просмотров: 100к+ — 20$ 250к+ — 30$ 500к+ — 60$ 1млн+ — 120$ (Просмотры не суммируются) (для видео опубликованных с 20.03) ВСЕМ УДАЧИ МУЖЧИНЫ 🫡 🚀 По всем вопросам — в лс @f00rsberg

❤201👍36🏆19🤪9

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

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

“Бустер Нарезки” (@NarezkiBuster), 8,663 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/NarezkiBuster.

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.