#바이빗 TOKEN2049 Playground: New user perks, BTC price guess & more!

Channel
코인코 팬 채널 - 거래소 공지, 뉴스, 정보
@coinkokr
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,609subscribers
-1 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 | -1002119187487 |
|---|---|
| Type | Channel |
| Username | @coinkokr |
| Description | 코인코 팬 채널 본 채널은 코인코를 보며 매매를 하던 팬이 기존 코인코의 알림 서비스가 사라지는 게 안타까워 비슷하게 만든 채널입니다. 코인코와 아무런 관계는 없습니다. ※정보는 투자 권유 목적이 아니며 투자의 책임은 항상 본인에게 있습니다. |
| Created | Between 1 November 2023 and 31 May 2024— 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 | 3 |
| Confirmed unchanged | 3 times, most recently 12 August 2026 |
| On Telegram | t.me/coinkokr |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 23:23 | 1,609 | -1 |
| 6 Aug 2026, 11:35 | 1,610 | no change |
| 6 Aug 2026, 10:01 | 1,610 | first reading |
Engagement
20 posts held, back to 17 April 2025 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 17 April 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈5
- Links
- ≈6,250
Lifetime counters from Telegram’s own channel header, read 7 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.
Recent posts
#바이빗 Delisting of BUZZUSDT Perpetual Contract
#바이낸스 Binance Pool Launches Super Mine Page: Increase BTC Hashrate to Share 5,000 USDT in Token Vouchers!
#바이낸스 Tokens Removed from Binance Alpha for Technical Incompatibility
#바이낸스 Introducing Initia (INIT) on Binance Launchpool! Farm INIT by Locking BNB, FDUSD and USDC
#바이빗 Updates on Tick Size for Spot Pairs (Apr 18, 2025)
#바이낸스 Binance Earn: Enjoy 29.65% APR or More and Up to 1,300 USDC Referral Rewards on Dual Investment
#코인원 [업데이트 노트] 가격 이탈 푸시 알림 기능 추가
#바이빗 🔥 Explore 11 new assets for spot margin trading, Crypto Loans and more (Apr 18, 2025)
#바이빗 🔥 Trade safer with Bybit: Can top liquidity reduce slippage risks? Tune in and share 2,000 USDT!
#바이낸스 Binance Introduces Certified Letter for Liquidity Pairing Program Users
#업비트 [이벤트] 식목일 기념! 자산을 모으면 업비트가 시드머니를 선물해 드려요! (이벤트 종료)
Showing the 12 most recent of 20 posts we hold for @coinkokr. 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 — 898,315 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.
Mentions
Named by 1 registered channel — 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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“코인코 팬 채널 - 거래소 공지, 뉴스, 정보” (@coinkokr), 1,609 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/coinkokr.
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.