레버리지의 위험성
🤣2🖕1
Signed 뺀지뤼 !

Channel
@bbanjil
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
10,681subscribers
-80 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001500265128 |
|---|---|
| Type | Channel |
| Username | @bbanjil |
| Description | 아는 것 없고 인사이트 없고 주식도 못해서 다른 분들의 좋은 자료들을 엄선해서 스크랩하는 채널입니다. 스크랩한다고 해서 제 의견이 아닙니다. * 본 채널의 게시물은 단순 의견 및 기록용으로 매수-매도 등 투자권유를 의미하지 않습니다. 해당 게시물의 내용은 부정확할 수 있으며 매매에 따른 손실은 거래 당사자의 책임입니다. 해당 게시물의 내용은 어떤 경우에도 법적 근거로 사용될 수 없습니다. |
| Created | 30 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 2 times, most recently 5 November 2026 |
| On Telegram | t.me/bbanjil |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 17:16 | 10,681 | -6 |
| 3 Nov 2026, 16:07 | 10,687 | -3 |
| 2 Nov 2026, 14:09 | 10,690 | -1 |
| 1 Nov 2026, 15:45 | 10,691 | -5 |
| 31 Oct 2026, 14:01 | 10,696 | -1 |
| 30 Oct 2026, 16:49 | 10,697 | -5 |
| 29 Oct 2026, 15:11 | 10,702 | -1 |
| 28 Oct 2026, 13:20 | 10,703 | +1 |
| 27 Oct 2026, 14:49 | 10,702 | -3 |
| 26 Oct 2026, 13:45 | 10,705 | -2 |
| 25 Oct 2026, 15:59 | 10,707 | +1 |
| 24 Oct 2026, 17:35 | 10,706 | -8 |
| 23 Oct 2026, 14:14 | 10,714 | -3 |
| 22 Oct 2026, 15:59 | 10,717 | -3 |
| 21 Oct 2026, 11:48 | 10,720 | +3 |
| 20 Oct 2026, 06:11 | 10,717 | -2 |
| 18 Oct 2026, 10:11 | 10,719 | +3 |
| 15 Oct 2026, 10:41 | 10,716 | -2 |
| 14 Oct 2026, 10:45 | 10,718 | -3 |
| 12 Oct 2026, 21:28 | 10,721 | first reading |
613 posts held, back to 7 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 45 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 41 of 97 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 613 (7 August 2026 – 5 November 2026) |
| Views total | 34,799 |
| Reactions total | 68 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 20:27 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 5 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 3 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.
513 reactions across 218 posts, in 20 distinct kinds. The most used accounts for 25.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 129 | 25.1% | |
| 👍 | 92 | 17.9% | |
| 🖕 | 88 | 17.2% | |
| 😁 | 79 | 15.4% | |
| 💩 | 40 | 7.80% | |
| 🤮 | 35 | 6.82% | |
| 👎 | 12 | 2.34% | |
| 🤬 | 7 | 1.36% | |
| 💯 | 6 | 1.17% | |
| 😱 | 6 | 1.17% | |
| 🤣 | 4 | 0.78% | |
| 🍌 | 3 | 0.585% | |
| 👏 | 2 | 0.39% | |
| 😈 | 2 | 0.39% | |
| 😭 | 2 | 0.39% | |
| 🙏 | 2 | 0.39% | |
| 🎃 | 1 | 0.195% | |
| 😇 | 1 | 0.195% | |
| 😢 | 1 | 0.195% | |
| 🤔 | 1 | 0.195% |
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 232 of the 613 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 513 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 613 most recent posts we hold, published 7 August 2026 to 5 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: 1 of 97 posts held from the last 30 days (1.03%) 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).
레버리지의 위험성
🤣2🖕1
Signed 뺀지뤼 !
VIX 지수 하루 상승폭 68% 기록 역대 3번째 기록이 될지는 장 마감까지 지켜봐야. VIX 역대 일간 상승폭 순위 1. 2018년 2월 5일/+115.60% 역사상 최대 일일 상승률 기록. 지정학적 위기나 경제 붕괴가 아니라, 금융 상품의 구조적 결함이 유발한 연쇄 폭발이라는 점에서 '볼마게돈(변동성+아마게돈)'으로 불림. 2. 2024년 12월 18일/+74% - 연준이 FOMC 회의에서 25bp 금리 인하를 단행했으나, 향후 전망에 대해 시장 예4보다 훨씬 매파적 입장을 내놓음. 특히 시장은 2025년 연간 금리 인하 횟수를 4회로 예상했으나, 연준은 이를 단 2회로 축소. - 여기에 미 대선 이후 차기 트럼프 행정부의 관세 부과 정책이나 무역 전쟁 가능성 등 거시경제적 정책 불확실성 상존. 3. 2026년 11월 6일/+68…
Signed 뺀지뤼 !
#SOXX #필라델피아반도체 20261106 중기 하방 클라이막스
🖕2
Signed 뺀지뤼 !
오늘의 하락 알고리즘 1. 트렌드포스에서 낸드메모리 ASP 떨어진다는 레포트 냄 2. 가격 떨어지는게 최대 악재인 메모리 주가 급락 3. 관련 데이터센터 및 AI 관련주 급락 4. 나스닥 급락 5. 비트코인 급락 *비트고인이 뭘 잘못했는데?!
🖕1
Signed 뺀지뤼 !
속보: 암호화폐 시장 폭락 비트코인(BTC) 5.85% 하락 이더리움(ETH) 7.45% 하락 엑스리프(XRP) 4.95% 하락 솔(SOL) 6.20% 하락 지난 4시간 동안 8억 7천만 달러 이상의 레버리지 암호화폐 포지션이 청산되었습니다. ...
🤮1
Signed 뺀지뤼 !
#블교수 미스터 비토의 몽니와 쪼개진 MAGA, 한국에 미치는 영향은? https://blog.naver.com/hwasikyuljeon/224466593555 미국 중간선거가 한국에 미칠 영향을 써봤습ㄴ디ㅏby 블교수
🤮1
Signed 뺀지뤼 !
😴
Signed 뺀지뤼 !
#농구천재 님 숙면투자 https://m.blog.naver.com/tosoha1/224466411036
🖕2
Signed 뺀지뤼 !
① 민주당 승리 ≠ 트럼프 산업정책 폐기 행정권에 기반한 관세·규제 완화·대중국 견제는 유지될 가능성이 높지만, 신규 법률과 재정지원이 필요한 정책은 제약을 받을 전망. ② 수혜는 산업 전체보다 특정 제품·사업에 집중 반도체의 AI 수요, 철강의 송전망·LNG용 강재, 조선의 함정 MRO 등이 상대적으로 유리하게 제시됨. 반대로 미국 현지화 비용과 세제 불확실성은 기업별 수익성 차이를 확대할 요인. ③ 방산·조선은 정책 방향보다 예산 집행을 확인할 필요 미국 군비 현대화와 조선업 재건 기조는 지속되지만, 신규 증액과 조달 일정은 의회 협상에 종속될 수 있음. 따라서 수주 기대와 실제 발주·매출 인식은 구분해야 함. ④ 가장 중요한 관찰 시점은 2027년 상반기 12월 11일 임시예산 만료 이후의 협상, 신규 의회 출범, FY2027…
Signed 뺀지뤼 !
Cnn Fear & Greed Index
Signed 뺀지뤼 !
아니 무슨 국장인가 싶을정도로 꼴박인데요..
🤣2😁1😱1
Signed 뺀지뤼 !
프랑스 마크롱 정부 예산안 근황
Signed 뺀지뤼 !
Showing the 12 most recent of 613 posts we hold for @bbanjil. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
현 시각 귀하의 선택은
The shares total 120%, 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 613 most recent posts we hold, published 7 August 2026 to 5 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 149 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 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.
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.
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 48 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“뺀지뤼의 SKLab.(스크랩)” (@bbanjil), 10,681 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/bbanjil.
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.