Telegram RegisterThe public register of Telegram
Telegram profile photo for Кофе В Арке (Томск)

Channel

Кофе В Арке (Томск)

@Kofe_V_Arke

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

89subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002157468692
TypeChannel
Username@Kofe_V_Arke
CreatedBetween 1 May 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live6 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 6 October 2026
On Telegramt.me/Kofe_V_Arke

Topic

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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.

Growth

8789887 August 2026 — 87 subscribers9 August 2026 — 87 subscribers25 September 2026 — 89 subscribers7 August 202625 September 2026
3 measurements spanning 49 days, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 87–89 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 15:0289+2
9 Aug 2026, 16:0287no change
7 Aug 2026, 18:0187first reading

Engagement

11 posts held, back to 26 January 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 11 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 37s
Average length
22s

Measured directly from 7 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.

Reaction mix

130 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 47.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6247.7%
❤‍🔥4635.4%
🥰1612.3%
😍64.62%

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 11 of the 11 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 130 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 26 January 2026 to 9 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.

Recent posts

9 Aug 2026, 05:51 UTC32 views13 reactionsread 9 August 2026
Photo

Всем доброго утра!

❤‍🔥7🥰6

23 Mar 2026, 01:28 UTC136 views7 reactionsread 9 August 2026
Video

Доброе кофейное утро! ☕️ #Томск #кофе #КофеВАркеТомск

😍4🔥2❤‍🔥1

21 Mar 2026, 07:21 UTC135 views12 reactionsread 9 August 2026
Photo

Доброго весеннего дня! Радуемся тёплыми солнцу и готовим апельсиновый 🍊 Бамбл Кофе (он же Холодный Шмель 🐝) Лёд 🧊 + Апельсиновый сок 🍊 + Карамельный сироп ❤️ + Двойной Эспрессо ☕️ #Томск #Кофе #КофеВАркеТомск #Весна

🔥10❤‍🔥2

20 Mar 2026, 02:32 UTC113 views10 reactionsread 9 August 2026
Video

Доброго утра! 👋 На дворе календарная весна , но за окном ещё летают снежинки ❄️ Мы очень ждём весеннего тепла и солнце 🔆 Активно ведём разработку весенних НЕ КОФЕЙНЫХ новинок, представляем молочный коктейль с мороженным 🍦 и пюре черники 🫐, этот коктейль так же будет в варианте с тапиокой (бабл-милк) 🧋🧋🧋🧋🧋🧋🧋🧋🧋🧋 #Кофе #Кофейное #Томск #КофеВАркеТомск

🔥8❤‍🔥2

19 Mar 2026, 01:51 UTC104 views12 reactionsread 9 August 2026
Photo

Доброе утро! ☀️☀️ 🧪🧪Немного наших кофейных экспериментов с альтернативной: в разогретый кувшин гейзера добавили 10 гр тёмного шоколада 🍫, залили тёплыми сливками ☕️ и дождались "извержения"🌋 кофе ☕️ #кофе #томск #КофеВАркеТомск

🔥11❤‍🔥1

17 Mar 2026, 01:56 UTC108 views16 reactionsread 9 August 2026

КоФе в АрКе Награда «Хорошее Место» наша! https://yandex.ru/maps/org/199320194479

🔥9❤‍🔥7

16 Mar 2026, 01:55 UTC115 views14 reactionsread 9 August 2026
Photo

Доброе утро ! ☕️ #кофе #Томск #КофеВАркеТомск

🥰10🔥3❤‍🔥1

15 Mar 2026, 03:54 UTC116 views13 reactionsread 9 August 2026
Photo

Доброе солнечное утро ☕️ ❤️ #Томск #кофе #КофеВАркеТомск

❤‍🔥13

25 Feb 2026, 11:04 UTC152 views10 reactionsread 9 August 2026
Photo

Друзья, всем привет! 👋 Сегодня завезли немного Робусты ☕️ этот сорт пользуется меньшим спросом, но находит своих ценителей ☕ Добро пожаловать к нам за чашечкой ароматного кофе! ☕️

❤‍🔥10

26 Jan 2026, 02:20 UTC216 views10 reactionsread 9 August 2026
Video

Video, posted without a caption

🔥9❤‍🔥1

26 Jan 2026, 02:14 UTC179 views13 reactionsread 9 August 2026
Photo

Всем доброго утра! Иногда авторы ТГ каналов после долгого перерыва в публикациях пишут разъяснительный пост - так мол и так устал, болел, загорал и т.д. тоже напишу: у нас так получилось) Всё это время мы варили вкусный кофе и радовали наших гостей. ☕️ Сегодня захотелось поделиться кофейной эстетикой. Первый пост 2026 года. Буря в стакане 🌪

🔥10😍2❤‍🔥1

Showing the 11 most recent of 11 posts we hold for @Kofe_V_Arke. 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.

Cite this entry

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“Кофе В Арке (Томск)” (@Kofe_V_Arke), 89 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Kofe_V_Arke.

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.