Telegram RegisterThe public register of Telegram

Channel

🥛 БЕЛЫЙ ПРОДАКШН 🥛

@belyproduction

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

150subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002199916487
TypeChannel
Username@belyproduction
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/belyproduction

Growth

1509 Aug 2026, 04:46 — 150 subscribers9 Aug 2026, 15:14 — 150 subscribers9 Aug 2026, 04:469 Aug 2026, 15:14
2 measurements taken within a single day. 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 149–151 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 15:14150no change
9 Aug 2026, 04:46150first reading

Engagement

18 posts held, back to 23 March 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
27.7%
avg views ÷ 150 subscribers
Avg views / post
41.5
2 posts measured
Reaction rate
7.23%
reactions ÷ views · ER floor
Posts in window
2
of 18 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held18 (23 March 20267 August 2026)
Views total83
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 04:46 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.

What this channel posts

Video runtime
1m 53s
Average length
28s

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

99 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 56.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5656.6%
❤‍🔥2020.2%
💔66.06%
💯66.06%
😱55.05%
😍22.02%
🆒11.01%
👍11.01%
🔥11.01%
🫡11.01%

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 18 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 99reactions 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 23 March 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.

Recent posts

7 Aug 2026, 14:54 UTC49 views6 reactionsread 9 August 2026

Сумасшедшая песня, конечно, вышла у Скворушки 🤌🏿 Тайминги сложились так, что Настя пришла к нам с уже очень сильной демкой в тот момент, когда мы левелапались в голове на тему тембров/исходников. Много обсуждали с парнями предыдущую песню «Лихо», подмечали какие-то недочеты для себя, искали улучшения. И в «Лисья» без этого так вкусненько, наверное, не вышло бы. Мы отказались от слепого поиска на Splice, убрали компр

6

7 Aug 2026, 11:38 UTC34 views0 reactionsread 9 August 2026
Forwarded from @prod_by_MOLOKO

SKVORUSHKA - Лисья История, которая вполне могла бы быть сказкой. SKVORUSHKA продолжает погружать нас в мир народных образов, а мы собираем вокруг них современное фолк-звучание. «Лисья» уже на всех площадках. songwrite | vox | idea - SKVORUSHKA prod | rec | mix | master - MOLOKO

28 Jun 2026, 14:19 UTC131 views8 reactionsread 9 August 2026

Я такого на записях не слышал никогда 😍

8

28 Jun 2026, 14:17 UTC124 views8 reactionsread 9 August 2026
Video message

Video message, posted without a caption

💔61🔥1

7 Jun 2026, 16:40 UTC189 views7 reactionsread 9 August 2026
Video message

Video message, posted without a caption

7

28 May 2026, 21:33 UTC149 views8 reactionsread 9 August 2026
Forwarded from @prod_by_MOLOKOVideo

PADL на всех площадках prod, rec, mix, master - MOLOKO music - Денис Кривего, Степан Беленький songwrite, vocal - Степан Беленький back vocal - Анастасия Сергеева gtrs - Екатерина Леонова bass - Андрей Голошумов cover - Денис Кривего, Ульяна Трушина video - Даня Молко, Александра Ковач special thnks - Глеб Ульянов, Дмитрий Троепольский

7👍1

28 May 2026, 21:18 UTC69 views5 reactionsread 9 August 2026
Forwarded from @stbelenkyPhoto

PADL В СЕТИ - СЛУШАТЬ Сторис для продержки ниже, будем рады вашему саппорту! Но главное - послушайте 🥰

❤‍🔥5

25 May 2026, 18:48 UTC104 views7 reactionsread 9 August 2026
Forwarded from @prod_by_MOLOKOVideo

D. Krivego, .belenky - PADL 29.05.26 Presave 🎾

6🆒1

18 May 2026, 18:26 UTC101 views6 reactionsread 9 August 2026
Forwarded from @stbelenky

Короче, я продавал вам аж три дня и немного устал, поэтому без лишних слов D.Krivego, .belenky - PADL 29.05.26 Я буду очень благодарен вашему пресейву! https://band.link/PADL

6

20 Apr 2026, 16:35 UTC152 views5 reactionsread 9 August 2026
Forwarded from @prod_by_MOLOKOPhoto

Мы начинаем новую рубрику «Молочный дайджест», чтобы делиться с вами нашими буднями 🥛 На прошлой неделе мы были продуктивны: 1️⃣ Степа и Аркаша завершили продакшн песни для LIRIANAA. Получилось хорошечно - грустных пианинок поделали, рэпа дали. Все как полагается! 2️⃣ Даня и Степа уже записали вокал для этой песни. Было довольно весело, хотя и не без проблем. Из-за технических сложностей в сжатые сроки записали ме

5

13 Apr 2026, 04:06 UTC114 views3 reactionsread 9 August 2026
Forwarded from @prod_by_MOLOKO

SKVORUSHKA - Лихо Таинственный и кинематографичный фолк 🥀 Дебютный трек для артистки и дебютный проект в жанре фолк для нас. Такой большой и атмосферный звук мы еще не делали, так что рекомендуем к прослушиваю 🥛 Делитесь в комменты, побежали мурашки? 🤭

😍2🫡1

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

Citation-graph rank

Citation-graph rank — 1,063,001 of 1,160,990entries 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.

Forward network

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.

Mentions

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.

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

“🥛 БЕЛЫЙ ПРОДАКШН 🥛” (@belyproduction), 150 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/belyproduction.

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.