Telegram RegisterThe public register of Telegram
Telegram profile photo for Proxy.Coffee Channel

Channel

Proxy.Coffee Channel

@proxy_coffee_channel

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

27,998subscribers

+97 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002410634032
TypeChannel
Username@proxy_coffee_channel
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 August 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/proxy_coffee_channel

Growth

27,78127,99827,889.56 August 2026 — 27,901 subscribers6 August 2026 — 27,901 subscribers6 August 2026 — 27,902 subscribers7 August 2026 — 27,792 subscribers8 August 2026 — 27,781 subscribers9 August 2026 — 27,790 subscribers10 August 2026 — 27,810 subscribers11 August 2026 — 27,835 subscribers12 August 2026 — 27,859 subscribers13 August 2026 — 27,892 subscribers14 August 2026 — 27,911 subscribers15 August 2026 — 27,942 subscribers17 August 2026 — 27,989 subscribers18 August 2026 — 27,998 subscribers6 August 202618 August 2026
14 measurements spanning 13 days, net +97. 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 27,748–28,031 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 15:0727,998+9
17 Aug 2026, 11:4527,989+47
15 Aug 2026, 20:4527,942+31
14 Aug 2026, 14:0627,911+19
13 Aug 2026, 05:5627,892+33
12 Aug 2026, 02:5327,859+24
11 Aug 2026, 03:3627,835+25
10 Aug 2026, 05:4027,810+20
9 Aug 2026, 05:5227,790+9
8 Aug 2026, 05:0727,781-11
7 Aug 2026, 08:1027,792-110
6 Aug 2026, 09:0027,902+1
6 Aug 2026, 02:0127,901no change
6 Aug 2026, 01:3527,901first reading

Engagement

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

ERR · 30 days
29.5%
avg views ÷ 27,998 subscribers
Avg views / post
8,260
3 posts measured
Reaction rate
0.214%
reactions ÷ views · ER floor
Posts in window
3
of 21 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 6 August 2026
Posts held21 (22 February 20266 August 2026)
Views total24,780
Reactions total53
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 13:43 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

1,637 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 59.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
98059.9%
👍31319.1%
🔥17410.6%
🕊1297.88%
🎉412.50%

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

Measured over the 21 most recent posts we hold, published 22 February 2026 to 6 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.

Telegram Stars

Stars received
395
across the posts below
Posts paid on
15
of 21 we hold a reading for · 71%
Most on one post
105
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @proxy_coffee_channel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 21 most recent posts we hold for this entry, published 22 February 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 16:48 UTC≈5,430 views15 reactionsread 18 August 2026
Photo

☕️ Один наш партнёр заработал уже 100 000 ₽ с нами Просто рекомендуя нас своей аудитории. Без вложений и рекламных бюджетов. 💸 Платим: • 30% с первой покупки вашего человека • 10% со всех его продлений — постоянно Выводим от 100 ₽ — на карту, криптой или на баланс. 🔗 Берёте свою ссылку в разделе партнерки и делитесь. Всё просто. Бот: 👉 @proxy_coffee_bot

7👍4🔥3🕊1

24 Jul 2026, 11:54 UTC≈9,150 views14 reactionsread 18 August 2026
Photo

🔑 Coffee VPN — теперь бесплатный пробный период! Даем 3 дня полного доступа: • Все сайты и приложения • Безлимитный трафик • Больше 10 серверов • Подходит для любых устройств 👉 Бот: @proxy_coffee_bot

6🔥5🎉3

21 Jul 2026, 12:51 UTC≈10,200 views24 reactions10 Starsread 18 August 2026

🛡 Обновление Telegram Proxy! Провели масштабную модернизацию — расширили список серверов, улучшили стабильность и исправили проблемы с подключением. ✅ Теперь прокси лучше обходят новые блокировки: рукопожатие быстрее, «вечное обновление» уходит, медиа грузятся без задержек. Если прокси не работает: ▸ Откройте «Мои прокси» в боте ▸ Нажмите «Обновить прокси» ▸ Если всё ещё не работает — поменяйте сервер на другой

14🔥6🎉4

4 Jul 2026, 11:12 UTC≈14,500 views18 reactions43 Starsread 18 August 2026
Photo

☕️ Порадуйте своих близких с Coffee VPN Теперь своим друзьям и родным можно покупать не только чашку кофе, но и полезный подарок — быстрый, надёжный и безлимитный. 🎁 Приятный сюрприз для тех, кто ценит стабильный интернет. 👉 Бот: @proxy_coffee_bot

12🎉3🔥3

