Telegram RegisterThe public register of Telegram

Channel

ЗаДРИПанный кофейник

@CoffeejNik

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,841subscribers

+43 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002018091764
TypeChannel
Username@CoffeejNik
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/CoffeejNik

Growth

1,7981,8411,819.56 August 2026 — 1,798 subscribers6 August 2026 — 1,798 subscribers6 August 2026 — 1,799 subscribers9 August 2026 — 1,824 subscribers12 August 2026 — 1,841 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net +43. 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 1,792–1,847 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:471,841+17
9 Aug 2026, 15:111,824+25
6 Aug 2026, 09:451,799+1
6 Aug 2026, 06:511,798no change
6 Aug 2026, 05:221,798first reading

Engagement

19 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.68%
avg views ÷ 1,841 subscribers
Avg views / post
123
18 posts measured
Reaction rate
15.4%
reactions ÷ views · ER floor
Posts in window
19
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held19 (5 August 20267 August 2026)
Views total2,212
Reactions total341
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:30 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

189 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 23.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4523.8%
4322.8%
custom 54205862217871664932714.3%
custom 5269389547468245998178.99%
custom 5848020718545016089178.99%
custom 527176239664020049294.76%
🥰94.76%
custom 585070537375272646584.23%
😍73.70%
💘42.12%
😁31.59%

Custom emoji. 5 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 areTelegram’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 18 of the 19 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 341reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 5 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.

Recent posts

7 Aug 2026, 16:08 UTC53 views5 reactionsread 7 August 2026

Отзывы тех, кто уже попробовал 😏

custom 58480207185450160893custom 54205862217871664932

7 Aug 2026, 16:08 UTC54 views7 reactionsread 7 August 2026

Как он пахнет клубникой и ананасами вы бы знали 😍

custom 52717623966402004923custom 58480207185450160893custom 52693895474682459981

7 Aug 2026, 13:32 UTC108 views20 reactionsread 7 August 2026
Photo

🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤🤩 Что-то на богатом 😎 Зерно: Копи-Лувак Дескрипторы: манго, мандарин, макадамия, перец Обжарка: фильтр Обжарщик: Bravos Coffee Метод заваривания: дрип Делал по рецепту: 3 пролива до 180 воды t 93°, вода 101 ppm Добавил 1 каплю минералов от Hiwater в "Святой Источник" с 65 ppm, чтобы стабилизировать 200 гр вод 50, 60, 70 гр воды По собственным ощущениям: 🤩 В аромате при открытии дрипа тропики, мандари

6🔥5😁3custom 54205862217871664932💘1🥰1😍1custom 52717623966402004921

7 Aug 2026, 06:56 UTC130 views16 reactionsread 7 August 2026
Photo

Доброе утро, ребзя 😏 Оно у меня началось с добивки каппинга #ДушноеКофейноеБинго Безумно нравится формат, вообще с удовольствием участвую) А вас с пятницей и скорым началом выходных 🥰

7custom 54205862217871664935custom 58480207185450160894

6 Aug 2026, 13:08 UTC154 views28 reactionsread 7 August 2026
Photo

Друзья продолжают присылать штрих коды на озон 😁

🔥16custom 58480207185450160897custom 52717623966402004925

6 Aug 2026, 11:52 UTC164 views26 reactionsread 7 August 2026
Photo

Начнем каппить #ДушноеКофейноеБинго Буду пробовать по 2 чашки, чтобы не напрягать чайник Воду Aqua Minerale мешаю с минеральными каплями от Hiwater, добавил 2 капельки, t° - 93: 102 ppm на первые 2 чашки 110 ppm на вторые 2 чашки Помол 18 щелчков на Timemore C2 по 11 гр кофе на чашку Номер 2 отвал бошки, 1 и 4 очень похожи, поэтому я для них куплю ещё водички и переделаю эти чашки) 3 под сомнением, но в целом отв

🔥117🥰4😍3💘1

6 Aug 2026, 09:49 UTC162 views37 reactionsread 7 August 2026
Photo

Наконец я постригся 😁

🔥13custom 5269389547468245998127🥰2💘1😍1custom 58507053737527264651

6 Aug 2026, 08:03 UTC158 views21 reactionsread 7 August 2026
Photo

В основном, как я заметил, выкладываю эти посты по средам почему-то, вчера и правда хотел, но контента было достаточно) Для новеньких и в целом для удобства скомпонованная навигация по каналу❤️ 🟠Пост-знакомство со мной 🟠Волшебные слова 😏 Обучающая рубрика #научпокКофе: 🔶Вкусный способ заварки дрипов 🔶Сенсорика дома: фрукты 🔶Сенсорика дома: цитрусы 🔶Как минерализация воды влияет на вкус кофе? 🔶Как вкусно сварить во

custom 542058622178716649398custom 52693895474682459982😍1custom 58507053737527264651

6 Aug 2026, 06:03 UTC127 views29 reactionsread 7 August 2026
Forwarded from @CoFeeINkaPhoto

Можно поздравить Никиту с коллаборацией 🤎 Общие сведения: Зерно: Colombia Las Moras Huila Washed Дескрипторы: ананас, клубника Обработка: мытая Регион: Уила Q: 86 Обжарка: фильтр Обжарщик: Колибри кофе. Я еще не пробовала дрипчики ☕ но точно знаю, что буду заваривать по рецепту от Никиты, который написан на пачке 😉 😄ВКонтакте 😉YouTube 😅Нельзяграмм 📩Coffeeinka

custom 542058622178716649398custom 58507053737527264656🥰2custom 52693895474682459982💘1😍1

6 Aug 2026, 06:03 UTC≈37 views4 reactionsread 6 August 2026

Доброе утро, ребзя 😏 Сегодня четверг, не забываем про корицу в кофе 🥰

5 Aug 2026, 20:27 UTC≈106 views15 reactionsread 6 August 2026
Video message

Video message, posted without a caption

Showing the 12 most recent of 19 posts we hold for @CoffeejNik. 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.

Citation-graph rank

Citation-graph rank — 17,562 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 7 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.

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.

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

“ЗаДРИПанный кофейник” (@CoffeejNik), 1,841 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/CoffeejNik.

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.