https://www.binance.com/en/support/announcement/detail/9ef6e347da924cdc90f53577ab483b1f MEXC 절대 입금, 출금 자제하시길 바랍니다. 멕씨 쪽에서는 뭐 미국 로펌 선임해서 연락한다고 공지 올렸지만 달라지지 않을 확률이 훨씬 높아요(HTX도 푼다더니 막혀있음) 일단 들어가면 나올 거래소가 없으니 들어가지 마시길..
❤1

Channel
@CryptoOwlNotice
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
7,713subscribers
-217 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001646725578 |
|---|---|
| Type | Channel |
| Username | @CryptoOwlNotice |
| Description | 둥지 짓는 부엉이 코인에 대한 모든 정보를 다루는 채널입니다 공지방: https://t.me/CryptoOwlNotice 채팅방: https://t.me/CryptoOwlNest 트위터: https://x.com/crypto_owl77 카카오톡:https://open.kakao.com/o/g5QSMgNf Dm: @cryptoowl77 |
| Created | 12 July 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/CryptoOwlNotice |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 18 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Bounty_ATM/1680731 Oct 2026, 07:33 UTC | @CryptoOwlNotice/12378 · this entry31 Oct 2026, 08:43 UTC | 1.00 | 70 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Bounty_ATM | 5 (5/5 hand-verifiable sample passed) | 1.00 | 68 minutes | this entry (3–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 202 comparable posts for this entry, running 5 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 07:19 | 7,713 | -12 |
| 6 Nov 2026, 00:19 | 7,725 | -9 |
| 3 Nov 2026, 01:29 | 7,734 | -5 |
| 31 Oct 2026, 01:29 | 7,739 | -8 |
| 27 Oct 2026, 19:41 | 7,747 | +1 |
| 24 Oct 2026, 16:44 | 7,746 | -4 |
| 21 Oct 2026, 13:59 | 7,750 | -13 |
| 18 Oct 2026, 12:57 | 7,763 | -3 |
| 15 Oct 2026, 05:57 | 7,766 | -26 |
| 12 Oct 2026, 01:19 | 7,792 | -8 |
| 5 Oct 2026, 17:39 | 7,800 | -4 |
| 28 Sept 2026, 11:42 | 7,804 | -26 |
| 18 Sept 2026, 10:56 | 7,830 | -12 |
| 14 Sept 2026, 02:21 | 7,842 | -4 |
| 10 Sept 2026, 14:01 | 7,846 | -16 |
| 5 Sept 2026, 15:57 | 7,862 | -15 |
| 2 Sept 2026, 02:44 | 7,877 | -10 |
| 30 Aug 2026, 11:45 | 7,887 | -10 |
| 27 Aug 2026, 19:23 | 7,897 | +10 |
| 25 Aug 2026, 03:44 | 7,887 | first reading |
274 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 35 pages of Telegram’s post history, 20 posts per page.
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 44 of 52 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 274 (5 August 2026 – 10 November 2026) |
| Views total | 17,619 |
| Reactions total | 66 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 01:32 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.
Lifetime counters from Telegram’s own channel header, read 11 November 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.
1,165 reactions across 221 posts, in 10 distinct kinds. The most used accounts for 67.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 781 | 67.0% | |
| 👍 | 235 | 20.2% | |
| 🔥 | 107 | 9.18% | |
| 😈 | 28 | 2.40% | |
| 🥰 | 5 | 0.429% | |
| 👏 | 3 | 0.258% | |
| 🆒 | 2 | 0.172% | |
| 🐳 | 2 | 0.172% | |
| 😁 | 1 | 0.086% | |
| 🫡 | 1 | 0.086% |
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 240 of the 274 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,354 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 274 most recent posts we hold, published 5 August 2026 to 10 November 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’s own ‘edited’ marker: 2 of 52 posts held from the last 30 days (3.85%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
https://www.binance.com/en/support/announcement/detail/9ef6e347da924cdc90f53577ab483b1f MEXC 절대 입금, 출금 자제하시길 바랍니다. 멕씨 쪽에서는 뭐 미국 로펌 선임해서 연락한다고 공지 올렸지만 달라지지 않을 확률이 훨씬 높아요(HTX도 푼다더니 막혀있음) 일단 들어가면 나올 거래소가 없으니 들어가지 마시길..
❤1
바낸에서 굿즈준다네요
❤1
업비트(Upbit) 공지 [거래] 하이퍼리퀴드(HYPE) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) 2026-11-10 13:50:00
❤1
아 ㅈ된거 같은데... 강 38에 털껄
❤2
얼어죽지 않기 위해 꿀팁 전수 중
❤2
갈만한데?!
❤1
얼마전에 항해사로 근무하는 친구 만나서 커피먹는데 친구가 호르무즈 한번 건너면 월급이 1억을 준다고 해서 에이~ 개구라겠지 했는데 진짜로 1억이라고함 호르무즈 해협이 항로에 포함되어 있으면 기본 월급 10만달러 + 통과한번 할때마다 5만불 줌. 유조선이 대부분이라, 한번갔다오는데 한 4개월 걸린다고 치면 1번 갔다오면 대~강 40~50만불 버는셈. 한국에 장금상선이라는 곳은 호르무즈 몰래 통과 존내하다가 이란 혁명수비대한테 찍혀서 협박도 받았다고함 목숨딱 한번걸고 다녀오면 6억
성수면 가까운데 혼내주러 가야하나.... 같이 갈 공주 찾습니다
❤1
신한은행 연 4% 예금 재출시 신한은행이 지난달 완판된 최고 연 4% 예금을 5,000억원 한도로 다시 팝니다 - 판매 기간: 11월 9일~12월 31일, 한도 소진 시 조기 마감 - 가입 금액: 50만원부터 1인당 2,000만원 - 6개월 기본 연 3.3%, 12개월 기본 연 3.6% - 앱 신규 접속과 급여이체 조건을 채우면 12개월 최고 연 4% 원금 손해 안 보는 예금으로 대동단결! ➡️원문
❤1
납치 30분 만에 코인 210만달러 탈취 영국 옥스퍼드에서 납치 피해를 본 투자자가 얼굴인증으로 거래소 계정이 털린 과정을 공개함 - 복면 남성 5명이 차량에 침입해 폭행 - 휴대폰 Face ID를 풀어 바이낸스에서 150만달러를 이체 - 게이트 계정의 ETH 약 60만달러도 빼감 - 바이낸스·MEXC 도움으로 약 100만달러를 동결·회수 와 이젠 아예 납치해서 인증으로 풀어버리네 ㄷ ㄷ ➡️원문
❤1
그만 내려가라..... Kda.. 붐은 온다...
❤1
음.. Ai 반도체를 잘하려면 불륜을 잘 해야하나..
❤1
Showing the 12 most recent of 274 posts we hold for @CryptoOwlNotice. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@CryptoOwlNotice named 10 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“크립토 부엉이🦉” (@CryptoOwlNotice), 7,713 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/CryptoOwlNotice.
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.