Posted without readable text
custom 54001898301203554376👍4😍3

Channel
@park47coffee
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
381subscribers
+26 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001529053609 |
|---|---|
| Type | Channel |
| Username | @park47coffee |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/park47coffee |
Local community — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 12 Sept 2026, 01:55 | 381 | -2 |
| 4 Sept 2026, 02:16 | 383 | +3 |
| 27 Aug 2026, 21:15 | 380 | +5 |
| 21 Aug 2026, 04:13 | 375 | +12 |
| 14 Aug 2026, 18:35 | 363 | +7 |
| 7 Aug 2026, 07:18 | 356 | +1 |
| 6 Aug 2026, 21:04 | 355 | no change |
| 6 Aug 2026, 13:38 | 355 | first reading |
12 posts held, back to 12 July 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 12 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
144 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 34.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 49 | 34.0% | |
| custom 5400189830120355437 | 27 | 18.8% | |
| ❤ | 17 | 11.8% | |
| 👍 | 16 | 11.1% | |
| ❤🔥 | 12 | 8.33% | |
| 😍 | 12 | 8.33% | |
| 🥰 | 5 | 3.47% | |
| 👏 | 4 | 2.78% | |
| custom 5364172032512640299 | 2 | 1.39% |
Custom emoji. 2 of the rows above are 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 are Telegram’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 12 of the 12 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 144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 12 July 2026 to 5 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.
Posted without readable text
custom 54001898301203554376👍4😍3
этот месяц для нас особенный: вместе с кофейней PARK47 будем отмечать день новых черемушек! в программе — дискуссия об истории района вместе с местной жительницей и гидом марией яшкиной, ностальгический dj set от гражданки пятки, а в завершение — музыкальный вечер с исполнением советских песен. ребята также подготовили специальные позиции в меню: фильтр ананас-черемуха и черемуховый торт. зовем увидеться и отметить…
custom 54001898301203554378👍2🔥2
Мы не прощаемся с вами. Позвольте рассказать о нашем новом совместном мероприятии, которое состоится совсем скоро. Мы удивим вас не только масштабами, но и новым взглядом на кофейные напитки
🔥5👏2custom 54001898301203554371
Дорогие друзья! С огромным удовольствием мы завершили нашу дегустацию нового зерна из Исландии. Отбор лучших образцов и создание новых рецептов стали для нас настоящим праздником. Уже завтра вы сможете попробовать все понравившиеся вам лоты на v60 Ждем вас на Архитектора Власова 47
❤🔥6👍4🔥3
Posted without readable text
🔥4custom 54001898301203554373👍2
Друзья! Мы расширяем запись на каппинг! Очень хочется, чтобы нас было больше — невероятный опыт ждёт! Доступно 10 мест, запись по ссылке. Воскресенье 2.08, 15:00, PARK47 на улице Архитектора Власова.
🔥4👍2🥰2custom 54001898301203554371
Вы только посмотрите, какой красивый! Это наш айс-латте с ежевикой, гранатом и лавандой💙 Эспрессо и молоко как отличная база, а на неё - под легким флёром лаванды - отлично ложится сладость ежевики и глубина граната🌸 Подаем с пастилой из боярышника Уже в PARK47 и MINI PARK47
❤🔥4🥰3😍3🔥2custom 54001898301203554371
В следующее воскресенье, 2.08, в PARK47 пройдет каппинг лотов от обжарщика из Исландии! Будем пробовать кофе от KAFFIBRUGGHUSID. Это отличная возможность разделить с нами этот уникальный вкусовой опыт. В конце обязательно поделимся своими мыслями! Участие бесплатное, но нужна регистрация Она доступна по ссылке 2.08, воскресенье, 15:00 Кафе PARK47 на Архитектора Власова, 47
🔥7custom 54001898301203554377👏2
Уимблдонский турнир, Wimbledon — старейший и самый престижный теннисный турнир🎾 Первый турнир был проведен в 1877 году, а в этом — наш спортсмен, Сафиуллин Роман, выиграл третий круг! Мы привезли для вас памятный сувенир. Это кружка с логотипом турнира — отличный подарок для любителя тенниса!✨ Стоимость - 4900₽ Купить её можно у нас, по адресу: ул.Архитектора Власова, 47💙
🔥4❤3😍2
Дорогие гости! Мы знаем, что среди вас очень много талантов! Позвольте вам рассказать — 16 августа в стенах нашей кофейни пройдет камерный вечер акустической музыки…. ….и мы в поисках гитариста! Если вы, так же как и мы, любите живую музыку, играете на гитаре и хотите принять участие в вечере — дайте нам знать! Будем ждать весточки в сообщения канала💙 С любовью, команда PARK47
🔥10❤4😍4
Posted without readable text
❤5🔥5👍2custom 53641720325126402992
Привезли что-то из Нижнего Новгорода! Это лоты на V60 от обжарщика СТРЕЛКА Первый — из Колумбии, экспериментальной обработки от Кристиана Франко. Очень тактильный, характерный кофе с профилем тропическим фруктов и кураги. Второй лот — Кения натуральной анаэробной обработки. Не классическая Кения — здесь, благодаря обработке, темный букет — ежевика, виски, ликер. Оба лота можно попробовать, пока есть зерно, а зерн…
❤5🔥3❤🔥2
Showing the 12 most recent of 12 posts we hold for @park47coffee. 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.
Named by 4 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“PARK47” (@park47coffee), 381 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/park47coffee.
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.