Channel
@ludidobrie_production
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
62subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001474746307 |
|---|---|
| Type | Channel |
| Username | @ludidobrie_production |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ludidobrie_production |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 04:59 | 62 | -1 |
| 31 Aug 2026, 10:48 | 63 | +1 |
| 10 Aug 2026, 04:00 | 62 | no change |
| 7 Aug 2026, 11:18 | 62 | first reading |
10 posts held, back to 16 March 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 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 10 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 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.
115 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 25.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 29 | 25.2% | |
| 🔥 | 24 | 20.9% | |
| ❤ | 16 | 13.9% | |
| 🥰 | 12 | 10.4% | |
| ⚡ | 11 | 9.57% | |
| 👍 | 11 | 9.57% | |
| 😎 | 6 | 5.22% | |
| 🤩 | 3 | 2.61% | |
| 💔 | 2 | 1.74% | |
| 💯 | 1 | 0.87% |
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 10 of the 10 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 115 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 16 March 2026 to 4 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.
Вместе с Марком Клубом собрались, чтобы обсудить, куда сегодня движется контент, как выстраивать производство так, чтобы оно приносило результат, а не просто съедало бюджет и какие идеи уже хочется нести в работу. Любим такие встречи за живой разговор, обмен опытом и людей, которые так же горят своим делом. Спасибо каждому, кто был с нами ❤️
❤🔥4🔥4👍3
В этом году мы стали партнерами проекта MAD Architects, который был одной из точек притяжения на главной архитектурной выставке страны. Смотрите кадры — они лучше любых слов передают атмосферу АРХ МОСКВЫ 2026.
❤🔥3👍2💔2🔥2
Каждый классный результат начинается с процесса. Показываем вам не только финальное видео, но и то, сколько стараний, внимания и творчества стоит за каждым этапом работы над проектом.
❤3❤🔥3👍3⚡1
Отсняли крутой проект с @samokatwithlove и теперь с удвоенной энергией продолжаем съемки.
❤🔥4⚡3🔥2
Стоп! Забудьте про скучные семейные застолья в рекламе. У нас все по‑честному: cочное мясо, жар углей, смех друзей. Лето по‑сибирски — пожарь, откуси, повтори. В новой кампании для сибирского бренда мясных продуктов сделали ставку на драйв и эмоции: молодежная атмосфера, живые моменты у мангала и аппетитный продукт, который хочется попробовать немедленно. Чтобы усилить визуал, использовали ИИ: сгенерировали динамич…
😎4❤🔥3🔥3
Осторожно, высокая степень аппетитности! Мы создали рекламу шницеля мечты: хрустящая корочка, сочная середина, идеальный золотистый оттенок. Гарантированно вызывает желание бросить все и бежать на кухню.
❤🔥4⚡3😎2👍1💯1🤩1
Последнее время снимаем много и по-настоящему «вкусно» 🔥 Что не менее важно, кайфуем от процесса и результата. Пока не все можно показывать целиком, делимся съемочным процессом.
⚡4❤🔥3🥰3👍2🤩2🔥1
«Мужчины тоже плачут». И иногда из-за хорошей рекламы. Совместно с «Мистраль» реализовали нейросетевой ролик для бренда «Амца». Прошли путь от идеи до готового видео в максимально сжатые сроки, без потери качества и креативной идеи. Гордимся результатом вместе, так получился еще один наш кейс на Sostav ➡️ *клик*
❤5🔥5🥰5
Хотим показать вам кусочек внутрянки проекта для @selectelcareers, над которым мы работали. Столько всего остается за кадром, что жалко не поделиться.
🔥4🥰4❤3
С удовольствием делимся закулисьем проекта, над которым работали этой зимой. Снимали ролик о докторской колбасе — и честно, удержаться от дегустации было настоящим подвигом 🤪
❤5❤🔥5🔥3
Showing the 10 most recent of 10 posts we hold for @ludidobrie_production. 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.
Named by 2 registered channels — 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Люди Добрые Production” (@ludidobrie_production), 62 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ludidobrie_production.
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.