Telegram RegisterThe public register of Telegram

Channel

Coffee Crypto Official

@CoffeeCryptooo

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

24,545subscribers

-65 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001562170071
TypeChannel
Username@CoffeeCryptooo
DescriptionOwner: @duyhayla Booking Ads: @xutocdo Group Chat: https://t.me/CoffeeCryptoo 🛠️ Coffee Crypto Airdrop & Insight https://t.me/coffeecryptoai 📰 Coffee Crypto News https://t.me/coffeecryptonews
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/CoffeeCryptooo

Growth

24,54524,61024,577.57 August 2026 — 24,610 subscribers7 August 2026 — 24,610 subscribers8 August 2026 — 24,601 subscribers9 August 2026 — 24,594 subscribers10 August 2026 — 24,582 subscribers11 August 2026 — 24,565 subscribers12 August 2026 — 24,545 subscribers7 August 202612 August 2026
7 measurements spanning 5 days, net -65. 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 24,535–24,620 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:4224,545-20
11 Aug 2026, 07:0524,565-17
10 Aug 2026, 07:1224,582-12
9 Aug 2026, 03:5324,594-7
8 Aug 2026, 05:1424,601-9
7 Aug 2026, 05:1524,610no change
7 Aug 2026, 05:0824,610first reading

Engagement

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

ERR · 30 days
16.1%
avg views ÷ 24,545 subscribers
Avg views / post
3,940
26 posts measured
Reaction rate
0.992%
reactions ÷ views · ER floor
Posts in window
26
of 26 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 11 August 2026
Posts held26 (28 July 202611 August 2026)
Views total102,460
Reactions total1,016
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 22:36 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.

What this channel posts

Photos
6,130
Videos
214
Links
661

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

1,016 reactions across 26 posts, in 5 distinct kinds. The most used accounts for 67.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
69067.9%
🤣26325.9%
🔥363.54%
👏151.48%
💯121.18%

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

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

11 Aug 2026, 14:36 UTC≈2,190 views20 reactionsread 12 August 2026
Photo

Dành dụm hơn nửa năm mới sắm được 2 cọng dây. Vàng giờ mất giá quá ae

🤣145💯1

Signed Nhi Cua

10 Aug 2026, 07:00 UTC≈2,850 views42 reactionsread 12 August 2026

Có luật không đồng nghĩa với việc crypto mua từ trước sẽ bị thu hồi. Hiện chưa có quy định nào mình tìm thấy nói rằng tài sản mã hóa được mua trước khi khung pháp lý mới hình thành thì sẽ mất quyền sở hữu chỉ vì được mua từ trước. Nhưng có một vấn đề thực tế đáng quan tâm hơn: Nếu sau này bạn bán BTC/USDT và chuyển vài tỷ đồng về ngân hàng, bạn có thể giải thích được dòng tiền đó hình thành như thế nào không? Ví

37🔥4💯1

Signed Nhi Cua

9 Aug 2026, 10:55 UTC≈3,270 views38 reactionsread 12 August 2026
Photo

Đẹp lắm nha

38

Signed Duyhayla

9 Aug 2026, 07:24 UTC≈3,340 views35 reactionsread 12 August 2026

Anh em nghĩ sao về câu hỏi này: Chị ơi, em đã mua BTC từ nhiều năm trước. Sau này bán vài tỷ rồi chuyển về ngân hàng, chứng minh nguồn tiền thế nào ạ?

29🔥5💯1

Signed Nhi Cua

8 Aug 2026, 05:58 UTC≈3,910 views74 reactionsread 12 August 2026
Photo

Lên xe Stl 63567 Tp 71-75

63🤣11

Signed Duyhayla

8 Aug 2026, 05:57 UTC≈3,610 views40 reactionsread 12 August 2026
Photo

Giờ mở nến ngày ra mới thấy ma trận fibo luôn, bt coi h2 không để ý 😰, ai tin BTC lên 71-75 dơ tay!

38🤣2

Signed Duyhayla

7 Aug 2026, 07:57 UTC≈3,620 views39 reactionsread 12 August 2026

Thôi éo gồng nữa chốt luôn đi chán vc

🤣276👏4💯2

Signed Duyhayla

6 Aug 2026, 09:39 UTC≈4,630 views39 reactionsread 12 August 2026

Anh em ko sử dụng sticker liên quan đến mấy Bác mấy Cụ nha, mod thấy dùng ban luôn nha.

37🤣2

Signed Duyhayla

6 Aug 2026, 08:57 UTC≈4,000 views38 reactionsread 12 August 2026
Photo

Vẫn giữ đợi tp

34🔥2💯1🤣1

Signed Duyhayla

5 Aug 2026, 13:50 UTC≈4,110 views84 reactionsread 12 August 2026
Photo

:))) má chửi quá chửi bay mẹ kênh

🤣6816

Signed Duyhayla

5 Aug 2026, 12:20 UTC≈3,670 views28 reactionsread 12 August 2026
Photo

🔴 #NÓNG: ANH EM LƯU Ý ‼️ CÔNG VĂN HỎI CƠ QUAN THUẾ VỀ KÊ KHAI GIAO DỊCH P2P/OTC USDT Một nhà đầu tư tại TP.HCM cho biết đã trực tiếp nộp công văn đến Chi cục Thuế Cơ sở 2 TP.HCM để xin hướng dẫn chính thức về việc kê khai và nộp thuế đối với giao dịch USDT qua Binance P2P và OTC. 👉 Các nội dung được đề nghị làm rõ gồm: - Giao dịch P2P/OTC được xem là đầu tư, chuyển nhượng tài sản số hay hoạt động kinh doanh? - T

28

Signed Duyhayla

5 Aug 2026, 08:30 UTC≈3,670 views14 reactionsread 12 August 2026

Trong trường hợp anh em chưa biết cách sử dụng discord ntn, liên hệ với các admin để được hướng dẫn nhé @ann_neeee @Kem2k9 @laohac_cc @phuongnam03 @hoaluuu

13💯1

Signed Nhi Cua

Showing the 12 most recent of 26 posts we hold for @CoffeeCryptooo. 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 — 148,199 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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Binance Futures Liquidations
@BinanceLiquidations · 183,475
Telegram ranks this channel #37 of 95 here — alongside 94 others — read 12 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“Coffee Crypto Official” (@CoffeeCryptooo), 24,545 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/CoffeeCryptooo.

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.