Channel
@etloncoffee
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,147subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001628237124 |
|---|---|
| Type | Channel |
| Username | @etloncoffee |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/etloncoffee |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 03:52 | 4,147 | -11 |
| 9 Aug 2026, 09:52 | 4,158 | +5 |
| 6 Aug 2026, 04:17 | 4,153 | no change |
| 6 Aug 2026, 03:50 | 4,153 | first reading |
12 posts held, back to 28 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 5 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 12 (28 July 2026 – 7 August 2026) |
| Views total | 14,929 |
| Reactions total | 571 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:16 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.
Measured directly from 3 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.
334 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 35.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5460664807894045456 | 119 | 35.6% | |
| custom 5319066444883828666 | 109 | 32.6% | |
| custom 5321467585005376421 | 60 | 18.0% | |
| custom 5222128023695812989 | 26 | 7.78% | |
| custom 5319007148565341481 | 20 | 5.99% |
Custom emoji. Every 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 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 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 571reactions 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 28 July 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.
Квест закончился, кофейни закрылись, а мы при помощи рандомайзера выбрали тех, кому подарим билеты на Пикник Афиши! 🪩☕️ Объявляем победителей: @foxydashk @olinkadolinka @nastya_kriss @asya_won @hecoyc Поздравляем и желаем классно провести субботу. Проверяйте свои билеты в сообщениях завтра утром. Увидимся на Пикнике! 🧺
custom 522212802369581298914custom 531906644488382866614custom 546066480789404545611
Отменяем маршрут дом→работа→дом и предлагаем свой на последний месяц лета! 🗺️ Собрали маршрут с прогулками, кофе, фестивалями и местами, куда стоит заглянуть в августе.
custom 546066480789404545621custom 531906644488382866617custom 532146758500537642111custom 52221280236958129896
Яркие баночки в наших холодильниках! 👀🧡 Вместе с lapochka выпустили лимонады без сахара в ярких банках, которые освежают, утоляют жажду и легко становятся спутниками летних прогулок. Встречайте в наших кофейнях два вкуса: • Яблочный шорле • Дыня + мята Одна баночка – 250₽. А теперь главный вопрос: яблоко или дыня?
custom 531906644488382866629custom 546066480789404545616custom 532146758500537642111
В жару хочется выпить всё со льдом! 😌🧊 На такие случаи у нас есть холодная классика и сезонное меню A-la rus. Холодная классика: любимые кофейные хиты — от освежающего латте до бодрящего эспрессо-тоника. Сезонное меню A-la rus: вкусы, которые знакомы с первого глотка, в летнем исполнении. А что сегодня будет в твоём стакане?
custom 546066480789404545612custom 53214675850053764219custom 53190664448838286667
Ваши идеи прошли проверку на практике! 😉🥪 Самым лучшим сочетанием к напитку сегодня стал грилдчиз с курицей и соусом терияки, поэтому бонусный напиток начисляем автору этого комментария.
custom 54606648078940454566
Наш SMM думает, с чем выпить кофе. Поможете? 👀☕️ Продолжайте в комментариях: мой идеальный напиток невозможен без... Автору самой вкусной идеи начислим бонусный!
custom 546066480789404545620custom 532146758500537642114custom 531906644488382866612custom 52221280236958129893
Ритуал на август, который точно сделает это лето: 🟠Обновить заставку на экране телефона; 🟠Не забывать пить кофе; 🟠Наслаждаться последним тёплым месяцем. Обои в хорошем качестве в комментариях! 💬
custom 531906644488382866615custom 546066480789404545614custom 53214675850053764218custom 52221280236958129893
Показываем, чем в наших кофенях можно дополнить напиток: от протеина до миндальной пенки 🥥🧋 А что ты добавляешь в свой кофе чаще всего?
custom 531900714856534148120custom 546066480789404545619custom 531906644488382866615custom 53214675850053764217
Объявляем сладкую паузу! 🥛🍓 Во всех кофейнях теперь готовим молочные коктейли: сливочные, холодные и с любимым сиропом. Для тех моментов, когда хочется взять что-то вкусное и почувствовать лёгкую беззаботность этим летом. 480 мл – 330₽
Надеемся, никто не заметил 🫨🍹
Июль официально отправляется в фотоархив 🎞️ А бонусный напиток — к автору этого комментария. Встречаемся за кофе!
Ждали кофейный квест? Мы тоже! 💌 Этлон и Пикник Афиши придумали маршрут, который станет отличным поводом погулять по Петербургу, заглянуть в наши кофейни и, конечно, побороться за классные призы. С 29 июля по 7 августа: • делай покупки в кофейнях-участницах; • собирай уникальные наклейки; • проходи маршрут до конца и получай попытку вытянуть приз из автомата. В подарках: VIP-билеты и билеты на Пикник Афиши, термос…
Showing the 12 most recent of 12 posts we hold for @etloncoffee. 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 — 137,922 of 1,169,250entries 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.
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.
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.
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.
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.
“ETLON COFFEE” (@etloncoffee), 4,147 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/etloncoffee.
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.