Channel
@coffeejazz_home
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
7,605subscribers
+20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001439327301 |
|---|---|
| Type | Channel |
| Username | @coffeejazz_home |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/coffeejazz_home |
Real estate — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 18 Sept 2026, 11:20 | 7,605 | +34 |
| 14 Sept 2026, 13:58 | 7,571 | -2 |
| 11 Sept 2026, 02:15 | 7,573 | +2 |
| 5 Sept 2026, 20:01 | 7,571 | -8 |
| 29 Aug 2026, 11:28 | 7,579 | -1 |
| 26 Aug 2026, 21:55 | 7,580 | -3 |
| 24 Aug 2026, 04:36 | 7,583 | +8 |
| 20 Aug 2026, 09:34 | 7,575 | +31 |
| 17 Aug 2026, 12:13 | 7,544 | -19 |
| 14 Aug 2026, 07:27 | 7,563 | -13 |
| 11 Aug 2026, 06:31 | 7,576 | -8 |
| 7 Aug 2026, 23:16 | 7,584 | -1 |
| 7 Aug 2026, 20:45 | 7,585 | no change |
| 7 Aug 2026, 20:37 | 7,585 | first reading |
8 posts held, back to 21 June 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 15 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 8 posts for this entry, the most recent from 18 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
276 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 64.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 179 | 64.9% | |
| 🔥 | 60 | 21.7% | |
| 👏 | 28 | 10.1% | |
| 🥰 | 9 | 3.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 8 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 276 reactions 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 21 June 2026 to 18 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.
ЖК Руставели 14, ПИК Часть 2 - кухня-гостиная 33 м², в которых мы не побоялись цвета 💗💙 Спокойную светлую базу мы специально разбавили цветом: голубым, розовым, сиреневым, немного насыщенного синего. Добавили необычный свет, искусство, фактуры и декор — и типовая отделка перестала выглядеть типовой. Для меня этот проект — хороший пример того, что дизайн начинается не с дорогого ремонта и демонтажа всего от застрой…
❤17🔥7👏4
ЖК Руставели 14, ПИК Часть 1 - спальня, ванна 33 м², в которых мы не побоялись цвета 💗💙 Этот проект мы создавали для молодой девушки - и хотелось, чтобы квартира получилась такой же: лёгкой, яркой, немного ироничной и очень живой. Исходные данные — квартира 33 м² с готовой чистовой отделкой от ПИК. Поэтому нашей задачей было не переделывать всё с нуля, а грамотно доработать базу от застройщика и за счёт мебели, св…
❤24🥰6👏4
Видео обзор проекта в Level Стрешнево 45 кв м С бетона Для аренды Полезные ссылки и цены: • Кухня, каменная столешница, шкаф в спальне + стеллаж и рабочий сто, шкаф в коридор, вся мебель в ванной - на заказ 870 тыс • Мойка на кухню - 30 тыс • Смеситель на кухню - 8 тыс • Стол круглый 95 см - 40 тыс • Гобелен от братьев Либа - 30 тыс • ТВ тумба озон - 18 тыс • Диван Биани - 89 тыс • Кровать Далти - 71 тыс • Матра…
❤18👏8🔥8
ЖК Level Стрешнево Проект для аренды Площадь 45 кв м Часть 2 - спальня, коридор, санузел Данный объект мы вели с бетона. Фото ДО можно увидеть здесь. Этот проект мы вели полностью от и до — от черновых работ до финальной фотосессии. На нашей стороне была вся реализация: инженерия, черновая и чистовая отделка, электрика, сантехника, кондиционирование, мебель на заказ, комплектация, текстиль и декор. Заказчики пол…
🔥19❤12👏2
ЖК Level Стрешнево Проект для аренды Площадь 45 кв Часть 1 - кухня-гостинная Данный объект мы вели с бетона. Фото ДО можно увидеть здесь. Задача: Заказчики попросили создать интерьер с большим количеством «воздуха» и ощущением визуально свободного пространства. Поэтому вместо глухой межкомнатной стены мы сделали лофт-перегородку. Она сохранила естественный свет, визуально объединила пространство и при этом позво…
❤20🔥7👏2
В один день у нас были финалы двух проектов! Первый проект - ЖК Амурский парк, 50 кв для жизни молодой семьи с малышкой. Второй проект - ЖК Ильинойс, 40 кв для жизни молодой девушки. Самое бесценное - это эмоции наших заказчиков. Люблю и ценю каждого ♥️
❤38🔥9👏1
Спойлеры нового проекта … ЖК Ярославский 35 кв для жизни Невероятно красивый проект для жизни молодой девушки, которая, кстати, является медийным лицом в Москве. Интерьер получился стильный, но по домашнему теплый и уютный. Главный акцент квартиры - это фартук в цвете бургунди ♥️
❤33🔥10👏2
📍Новый проект в Петербурге ЖК «Сенат» Студия 25 м² Квартиру заказчица приобрела для сдачи в аренду, но с перспективой проживания самой. Поэтому наша задача - создать интерьер, который будет актуален долгие годы. Меня искренне впечатлил ЖК и закрытый двор: много зелени, продуманное зонирование, прогулочные маршруты и велодорожки, спортивные и детские площадки. Здесь хочется не просто жить, а проводить время вне кв…
❤17👏5🥰3
Showing the 8 most recent of 8 posts we hold for @coffeejazz_home. 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 3 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Coffeejazz Home” (@coffeejazz_home), 7,605 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/coffeejazz_home.
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.