Channel
@lukdnb
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
59subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001342344262 |
|---|---|
| Type | Channel |
| Username | @lukdnb |
| Description | Звук как система и состояние. Game audio, интерактивная музыка, DJ-мышление. 🎧 Звук, который работает 🎮 Музыка и саунд-дизайн для игр, брендов и медиа 🎹 Аудио реклама · интерактивная музыка · подкасты 🔥 Drum & Bass producer & DJ |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lukdnb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 05:46 | 59 | no change |
| 7 Aug 2026, 18:38 | 59 | first reading |
8 posts held, back to 25 May 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 pageof 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 8 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
8 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5204426187136313032 | 3 | 37.5% | |
| custom 5408995187387015251 | 2 | 25.0% | |
| custom 5425089619551067771 | 2 | 25.0% | |
| custom 5341350410252723241 | 1 | 12.5% |
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 5 of the 8 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 25 May 2026 to 15 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.
Складываем пазлы фестивальных лайнапов, где можно увидеть наших именитых артистов: 🎸 Живая сцена 🥁 Drum’n’bass night 🪩 2000 hits 🧘 Chill out ⚙️ Mono stage 🕉️ Teleport 💃 R59 Билеты: https://qtickets.ru/event/243065
custom 52044261871363130321
17 июля. Я, NON GRATA И KORT раздаем Drum & Bass на PARMA VALLEY 2026
custom 53413504102527232411
Всем привет ) Осталось совсем немного, если ты еще без билета, переходи по ссылке и участвуй в розыгрыше - https://vk.ru/wall-174211750_20174 А так же в розыгрыше сертификаты «Вмясо» и «13/69», а еще фирменные футболки Parma Valley!
Новый релиз на нашем подлейбле BASS PLANTERS. Сингл от TIJA. Слушаем на всех платформах. ССЫЛКИ. 👈
custom 54089951873870152511
Было очень круто!!! 🔥 Спасибо всем, кто был этой ночью. Было по-настоящему жарко! 😎❤️
custom 52044261871363130321
Таймтейбл завтрашнего мероприятия 29 мая 2026 DRUM & BASS PARTY от NEGATIVE SOUND. Место проведения - Клуб СТУДИЯ, Сибирская 17. Дешёвый билет можно купить у NIGOLAZZ по 500 для владельцев мерча и 700 для остальных. На входе будет дороже! 23:00 KRAWTZMANN 00:00 NON GRATA 01:00 SLA JA 02:00 LUK 03:00 JULLY FEEL 04:00 KORT Спонсор мероприятия - ЯВИ - Объединённый сервис для видеовстреч.
Мероприятие уже в эту пятницу - 29 мая. Дешёвые билеты ещё есть у https://t.me/Nigolazz по 700, для владельцев мерча по 500 и на входе цена будет выше, если останутся места. Место проведения - клуб Студия, Сибирская 17. Старт в 23:00. Как это было в прошлый раз можно посмотреть тут https://vk.ru/wall6288570_31553
custom 54250896195510677712custom 52044261871363130321custom 54089951873870152511
Мероприятие уже в эту пятницу 29 мая. Выкладываем место - клуб СТУДИЯ, Сибирская 17. В клубе есть бар с алкогольными и безалкогольными напитками. Пиво, фирменные коктейли и крепкий алкоголь. Оплата картой и наличными. Барная зона отдельно от танцпола. Билеты на мероприятие можно приобрести у NIGOLAZZ по 700. Для владельцев мерча по 500. Пожалуйста приобритайте билеты заранее. Так Вы гарантированно попадёте на меро…
Showing the 8 most recent of 8 posts we hold for @lukdnb. 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“luk | sound & systems” (@lukdnb), 59 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/lukdnb.
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.