🚨 비트 70K 이탈 직전.
❤6👍2

Channel
@chavoonnam
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry
21,087subscribers
-426 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001250181792 |
|---|---|
| Type | Channel |
| Username | @chavoonnam |
| Description | 코인시황 및 차트분석 또는 이슈를 공유하는 텔레그램 채널입니다. ▶️[모든문의] @Chavoon_nam ▶️[공식 인스타그램] https://www.instagram.com/chavoonnam |
| Created | 22 May 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/chavoonnam |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 5 other registered channels. 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 |
|---|---|---|---|
| @cahier_de_market/1046119 Aug 2026, 06:48 UTC | @chavoonnam/37610 · this entry19 Aug 2026, 06:51 UTC | 1.00 | 3 minutes |
| @cahier_de_market/112443 Nov 2026, 12:40 UTC | @chavoonnam/38712 · this entry3 Nov 2026, 12:40 UTC | 1.00 | under a minute |
| @chavoonnam/37390 · this entry5 Aug 2026, 13:29 UTC | @degen2468/25825 Aug 2026, 13:29 UTC | 1.00 | under a minute |
| @HS_academy/107724 Aug 2026, 22:28 UTC | @chavoonnam/37380 · this entry4 Aug 2026, 22:37 UTC | 1.00 | 10 minutes |
| @HS_academy/111129 Nov 2026, 22:59 UTC | @chavoonnam/38839 · this entry9 Nov 2026, 23:03 UTC | 1.00 | 4 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @cahier_de_market | 13 (8/8 hand-verifiable sample passed) | 1.00 | 9 minutes | @cahier_de_market (13–0) |
| @insidertracking | 17 (8/8 hand-verifiable sample passed) | 0.99 | 8 minutes | @insidertracking (17–0) |
| @seaotterbtc | 10 (8/8 hand-verifiable sample passed) | 1.00 | 29 minutes | @seaotterbtc (9–1) |
| @degen2468 | 14 (8/8 hand-verifiable sample passed) | 1.00 | 12 minutes | @degen2468 (8–6) |
| @HS_academy | 5 (5/5 hand-verifiable sample passed) | 1.00 | 5 minutes | @HS_academy (5–0) |
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. 12 of the 13 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 181 comparable posts for this entry, running 4 August 2026 to 11 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 keys clone_copy · clone_mutual, last confirmed 12 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 |
|---|---|---|
| 12 Nov 2026, 07:05 | 21,087 | -1 |
| 8 Nov 2026, 19:11 | 21,088 | -8 |
| 6 Nov 2026, 09:47 | 21,096 | -15 |
| 5 Nov 2026, 08:49 | 21,111 | -1 |
| 4 Nov 2026, 11:45 | 21,112 | -4 |
| 3 Nov 2026, 13:36 | 21,116 | -5 |
| 2 Nov 2026, 13:19 | 21,121 | -6 |
| 1 Nov 2026, 15:06 | 21,127 | -11 |
| 31 Oct 2026, 13:37 | 21,138 | +4 |
| 30 Oct 2026, 14:11 | 21,134 | -9 |
| 28 Oct 2026, 07:56 | 21,143 | -10 |
| 27 Oct 2026, 06:55 | 21,153 | -1 |
| 26 Oct 2026, 03:57 | 21,154 | -6 |
| 25 Oct 2026, 03:50 | 21,160 | -8 |
| 24 Oct 2026, 01:56 | 21,168 | +3 |
| 22 Oct 2026, 22:17 | 21,165 | -10 |
| 21 Oct 2026, 16:09 | 21,175 | -8 |
| 20 Oct 2026, 13:27 | 21,183 | -5 |
| 19 Oct 2026, 16:47 | 21,188 | -2 |
| 18 Oct 2026, 19:09 | 21,190 | first reading |
690 posts held, back to 4 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 83 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 221 of 231 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 690 (4 August 2026 – 13 November 2026) |
| Views total | 420,066 |
| Reactions total | 1,986 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 03:47 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 13 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.
Measured directly from 6 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
8,197 reactions across 640 posts, in 3 distinct kinds. The most used accounts for 51.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4,241 | 51.7% | |
| ❤ | 3,606 | 44.0% | |
| 🔥 | 350 | 4.27% |
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 663 of the 690 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 8,412 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 690 most recent posts we hold, published 4 August 2026 to 13 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: 18 of 231 posts held from the last 30 days (7.79%) 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).
🚨 비트 70K 이탈 직전.
❤6👍2
블룸버그에 따르면 젠슨 황이 엔비디아 CEO에서 물러나기 직전 이사회가 늦은 밤까지 회의를 진행했으며, 결국 사임 외에는 선택지가 없는 상황에 놓였던 것으로 알려짐. 당시 젠슨 황은 평소 주도적이고 강한 모습과 달리 크게 무너진 모습을 보였으며, “아무래도 상관없다”, “신경 쓰지 않는다”는 취지의 말을 하기 시작한 것으로 전해짐. 이후 젠슨 황은 자신을 “쓰레기 같은 인간”이라고 표현했으며, 자신에게 앞으로 어떤 일이 벌어지는지는 더 이상 신경 쓰지 않는다고 말한 것으로 알려짐. 현재 가장 우려하는 부분은 자신의 아내와 이번 사건에 연루된 여성들의 삶을 “망치지 않는 것”이라고 밝힌 것으로 전해짐.
❤12👍1
BTC 72~70K 주요 지지 구간 진입 전일 장대음봉으로 72K를 한 번에 이탈. 거래량이 줄지 않는 가운데 20일 이동평균선도 200일 이동평균선을 하향 돌파하는 흐름이라, 일봉 기준 하방 우위가 이어지는 중. 70K는 지지 구간의 하단이자 심리적 지지선. 70K 위에서 횡보가 이어지거나 하락 시 거래량이 점차 줄어든다면 매도 압력 완화의 ‘초기 신호’로 볼 수 있음. 상승장 내 조정이 마무리될 가능성을 열어둘 수 있는 마지막 반등 구간으로 보고 있음. 다만, 주의해야 할 점은 최근 BTC는 나스닥의 단기 반등을 따라가지 못하는 모습. 나스닥이 다시 밀릴 경우 BTC도 동반 하락할 가능성이 매우 높다고 보고 있음. 나스닥 하락 시 70K 방어 여부를 주의 깊게 볼 필요가 있음. 70K마저 이탈하면 59K 저점에 대한 기존 관점…
❤10👍6
나스닥 선물
❤4👍2
주요 시장 이슈 젠슨 황 CEO의 사임으로 엔비디아가 장중 최대 14% 급락하면서 미국 증시 전반에 매도 압력이 확대됨. 다만 저가 매수세가 유입되면서 낙폭을 상당 부분 회복했고, 3대 지수 모두 0.4% 안팎의 하락으로 마감. 반면 국제유가는 미국과 이란의 협상 불확실성으로 상승했으며, 에너지 업종은 약 1.5% 강세를 기록. 예상보다 높은 소비자물가와 연준의 추가 금리 인상 가능성도 시장 부담으로 지속 작용 중.
👍3❤1
시장 위험 신호 점검 (11/13) • VIX 18.70 (+6.92%, 11/12) → 시장 변동성 재확대 • 미국 10년물 5.12% (+14bp, 11/12 시장 종가) → 금리 부담 크게 확대 • 하이일드 스프레드 3.34% (−8bp, 11/9 최신 확인치) → 신용시장 불안 완화 • 나스닥 25,366.09 (−0.39%, 11/12) → 이틀간 반등 이후 소폭 조정 종합 판단: 경계 유지 나스닥 조정 폭은 제한적이지만 국채금리가 5%를 돌파하고 VIX도 다시 상승한 상황. 신용스프레드는 안정되는 흐름이나 최신 수치 확인이 필요함. 지금은 지수 하락 폭보다 금리 상승과 변동성 확대가 동시에 이어지는지 확인하는 것이 중요해 보임.
👍2
국내 상승 출발
* 밍치 궈 - 젠슨황 사임 후 영향 의견 1. 단기적으로 악재는 주가에 반영됐다 - 주식시장에서는 이번 사임이 악재를 한 번에 털어내는 계기가 될 수 있다. 젠슨 황이 엔비디아와의 관계를 완전히 정리한 만큼, 향후 미 의회의 출석 요구나 후속 조사가 엔비디아 주가에 미치는 영향은 줄어들 가능성이 크다. 젠슨 황의 향후 행보가 엔비디아에 어떤 영향을 줄지는 조사 결과가 나오기 전까지 판단하기 이르다. 2. 구글 TPU가 가장 큰 수혜를 볼 가능성이 크다 - 엔비디아가 CEO 승계 불확실성에 직면하면서 구글 TPU는 고객사와 공급망 파트너의 신뢰를 더 얻을 기회를 맞았다. 단기적으로는 TPU의 핵심 파트너인 미디어텍과 브로드컴에 시장의 관심이 쏠릴 수 있다. 3. CEO 교체의 영향은 빨라도 2028년부터 나타날 전망이다 - 콜…
❤2
젠슨 황, ‘세 번째 여성’과 또 불륜 의혹 -사내 추가 혼외정사 정황 포착 https://www.g-enews.com/article/Global-Biz/2026/11/202611130623428207e250e8e188_1
👍2
🔥 차분남 × Gate 신규 가입 이벤트 🔥 전용 링크로 가입하고 KYC 인증과 첫 거래를 완료하면 출금 가능한 10 USDT를 즉시 지급. ✅ 참여 방법 1. 해당 링크로 신규 가입 2. KYC(본인 인증) 완료 3. 첫 거래 완료 ✅ 지급 혜택 - 1인당 10 USDT(즉시 출금 가능) 📅 이벤트 기간 - 참여 조건을 모두 충족한 선착순 100명까지 지급 🚨 주의사항 - 최초 가입자만 해당(중복 계정 X) - 선착순 100명 도달 시 이벤트 종료와 동시에 즉시 지급 🔅추가혜택 - 조건 완료 되면 관점공유방 입장 가능 - 30명 치킨 기프티콘 증정
🚨 엔비디아 전 CEO 젠슨 황이 미국 의회에 출석해 증언하기로 동의했다고 공화당 의원이 밝힘.
👍6❤1
엔비디아 -14% ➡️ -5% 속슬 -10% ➡️ 양전 코 앞 나스닥은 정말 정말 신이구나….
❤8👍1
Showing the 12 most recent of 690 posts we hold for @chavoonnam. 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.
@chavoonnam edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
현재 포지션
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
현재 포지션
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
중간선거 있는 이번주
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
비트코인
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 690 most recent posts we hold, published 4 August 2026 to 13 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Republishes 51 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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 5 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 24 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 14 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“차분남(차트분석하는남자)” (@chavoonnam), 21,087 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/chavoonnam.
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.