Channel
@nastyaprocoffee
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
492subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002041162766 |
|---|---|
| Type | Channel |
| Username | @nastyaprocoffee |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/nastyaprocoffee |
Travel — 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 96% 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 |
|---|---|---|
| 15 Sept 2026, 11:18 | 492 | +3 |
| 7 Sept 2026, 12:40 | 489 | -4 |
| 29 Aug 2026, 03:43 | 493 | -3 |
| 22 Aug 2026, 20:18 | 496 | -2 |
| 15 Aug 2026, 01:38 | 498 | -5 |
| 8 Aug 2026, 04:17 | 503 | no change |
| 7 Aug 2026, 14:31 | 503 | first reading |
3 posts held, back to 6 August 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
29 reactions across 3 posts, in 8 distinct kinds. The most used accounts for 31.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 9 | 31.0% | |
| ❤🔥 | 6 | 20.7% | |
| 🍓 | 5 | 17.2% | |
| ⚡ | 3 | 10.3% | |
| 🥰 | 3 | 10.3% | |
| custom 5233651227677433290 | 1 | 3.45% | |
| 💯 | 1 | 3.45% | |
| 😍 | 1 | 3.45% |
Custom emoji. One 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 count beside it is 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 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 29 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 6 August 2026 to 7 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.
Не могла не воспользоваться 1,5часовой остановкой в Минске поезда Гродно-Москва - как раз у ж/д вокзала есть кофейня 26 ☕️ Есть кофейные места, в которые я уже по традиции за захожу каждый визит в Минск и эта одна из них, с удобным месторасположением Очень вкусный авторский колбрю с лимонным молоком и прихватила с собой несколько дрипов от Single Step 🌸
🔥5❤🔥4🍓1custom 52336512276774332901
Гродно туристический 🇧🇾 Что успеть посмотреть за один день? • Площадь Ленина - начало маршрута, здесь же администрация города, памятник Ленину и нулевой километр • Советская улица - центральная пешеходная улица, по пути много магазинов и кафе с белорусской кухней, в здании ЦУМа расположилась смотровая площадка • Костёл святого Франтишка Ксаверия - католический храм на Советской площади • Старый замок - историчес…
⚡3❤🔥2💯1🔥1😍1
Прогуливаясь по центру, была найдена еще одна кофейня в арке на Советской площади - Sправа 🇧🇾 Минимализм в интерьере, полноценная кухня с завтраками и бранчами, зерно от обжарщиков из Минска Single Step: в эспрессо Бразилия, в фильтре была Кения, кофемашина La Marzocco за баром, цветы и растения, а на полках - кофейные журналы ✨ Брала капучино с собой - отличный баланс ☕️ 📍Sправа
🍓4🔥3🥰3
Showing the 3 most recent of 3 posts we hold for @nastyaprocoffee. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Настя про кофе” (@nastyaprocoffee), 492 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/nastyaprocoffee.
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.