National news — 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 85% 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.
Observations
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.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 12 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
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. 19 of the 19 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 352 comparable posts for this entry, running 5 August 2026 to 13 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.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @magonia_b — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 15 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.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
65 measurements spanning 102 days, net -1,536. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 25,636–27,632 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
15 Nov 2026, 19:00
25,866
-298
12 Nov 2026, 11:46
26,164
-25
10 Nov 2026, 07:39
26,189
-40
8 Nov 2026, 23:08
26,229
-14
7 Nov 2026, 17:47
26,243
-8
6 Nov 2026, 18:10
26,251
+5
5 Nov 2026, 18:51
26,246
-18
4 Nov 2026, 16:54
26,264
-40
3 Nov 2026, 15:01
26,304
-263
2 Nov 2026, 14:26
26,567
-19
1 Nov 2026, 15:49
26,586
-10
31 Oct 2026, 13:41
26,596
-18
30 Oct 2026, 12:31
26,614
-171
29 Oct 2026, 15:59
26,785
-9
28 Oct 2026, 15:05
26,794
+3
27 Oct 2026, 13:48
26,791
-13
26 Oct 2026, 13:59
26,804
-5
25 Oct 2026, 12:16
26,809
-2
23 Oct 2026, 15:20
26,811
+16
22 Oct 2026, 18:07
26,795
first reading
Engagement
882 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 159 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
4.70%
avg views ÷ 25,866 subscribers
Avg views / post
1,220
275 posts measured
Reaction rate
0.431%
reactions ÷ views · ER floor
Posts in window
275
of 882 held
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 197 of 275 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 15 November 2026
Posts held
882 (5 August 2026 – 15 November 2026)
Views total
334,315
Reactions total
1,068
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
15 Nov 2026, 17:54 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.
What this channel posts
Video runtime
23m 15s
Average length
1m 06s
Measured directly from 21 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.
Reaction mix
4,265 reactions across 639 posts, in 27 distinct kinds. The most used accounts for 75.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
3,208
75.2%
👍
402
9.43%
🔥
233
5.46%
🤣
79
1.85%
👎
67
1.57%
😁
51
1.20%
👏
45
1.06%
🤯
45
1.06%
😱
28
0.657%
😭
24
0.563%
💩
22
0.516%
🤡
13
0.305%
😇
12
0.281%
🥰
8
0.188%
👌
5
0.117%
🙏
4
0.094%
😎
3
0.07%
🤩
3
0.07%
🍌
2
0.047%
💊
2
0.047%
7 further kinds
9
0.211%
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 664 of the 882 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 4,311 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 882 most recent posts we hold, published 5 August 2026 to 15 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.
Recent posts
Telegram’s own ‘edited’ marker: 22 of 275 posts held from the last 30 days (8.00%) 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).
💡다음 금융시장은 무엇을 거래하게 될까? source
1. 현재 크립토 시장에서 가장 거래가 활발한 분야는 무기한 선물과 밈코인임. 그러나 향후 3년간 이들의 성장 배수는1.5배와 1.1배에 불과함. 이미 거대한 시장이 형성된 만큼 경쟁도 치열하고, 새로운 성장 여력도 제한적임
2. 반면 아직 시장이 제대로 형성되지 않은 분야들의 성장 잠재력은 큼. 중요한 건 AI 관련 산업이 성장한다는 사실 자체가 아님. 산업이 커지면서 그동안 거래할 필요조차 없었던 것들이 새로운 금융상품으로 등장할 수 있다는 점
2. 기업에게 GPU 사용료와 추론 비용은 원가이고, 데이터센터에게 전기요금은 핵심 비용 변수임. 임대료/전력 가격 급등 위험이 있다면 헤지하려는 수요가 뒤따름. 석유와 곡물, 환율과 금리의 변동성을 관리하기 위해 파생상품이 탄생했던 것과 …
이번 하락 원인 추측들
A. 앤트로픽 IPO 유동성 흡수 / 바이낸스 해킹 후 자금난으로 청산 유도 / 블랙먼데이
https://t.me/doratman18/5047
B. 미국쪽의 큰 자금 이탈 흐름 / BTC 초기지갑 개인키 탈취
https://t.me/ewlreads/1629
🔤 백팩 미국 청산소 라이선스 승인 ㄷㄷㄷㄷ
CFTC가 백팩 클리어링(TLD Clearing)을 DCO로 정식 등록했습니다! 신청한 지 약 7개월 반만이네요
DCO는 쉽게 말하면 선물 거래가 체결된 뒤 돈이 제대로 오가도록 보증해주는 청산소입니다!
작년부터 새로 등록된 청산소 11곳 중 코인베이스, ICE, 제미나이 등 10곳은 100% 담보를 넣는 선물만 청산할 수 있는데, 백팩만 증거금 선물까지 허가받았습니다 ㄷㄷㄷㄷ
증거금 선물은 레버리지가 허용된다는 뜻이라, 미국에서 Perp를 제대로 하려면 꼭 필요한 조건입니다.
남은 건 거래소(DCM)랑 선물중개업(FCM) 등록 두 개!
청산소 라이선스 먼저 뚫었으니 차근차근 잘 가고 있는 듯??🚀
https://www.cftc.gov/IndustryOversight/IndustryFil…
💬AI 버블론이 놓친 것 (feat. 닷컴버블) source
1. 닷컴버블 당시 투자자들이 상상했던 미래는 틀리지 않았음. 인터넷은 세상을 바꿨지만, 시장이 너무 앞서간 탓에 나스닥이 전고점을 회복하는 데 무려 15년이 걸렸음
2. 지금 AI와 관련 기업들도 버블일 수 있음. 하지만 버블이라 해도 이번에도 미래가 현실을 따라잡기까지 10년 이상 기다려야 할까? 그렇지 않을 것. AI는 지수적 기술이기 때문
3. 결정적인 차이는 기술의 발전 속도 자체가 가속하고 있다는 것임. Epoch AI의 연구에서도 4개 역량 지표 중 3개에서 발전 속도의 가속이 관찰됐음
4. 지능의 가격마저 폭락하고 있음. 동일한 수준의 AI 성능을 이용하는 비용은 2023년 이후 분기에 절반씩 하락했음. 성능은 급등하고 비용은 급락 중임
5. 불과 몇 년 전만…
진짜 거래소에 주식 올라오는게 다행인게
코인 주식 섞어서하니까 견문이 넓어지고 공부할게 아직도 너무 많음
알빠노 해버릴수있는게 다행이라고 느끼는 중
몇년이 지나면 결국 주식쪽으로 넘어가겠지만 그전까지는 AI활용하면서 열심히 두 섹터 파보는 계기가 되길
그래서 주식 하는 형님들 방이 텔그에 남아있는게 매우매우 감사하다고 느끼고 있어용
🐃 쌩매매러 입장에서도 코인의 큰 메리트가 사라지긴 했어요.
제가 느낀 코인의 메리트는 24시간+빠른사이클+변동성 + 구조적인부분에서 오는 이점(김프매매,각종 아비트리지 등등)이라 생각이 됩니다.
이제 주식도 24시간도 돌아가고, 변동성도 코인보다 크고 안정적이에요.
구조적인부분에서 오는 이점도 사람들이 점점 깨달아서 그런지 유동성빠지면서 먹을 파이가 없어지기도 하고 AI 발전으로 그마져도 안정화 된거 같습니다.
변동성이 쌘 알트코인들은 거의 과거 잡거래소 다단계코인 해쳐먹는거랑 다를게 없는 너무 공정하지않는 금융사기에 가깝습니다.
메이저 코인들은 사람들이 깨달음을 점점 얻고 rwa로 넘어가면서
유동성도 메마르고 있고 변동성도 죽어버렸습니다.
개인적으로 크립토의 투기적 가치가 트레이딩 자산으로 적합하다고
생각하는편이었는데, 지금은 …
요즘 AI로 뭘 만들든 한 가지를 같이 생각합니다. 이걸 잘해서 생기는 엣지가 얼마나 오래 갈까?
도구 쓰는 요령이나 프롬프트 우회법은 길어야 몇 주라고 봅니다. 어제까지 프롬프트를 세 번 꼬아서 시키던 일을 모델 업데이트 한 번에 한 줄로 할 수 있게 되니까요.
오케스트레이션은 한 반년쯤 더 봅니다. 어떤 모델에 일을 넘길지, 에이전트를 어떻게 지휘하고 스킬을 어디에 연결할지. 아직 이걸 실제로 묶어 쓰는 사람은 소수라 지금은 엣지가 있습니다. 다만 이 기능들도 모델과 제품 안으로 빠르게 들어오고 있죠.
취향이나 품질을 가르는 감도 지금은 사람 쪽에 우위가 있다고 봅니다. 결과물을 보고 어디가 어색한지, 뭘 빼야 더 좋아지는지 판단하는 데서 차이가 꽤 나요. 이 차이도 한 반년은 갈까 싶습니다. 도메인에서 쌓은 엣지도 비슷합니다. 시장…
믿을수가 없네요 소설보다 더 소설같은..
젠슨 황 엔비디아 최고경영자(CEO)와 부적절한 관계를 맺은 중국계 여성 앨리스 황(중국명 황러·黄樂)이 중국 최고 정보기관인 국가안전부 내 반도체 전담 공작 조직 요원인 것으로 알려졌다. 황러가 젠슨 황과 쌓은 사적 유대를 무기로 미국의 수출 통제망을 뚫고 약 10조 원어치에 달하는 첨단 반도체를 중국으로 빼돌렸을 뿐 아니라, 미국 정부의 대중국 수출 규제 완화까지 유도하려 했다는 구체적인 정황도 드러났다. 단순한 개인 간 스캔들로 치부됐던 이번 사태가 미국 인공지능(AI) 기술 패권을 무너뜨리려는 중국 최고위층의 치밀한 국가급 정보전이었다는 분석에 힘이 실린다.
자유시보는 미국 측이 입수한 정보와 관계자를 인용해 중국 공산당 중앙판공청이 미국과 AI 패권 경쟁에서 우위를 점하기 위해 범정부 특…
천연가스 개떡상 중 ㄷㄷㄷㄷㄷ
미국: 역대 가장 이른 극소용돌이 붕괴로 한파가 평소보다 이르게 찾아올 예정
유럽: 10여년 만에 가장 낮은 가스 재고로 한파 맞이할 예정
러시아: 남아 있는 유일한 가스관으로는 유럽 주요국을 제외한 일부에만 공급.
배로 운송하는 LNG는 아직 프랑스·스페인·네덜란드 등으로 공급되지만 EU가 올해부터 신규 계약을 금지, 단기계약은 이미 4~6월에 끝남.
장기계약도 LNG는 2027년 1월, 가스관은 2027년 가을까지만 허용.
심지어 우크라이나 가스·에너지 시설을 일주일에 128번이나 타격.
러시아 입장에서는 뻐기기만 해도 개이득인데 종전을 할까요??
이번 겨울은 역대급 추운 겨울이 될 것임.
인플레이션...잡히는 걸 기대하면 흑우겠지?
Opus가 말아주는 USDe 레버리지 루프 08년도 MMF와 닮은 점
1. 장부가 1달러로 고정돼 있다 (MMF의 상각원가 NAV와 같은 역할)
Aave의 리스크 매니저 LlamaRisk도 이 점을 직접 지적했습니다. Ethena 백킹이 근본적으로 실패해 USDe 시장가가 무너져도 Aave가 쓰는 USDT/USD 오라클은 약 1달러에 머문다는 겁니다. Reserve Primary Fund도 리먼 CP가 휴지가 된 순간까지 장부상으로는 1달러였습니다.
2. 하드페그 때문에 리스크가 루퍼에게서 대출자에게로 옮겨간다
담보 가격이 고정이고 sUSDe 환율은 오르기만 하니까, 스테이블을 빌린 루퍼는 가격 때문에 청산될 일이 거의 없습니다. 그만큼의 꼬리 리스크는 Aave에 USDC/USDT를 공급한 쪽, 즉 MMF 투자자 자리에 앉은 사람들이…
Showing the 12 most recent of 882 posts we hold for @magonia_b. 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.
Posts edited after publishing
@magonia_b 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.
First edit seen
13 October 2026
Most recent edit
13 October 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 104 registered channels. The 48 listed are the ones that have forwarded the most posts; 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.
Mentions
Named by 19 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.
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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@magonia_b named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@centrifuge named in 1 post, 10 October 2026 – 10 October 2026
@backpack_kr_fan named in 1 post, 19 August 2026 – 19 August 2026
Channels Telegram recommends alongside this one
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 11 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.
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.
30대에 은퇴번복한 머피 @murphybus · 19,883 Telegram ranks this channel #1 of 88 here — alongside 87 others — read 28 September 2026
신기술은 돈이 된다 공지방 @tlsrltnf · 22,343 Telegram ranks this channel #1 of 86 here — alongside 85 others — read 20 September 2026
폐지줍기 연구소 @airdr0p_lab · 20,446 Telegram ranks this channel #2 of 88 here — alongside 87 others — read 26 September 2026
갓물주 (코인정보, 돈되는거) @godmulzoo · 22,670 Telegram ranks this channel #2 of 81 here — alongside 80 others — read 19 September 2026
잼민123🦅 @mujammin123 · 25,711 Telegram ranks this channel #4 of 86 here — alongside 85 others — read 13 September 2026
DeFi 농부 👨🏻🌾 조선생 @BSC_Farmer_KR · 20,192 Telegram ranks this channel #5 of 88 here — alongside 87 others — read 26 September 2026
불개미 CRYPTO @fireant_crypto · 32,684 Telegram ranks this channel #5 of 92 here — alongside 91 others — read 4 September 2026
코인같이투자 정보 에어드랍🦋 @WeCryptoTogether · 48,126 Telegram ranks this channel #5 of 90 here — alongside 89 others — read 25 August 2026
에어드랍코리아 (Airdropkorea) @airdrop_kor · 21,207 Telegram ranks this channel #6 of 84 here — alongside 83 others — read 24 September 2026
우리는 트윗충 @twitchoong · 79,159 Telegram ranks this channel #6 of 91 here — alongside 90 others — read 25 August 2026
취미생활방📮 @enjoymyhobby · 48,799 Telegram ranks this channel #6 of 92 here — alongside 91 others — read 25 August 2026
졸업준비위원회🎓 @officialunivercityofcrypto · 22,651 Telegram ranks this channel #8 of 86 here — alongside 85 others — read 19 September 2026
새우잡이어선 공지방 @shrimp_notice · 28,266 Telegram ranks this channel #8 of 93 here — alongside 92 others — read 9 September 2026
텔레그램 코인 방,채널 - CEN @emperorcoin · 35,440 Telegram ranks this channel #9 of 91 here — alongside 90 others — read 19 August 2026
마샬 공유방 2.0 @marshallog · 21,351 Telegram ranks this channel #11 of 81 here — alongside 80 others — read 22 September 2026
해달의 투자 정보 공유 @seaotterbtc · 29,986 Telegram ranks this channel #11 of 94 here — alongside 93 others — read 7 September 2026
에어드랍ATM @Bounty_ATM · 25,790 Telegram ranks this channel #13 of 79 here — alongside 78 others — read 14 September 2026
크립토퀀트 알람 @cq_alert_kr · 21,577 Telegram ranks this channel #15 of 83 here — alongside 82 others — read 22 September 2026
코인 갤러리(Coin gallery) @dogeland01 · 20,884 Telegram ranks this channel #16 of 85 here — alongside 84 others — read 24 September 2026
Layergg exchange & project alert @layergg · 19,277 Telegram ranks this channel #17 of 91 here — alongside 90 others — read 1 October 2026
블록미디어 @blockmedia · 32,879 Telegram ranks this channel #18 of 90 here — alongside 89 others — read 4 September 2026
ZAP Tech News @zaponblast · 62,737 Telegram ranks this channel #19 of 82 here — alongside 81 others — read 21 August 2026
Gram 🇰🇷 @toncoin_kr · 22,891 Telegram ranks this channel #24 of 88 here — alongside 87 others — read 30 September 2026
차분남(차트분석하는남자) @chavoonnam · 21,065 Telegram ranks this channel #24 of 80 here — alongside 79 others — read 24 September 2026
This channel appears in 33 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.
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 15 November 2026 — this
entry's latest reading, not the date you are reading this.
“기분좋은 마곤” (@magonia_b), 25,866 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/magonia_b.
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.