근데 이러면 당장 수능은 어떻게 되려나요? 👀 EMP라도 쏴야하나... #수능 #AI안경
👀3🔥2

Channel
@marshallog
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
21,370subscribers
-795 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001519612053 |
|---|---|
| Type | Channel |
| Username | @marshallog |
| Description | 리딩방 아닙니다. 경제, 금융, 크립토, 시사 등 다양한 분야의 정보를 공유하며 같이 공부하는 방입니다. 🙏 협업/광고 문의 @korea_duck |
| Created | 19 August 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/marshallog |
Other / unclassifiable — 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 52% 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 6 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 |
|---|---|---|---|
| @enjoymyhobby/9820329 Oct 2026, 12:23 UTC | @marshallog/23524 · this entry29 Oct 2026, 12:38 UTC | 1.00 | 14 minutes |
| @marshallog/23531 · this entry31 Oct 2026, 11:48 UTC | @enjoymyhobby/9823231 Oct 2026, 12:19 UTC | 1.00 | 31 minutes |
| @marshallog/23558 · this entry8 Nov 2026, 20:52 UTC | @enjoymyhobby/983518 Nov 2026, 22:21 UTC | 1.00 | 89 minutes |
| @WeCryptoTogether/654025 Aug 2026, 10:54 UTC | @marshallog/23077 · this entry5 Aug 2026, 11:04 UTC | 1.00 | 10 minutes |
| @marshallog/23077 · this entry5 Aug 2026, 11:04 UTC | @leedogin2/232455 Aug 2026, 12:02 UTC | 1.00 | 58 minutes |
| @minchoisfuture/557925 Nov 2026, 17:48 UTC | @marshallog/23549 · this entry5 Nov 2026, 18:20 UTC | 1.00 | 32 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @enjoymyhobby | 5 (5/5 hand-verifiable sample passed) | 1.00 | 14 minutes | this entry (4–1) |
| @WeCryptoTogether | 9 (8/8 hand-verifiable sample passed) | 1.00 | 10 minutes | @WeCryptoTogether (8–1) |
| @leedogin2 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 58 minutes | this entry (7–0) |
| @minchoisfuture | 7 (7/7 hand-verifiable sample passed) | 1.00 | 14 minutes | @minchoisfuture (5–2) |
| @airdr0p_lab | 5 (5/5 hand-verifiable sample passed) | 1.00 | 7 minutes | @airdr0p_lab (5–0) |
| @xvgwhitedog2 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 1.8 hours | this entry (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. 1 of the 1 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 149 comparable posts for this entry, running 4 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 keys clone_copy · clone_mutual · clone_source, 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 |
|---|---|---|
| 10 Nov 2026, 11:58 | 21,370 | -10 |
| 8 Nov 2026, 23:01 | 21,380 | -13 |
| 7 Nov 2026, 12:26 | 21,393 | -10 |
| 6 Nov 2026, 15:57 | 21,403 | -16 |
| 5 Nov 2026, 16:15 | 21,419 | -9 |
| 4 Nov 2026, 16:18 | 21,428 | -10 |
| 3 Nov 2026, 15:25 | 21,438 | -4 |
| 2 Nov 2026, 11:49 | 21,442 | -8 |
| 31 Oct 2026, 15:37 | 21,450 | -3 |
| 30 Oct 2026, 13:11 | 21,453 | -13 |
| 29 Oct 2026, 11:18 | 21,466 | -7 |
| 28 Oct 2026, 12:51 | 21,473 | -5 |
| 27 Oct 2026, 12:05 | 21,478 | -11 |
| 26 Oct 2026, 08:50 | 21,489 | -1 |
| 25 Oct 2026, 05:30 | 21,490 | -4 |
| 24 Oct 2026, 06:48 | 21,494 | -5 |
| 23 Oct 2026, 10:07 | 21,499 | -25 |
| 22 Oct 2026, 12:48 | 21,524 | -14 |
| 21 Oct 2026, 06:56 | 21,538 | -17 |
| 20 Oct 2026, 02:50 | 21,555 | first reading |
346 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 87 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 12 November 2026 |
|---|---|
| Posts held | 346 (4 August 2026 – 12 November 2026) |
| Views total | 83,636 |
| Reactions total | 159 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 03:39 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 12 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 7 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.
1,166 reactions across 270 posts, in 12 distinct kinds. The most used accounts for 56.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 660 | 56.6% | |
| 👍 | 196 | 16.8% | |
| 😭 | 89 | 7.63% | |
| 🔥 | 69 | 5.92% | |
| 🙊 | 49 | 4.20% | |
| 👏 | 35 | 3.00% | |
| 😁 | 25 | 2.14% | |
| 👀 | 17 | 1.46% | |
| 🙏 | 11 | 0.943% | |
| 👌 | 7 | 0.6% | |
| 🥰 | 5 | 0.429% | |
| 🕊 | 3 | 0.257% |
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 287 of the 346 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,212 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 346 most recent posts we hold, published 4 August 2026 to 12 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Measured over the 346 most recent posts we hold, published 4 August 2026 to 12 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
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).
근데 이러면 당장 수능은 어떻게 되려나요? 👀 EMP라도 쏴야하나... #수능 #AI안경
👀3🔥2
일단은 세무사 시험만 뉴스에 나오고 있지만, 한 해에 90명 뽑는 관세사 시험에서 올해 10명이 생동차 합격이었고, (로스쿨 갈 생각도 없던 사람이) 20년만에 LEET 전영역에서 만점을 받았다는 소식도 있었다. https://n.news.naver.com/mnews/article/008/0005440002?sid=102 https://gall.dcinside.com/mgallery/board/view/?id=cta&no=148367 (AI 안경 치팅이 만연하다는 증거)
👍3
⚾️ 에테나 x 아발란체 x 월드비전 러닝 기부 캠페인 Source 달린 거리만큼 기부금 적립해 월드비전에 $AVAX 로 전액 기부하는 캠페인 러너 20명 모집 중 ➡️ Web3 Run for Good 참가 신청 링크 📔 캠페인 정보 · 11월 27일 오후 7시 30분 시작 · 총 6km 러닝 진행 · 평균 페이스는 8분대로 누구나 부담없는 속도 · 1인, 1km마다 4,000원 기부금 적립 · 러닝 도중 러닝메이트와 질문지 통해 네트워킹 ✍️ 20명만 모집하고 승인제라 참석하셔서 뛰실 분들만 신청 고고 #Ethena #Avalanche #이벤트
👌2
🙃 맨틀 총 $4,000 상당 상금 콘텐츠 바운티 진행중 Source #AD 12월 8일까지 (현재 진행중) 총 상금 $4,000 상당 $MNT 수상자 총 19명 📔 콘텐츠 바운티? · 리서치, 글, 디자인, 영상, 분석, 밈 등 자유 형식 · 2026년 맨틀 트위터 게시물 중 하나 고르기 · 해당 게시물 인용해 본인 관점과 함께 포스팅 · 게시 후 폼 통해 링크 제출 ✍️ 요새 이런 것도 많이 사라져서 뜸했는데 돌아온 맨틀의 콘텐츠 바운티네요 구글폼 내 노션에 따로 심사 기준도 나와있으니 확인해보시고 노려보실 분들은 도전해보시죠 #Mantle #이벤트
❤3
해외 트윗에서는 zec 관련한 무지성 실링이 좀 많은 편인데 여기서 노이즈을 느낀 전 메사리 리서쳐 sam이 글을 하나 게시했네요 (사진은 샘이 인용한 qw의 zec 불포스팅) 솔직히 이 전망이 zcash의 전체 문제점이고, 왜 모두가 제대로 준비하지 못했는지 보여주는 거야. zec가 보장된 20배 수익이라는 기대. 그건 터무니없어. btc 외에 SoV라는 건 존재하지 않아. 다음 SoV가 나올수록 그 라벨의 가치가 떨어져. 그냥 밈코인일 뿐이야. 진짜 프라이버시에 관심 있다면, zec로 포트폴리오 전체를 구성하지 않고도 돈을 훨씬 편리하게 프라이빗하게 옮길 방법이 많아. 그리고 여기 20명의 KOL들이 근거 없는 가격 목표를 내놓고, HODL 하라고 하면서 (익숙한 소리지?) 트레이더들은 영원히 가난할 거라고 해. 제발 그만해. 난 …
❤1
#속보🚨 미국 소비자물가지수(CPI): 전년 대비 +3.9% 상승 (추정치) 미국 근원 소비자물가지수(CORE CPI): 전년 대비 +2.8% 상승 (추정치) AI+ : 미국 CPI·근원 CPI 실제 수치가 누락돼 금리·인플레이션 충격 판단은 제한적이며, 나스닥 선물은 2.76% 상승했다. 관련 : $USD, $DXY #미국, #인플레이션, #GDP/인플레이션데이터발표, #연준 2026-11-10 22:30:04 ✈ 빠른속보, 특파원김씨
😭2❤1
[속보] 금융보안원도 해킹으로 정보유출 https://n.news.naver.com/mnews/article/015/0005352488?sid=001
👍4
예전부터 말했지만 해킹도 잦은 요즘 시기에 더더욱 잡거래소 사용은 피하는게... 투자하는데 굳이 저기까지 가야한다 라고 하면 그건 어딘가 이상한거라 생각함 적당히 털려도 갚아줄 능력 있는 거래소들도 무서운 시기인데, 오히려 고객을 터는 거래소는...😊
지금 이슈되는 거래소 두개가 있네요. MEXC LBANK MEXC : 사용하지말라는 내용 https://x.com/WuBlockchain/status/2120074475794554960 LBANK : 돈 먹튀 이슈 https://x.com/solyfw34/status/2120005755990597794 특히 MEXC 경우 여기서 입출금 잘못했다가 다른 거래소 자금도 문제생길수있으니 매우 조심해야한다고 봅니다. 매우.
빗썸(Bithumb) 공지 하이퍼리퀴드(HYPE), 콜렉터크립트(CARDS) 원화 마켓 추가 2026-11-10 14:13:56
❤2
$HYPE listed on Upbit spot (KRW)・
❤2
😆 빗썸, 국가고객만족도 1위 가상자산거래소 빗썸은 한국생산성본부 2026 국가고객만족도(NCSI) 조사에서 올해 처음 신설된 '디지털자산거래소 부문' 최초 1위에 선정됐다고 10일 밝혔다. 올해 금융 업종에 디지털자산거래소 부문이 처음 신설된 가운데, 빗썸이 조사 대상 기업 중 가장 높은 점수를 받아 초대 1위에 올랐다. 빗썸 뭐 1위했다고해서 뭐지해서 봤는데 국가고객만족도 조사에서 1등했다고 함, 장 분위기만 좋으면 이벤트 기대했을텐데... 아쉽네 😭 #빗썸 #광고아님
👍2❤1👏1🔥1
Showing the 12 most recent of 346 posts we hold for @marshallog. 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.
Republishes 63 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 10 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 22 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 30 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“마샬 공유방 2.0” (@marshallog), 21,370 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/marshallog.
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.