2 Jul 2026, 11:45 UTC≈12,600 views28 reactions71 Starsread 18 August 2026

✅ Всё работает! Завершили переезд на новый стабильный дата-центр — теперь сервера работают надёжнее. ▸ Бот и мини-апп полностью восстановлены. ▸ Прокси и VPN — в штатном режиме. ▸ Покупка и продление доступны. ☕️ Заходите: @proxy_coffee_bot

15👍7🔥6

30 Jun 2026, 09:37 UTC≈13,100 views34 reactions20 Starsread 18 August 2026

⚠️ Идут технические работы! Бот временно недоступен из-за сбоя у хостинг-провайдера. Сами прокси и VPN работают — проблема только с покупкой и продлением через бота. 🔐 Ваши данные и подписки в безопасности. Если оплатили — всё придёт автоматически после восстановления. Переезжаем на более надёжную платформу, чтобы такое не повторялось. Бот скоро заработает. 🙏 Спасибо за понимание!

🕊1511🔥6👍2

25 Jun 2026, 15:18 UTC≈16,400 views22 reactions10 Starsread 18 August 2026

☕️ Представляем новый Coffee VPN! Теперь мы — не просто прокси, а полноценный VPN. Работает стабильно при текущих блокировках в РФ. В вашем распоряжении 10 серверов с кофейными именами: Американо, Эспрессо, Латте, Капучино и др. 📶 Один ключ — для всех ваших устройств. Подключайтесь: ☕️ t.me/proxy_coffee_bot?start=vpn

🔥137👍2

31 May 2026, 11:38 UTC≈24,000 views44 reactions105 Starsread 18 August 2026

😀 Пока в Telegram кипели новости о блокировках прокси — наши работали стабильно. И у нас сразу несколько обновлений: ▸ Новый недельный тариф └ Отличный вариант попробовать сервис. ▸ Прокачали поддержку └ Теперь все вопросы решаем оперативно. Пишите в @assistent. ▸ Последний день весны └ Промокод SPRING даёт −20%. Только до конца дня! ☕️ Наш: бот / мини-апп

23👍10🔥7🕊3🎉1

8 May 2026, 13:24 UTC≈34,200 views69 reactions10 Starsread 18 August 2026

🥇 Первый прокси, который работает при любых блокировках! В последнее время многие из вас столкнулись с проблемами: отключения мобильного интернета, белые списки, ограничения во время беспилотных атак — всё это влияло на работу прокси. 🥳 Мы нашли решение! Встречайте новый сервер TG Espresso — обходит все текущие блокировки и ограничения. Что нужно сделать: → Выбрать сервер TG Espresso в боте → Или переключиться с т

46🔥13🎉8🕊2

10 Apr 2026, 12:42 UTC≈34,500 views74 reactions12 Starsread 18 August 2026

🔄 Вчера Telegram выпустил обновление с фиксом MTProto Proxy на iOS — на остальных платформах обновление доступно уже пару дней. Обновитесь, если ещё не сделали этого. Работа прокси стала заметно стабильнее. ⚠️ Сегодня произошёл аппаратный сбой ноды на части серверов — возможны перебои в работе бота. Мини-апп работает штатно. ▸ TG-SPB — недоступен ▸ TG-MSK — технические неполадки ▸ Остальные серверы — в штатном реж

47👍18🕊8🔥1

4 Apr 2026, 17:29 UTC≈35,600 views90 reactionsread 18 August 2026

🛡 Добавили резервные прокси Сейчас Telegram исправляет уязвимость в MTProto Proxy, через которую РКН легко блокирует соединения, а заодно обновляет наши DNS-записи — процесс небыстрый, и часть подключений может не работать.. Пока ждём, мы подключили для вас резервные серверы, которые работают прямо сейчас. 🔘 Что делать: ▸ Откройте «Мои прокси» ▸ Выберите резервный прокси: Fake-TLS или Standard ▸ Подключитесь Как

48👍28🔥10🎉4

3 Apr 2026, 21:14 UTC≈28,700 views132 reactions1 Starread 18 August 2026

⚡️ Хорошие новости! Работа части серверов уже восстановлена. Для тех, у кого всё ещё нет соединения — добавили новый сервер с двухуровневой системой обхода 🛡 Переключитесь на 🏳️ TG Stable — все должно заработать. 🌐 Скоро восстановим остальные серверы в полном объёме. Оставайтесь с нами ☕️

96👍23🕊7🎉6

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 210,929 of 1,549,376entries 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

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.

Mentions

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

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

“Proxy.Coffee Channel” (@proxy_coffee_channel), 27,998 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/proxy_coffee_channel.

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.