Channel
@ZzburoDesign
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
597subscribers
+25 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001793822172 |
|---|---|
| Type | Channel |
| Username | @ZzburoDesign |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/ZzburoDesign |
Art & design — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 06:36 | 597 | +3 |
| 30 Sept 2026, 07:42 | 594 | +7 |
| 15 Sept 2026, 09:19 | 587 | -1 |
| 30 Aug 2026, 01:33 | 588 | +7 |
| 22 Aug 2026, 22:58 | 581 | +7 |
| 15 Aug 2026, 01:13 | 574 | +2 |
| 7 Aug 2026, 06:32 | 572 | no change |
| 7 Aug 2026, 06:24 | 572 | first reading |
3 posts held, back to 20 April 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 3 posts for this entry, the most recent from 25 June 2026. An engagement rate over an empty window would be a number about nothing.
47 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 70.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 33 | 70.2% | |
| 🔥 | 8 | 17.0% | |
| 👍 | 4 | 8.51% | |
| 🥰 | 2 | 4.26% |
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 3 of the 3 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 47 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 20 April 2026 to 25 June 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
Добрый день, подписчики. Смотрите, как у нас красиво интерьер на Зиларте собирается. Мы полностью ведем этот объект, от первичного обмера в бетоне, создания идеи-концепции, подготовки строительной документации, выхода на стройку, ее сопровождения, закупки материалов и мебели до финального клининга и передачи ключей от готовой квартиры заказчикам. Если вы хотите для себя такой же сервис, напишите нам. Мы сейчас форм…
❤18🥰2
Добрый день. Предлагаю сегодня повышать насмотренность вместе. Сегодня спальни. И все эти спальни придумали дизайнеры нашего бюро. Что тут интересного модно увидеть: 1. Цвета. Все гармонично, но и ярко в то же время 2. Текстуры, можем смело сочетать разные материалы, это добавляет условного «конфликта» в интерьер, что создает «глубину» и сложность пространству. А следовательно, результат выглядит дороже, чем просты…
❤15🔥4
Showing the 3 most recent of 3 posts we hold for @ZzburoDesign. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“ZZBURO Дизайн интерьеров.” (@ZzburoDesign), 597 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/ZzburoDesign.
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.