Telegram RegisterThe public register of Telegram

Channel

Coin68

@coin68

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

24,323subscribers

-79 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-1001300523532
TypeChannel
Username@coin68
DescriptionCoin68.com là nơi cung cấp cái nhìn tổng quan nhanh và chính xác nhất về tiến bộ công nghệ blockchain và AI trên toàn cầu.
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/coin68

Growth

24,32324,40224,362.56 August 2026 — 24,402 subscribers7 August 2026 — 24,392 subscribers8 August 2026 — 24,374 subscribers9 August 2026 — 24,361 subscribers10 August 2026 — 24,349 subscribers11 August 2026 — 24,345 subscribers12 August 2026 — 24,334 subscribers13 August 2026 — 24,323 subscribers6 August 202613 August 2026
8 measurements spanning 7 days, net -79. 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,311–24,414 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:5724,323-11
12 Aug 2026, 04:3824,334-11
11 Aug 2026, 03:3524,345-4
10 Aug 2026, 06:4124,349-12
9 Aug 2026, 05:2224,361-13
8 Aug 2026, 07:2024,374-18
7 Aug 2026, 04:1724,392-10
6 Aug 2026, 05:1824,402first reading

Engagement

58 posts held, back to 3 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 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.48%
avg views ÷ 24,323 subscribers
Avg views / post
604
58 posts measured
Reaction rate
0.328%
reactions ÷ views · ER floor
Posts in window
58
of 58 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. It is computed over the 42 of 58 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held58 (3 August 202613 August 2026)
Views total35,044
Reactions total88
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 11:50 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
3,680
Videos
20
Links
25,300

Lifetime counters from Telegram’s own channel header, read 13 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

74 reactions across 34 posts, in 7 distinct kinds. The most used accounts for 60.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4560.8%
👍810.8%
😁810.8%
🔥68.11%
😭45.41%
👌22.70%
🤔11.35%

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

Measured over the 58 most recent posts we hold, published 3 August 2026 to 13 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

13 Aug 2026, 10:29 UTC160 viewsread 13 August 2026
Photo

Hyperliquid kỳ vọng CFTC sẽ cho phép các tổ chức được cấp phép triển khai mô hình perpetual futures trên blockchain của sàn. Xem thêm: https://coin68.com/hyperliquid-tim-duong-dua-perpetual-futures-vao-thi-truong-my/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

13 Aug 2026, 09:21 UTC245 viewsread 13 August 2026
Photo

Fidelity chuẩn bị bổ sung staking cho Fidelity Ethereum Fund (FETH) - quỹ ETF Ethereum spot đang quản lý khoảng 898 triệu USD. Chi tiết: https://coin68.com/fidelity-bo-sung-staking-cho-etf-ethereum-tra-thuong-hang-quy/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

13 Aug 2026, 08:00 UTC308 viewsread 13 August 2026
Photo

Metaplanet hiện là công ty đại chúng nắm giữ Bitcoin lớn thứ ba thế giới với 43.000 BTC, tương đương hơn 2 tỷ USD. Xem thêm: https://coin68.com/metaplanet-bac-tin-ban-322-trieu-usd-bitcoin/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

13 Aug 2026, 07:00 UTC343 viewsread 13 August 2026
Photo

Goldman Sachs chi 2,25 tỷ USD mua NEOS, sở hữu ngay ba quỹ ETF Bitcoin và Ethereum tạo thu nhập, quản lý hơn 1 tỷ USD tài sản. Chi tiết: https://coin68.com/goldman-sachs-thau-tom-ba-quy-etf-crypto-quan-ly-hon-11-ty-usd/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

13 Aug 2026, 05:53 UTC361 views2 reactionsread 13 August 2026
Photo

Trong lúc nhiều công ty kho bạc crypto chật vật vì thị trường suy yếu, Hyperion lại ghi nhận quý lãi khủng nhờ giá HYPE tăng mạnh và kho dự trữ token phình to từ 71 triệu USD lên 133 triệu USD, tương đương khoảng 87%. Xem thêm: https://coin68.com/hyperion-lai-ky-luc-31-trieu-usd-nho-kho-bac-hype/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

1🔥1

13 Aug 2026, 04:43 UTC393 viewsread 13 August 2026
Photo

SEC mở đường để các quỹ do Franklin Templeton triển khai được phép nắm giữ token BENJI nhằm phục vụ hoạt động quản lý dòng tiền nhàn rỗi. Xem thêm: https://coin68.com/sec-cho-phep-cac-quy-cua-franklin-templeton-dau-tu-vao-token-benji/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

13 Aug 2026, 03:33 UTC443 views2 reactionsread 13 August 2026
Photo

Tổng thống Mỹ Donald Trump cùng một số quan chức Nhà Trắng đang đối mặt với một vụ kiện liên bang liên quan đến Truth API, dịch vụ trả phí cho phép khách hàng nhận bài đăng từ các tài khoản lớn trên Truth Social sớm hơn công chúng. Chi tiết: https://coin68.com/trump-bi-kien-vi-ban-quyen-doc-truoc-bai-dang-truth-social/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

🔥1😁1

13 Aug 2026, 02:27 UTC467 viewsread 13 August 2026
Photo

CFTC can thiệp khẩn cấp để Kalshi tiếp tục hoạt động sau khi bang New York kiện nền tảng này với cáo buộc vận hành hoạt động cờ bạc trái phép. Chi tiết: https://coin68.com/cftc-van-cho-phep-kalshi-tiep-tuc-hoat-dong-bat-chap-don-kien-tu-new-york/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

12 Aug 2026, 08:38 UTC581 views2 reactionsread 13 August 2026
Photo

Ngân hàng Trung ương Nga vừa đề xuất đưa Bitcoin (BTC), Ethereum (ETH) và USDT của Tether vào danh sách tài sản được phép giao dịch trên các nền tảng được cấp phép. Chi tiết: https://coin68.com/nga-bat-den-xanh-cho-3-dong-crypto-dau-tien/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

1🔥1

12 Aug 2026, 07:39 UTC577 views2 reactionsread 13 August 2026
Photo

Layer-1 Harmony xác nhận bị hacker mint trái phép 4 tỷ ONE, chuyển gần 97% số token này lên sàn, kéo giá ONE lao dốc hơn 39%. Xem thêm: https://coin68.com/layer-1-harmony-bi-hacker-mint-trai-phep-4-ty-one/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

1👌1

12 Aug 2026, 05:57 UTC568 viewsread 13 August 2026
Photo

Ravencoin (RVN) đang đối mặt nguy cơ phải “quay ngược” blockchain khoảng 3 ngày sau một lỗ hổng nghiêm trọng, khiến các block không hợp lệ lọt vào mạng lưới. Chi tiết: https://coin68.com/ravencoin-nguy-co-dao-nguoc-blockchain-gia-rvn-lao-doc-20/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

12 Aug 2026, 04:34 UTC576 views1 reactionsread 13 August 2026
Photo

CEO Strategy Phong Le khẳng định công ty sẽ sớm quay lại mua Bitcoin, nhấn mạnh lượng BTC mua từ đầu năm vẫn cao gấp 25 lần số Bitcoin đã bán. Xem thêm: https://coin68.com/strategy-se-mua-bitcoin-tro-lai-vao-cuoi-nam/ ——————— Theo dõi Coin68 tại: Website | Facebook | Telegram | X

1

Showing the 12 most recent of 58 posts we hold for @coin68. 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 — 203,997 of 1,183,361entries 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Coin68” (@coin68), 24,323 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/coin68.

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.