13 Jan 2025, 10:11 UTC≈2,090 viewsread 7 August 2026
지갑주소랑 닉네임 개인적으로 보내주시면 빠르게 처리도와드리겠습니다.
Channel
크립토플로우 공지방
@cryptoflow_notice
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
764subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001929824237 |
|---|---|
| Type | Channel |
| Username | @cryptoflow_notice |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/cryptoflow_notice |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 07:37 | 764 | -1 |
| 28 Aug 2026, 04:35 | 765 | -2 |
| 21 Aug 2026, 04:48 | 767 | -1 |
| 14 Aug 2026, 20:35 | 768 | -4 |
| 8 Aug 2026, 03:53 | 772 | no change |
| 7 Aug 2026, 09:18 | 772 | first reading |
Engagement
20 posts held, back to 10 January 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 1 page of 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 13 January 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
11 Jan 2025, 10:47 UTCviews —
크립토플로우 공지방 pinned a photo
11 Jan 2025, 09:51 UTC≈5,890 viewsread 7 August 2026
Photo
안녕하세요, 크립토플로우입니다. 항상 저희 서비스를 이용해 주신 모든 분들께 진심으로 감사드립니다. 갑작스럽지만 안타깝게도 개인적인 사정으로 인해 2024년 1월 13일 이후로 크립토플로우 서비스를 종료하게 되었습니다. 그동안 서비스를 운영하면서 좋은 분들을 만나고 많은 사랑과 관심을 받을 수 있어 정말 행복했습니다. 추가적으로 웹소켓 서비스를 이용해 주신 분들은 후원비를 반환해 드릴 예정입니다. 관련된 내용은 번거로우시겠지만 개인적으로 연락 주시면 빠르게 처리해 드리겠습니다. 새해에 모든 분들의 건강과 성공을 기원하며, 다시 한 번 진심으로 감사드립니다.
11 Jan 2025, 02:00 UTC≈1,860 viewsread 7 August 2026
🔃 빗썸 공지사항 UPDATE 아이오타(IOTA) 원화 마켓 추가 기념 거래 / 순입금 이벤트 ⏰ 2025-01-11 11:00:29
11 Jan 2025, 02:00 UTC≈1,730 viewsread 7 August 2026
🔥 빗썸 상장 🔥 (이벤트) 아이오타(IOTA) 원화 마켓 추가 기념 거래 / 순입금 이벤트 ⏰ 2025-01-11 11:00:28
11 Jan 2025, 01:20 UTC≈3,890 viewsread 7 August 2026
🔃 빗썸 공지사항 UPDATE (마켓 추가) 스트라이크(STRIKE), 아이오타(IOTA) 원화 마켓 추가 ⏰ 2025-01-11 10:20:29
11 Jan 2025, 01:20 UTC≈1,550 viewsread 7 August 2026
🔥 빗썸 상장 🔥 스트라이크(STRIKE), 아이오타(IOTA) 원화 마켓 추가 ⏰ 2025-01-11 10:20:29
10 Jan 2025, 14:50 UTC≈1,270 viewsread 7 August 2026
🔃 업비트 공지사항 UPDATE optimism 네트워크 업그레이드에 따른 MTL, LSK, BRETT, CARV, PI 입출금 일시 중단 안내 (완료) ⏰ 2025-01-10 23:50:01
10 Jan 2025, 14:50 UTC≈1,870 viewsread 7 August 2026
🔃 업비트 공지사항 UPDATE Temporary suspension of Deposits/Withdrawal service for MTL, LSK, BRETT, CARV, PI due to Network Upgrade (Completed) ⏰ 2025-01-10 23:50:01
10 Jan 2025, 12:30 UTC≈1,150 viewsread 7 August 2026
📢 바이낸스 공지사항 Binance Will Add aixbt by Virtuals (AIXBT), ChainGPT (CGPT) and Cookie DAO (COOKIE) on Earn, Buy Crypto, Convert & Margin ⏰ 2025-01-10 21:30:13
10 Jan 2025, 11:00 UTC≈1,050 viewsread 7 August 2026
🔃 업비트 공지사항 UPDATE Investment Warning (SOLVE) ⏰ 2025-01-10 20:00:02
10 Jan 2025, 11:00 UTC≈1,450 viewsread 7 August 2026
📢 업비트 공지사항 솔브케어(SOLVE) 거래 유의 종목 지정 안내 ⏰ 2025-01-10 20:00:00
Showing the 12 most recent of 20 posts we hold for @cryptoflow_notice. 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.
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.
New Listings Feed
@NewListingsFeed · 57,570
Telegram ranks this channel #12 of 84 here — alongside 83 others — read 23 August 2026
@NewListingsFeed · 57,570
Telegram ranks this channel #12 of 84 here — alongside 83 others — read 23 August 2026
우리는 트윗충
@twitchoong · 73,696
Telegram ranks this channel #16 of 91 here — alongside 90 others — read 25 August 2026
@twitchoong · 73,696
Telegram ranks this channel #16 of 91 here — alongside 90 others — read 25 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“크립토플로우 공지방” (@cryptoflow_notice), 764 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/cryptoflow_notice.
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.