삼가 고인의 명복을 빕니다.
❤25
Signed 카가

Channel
@gatubang
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
14,537subscribers
-59 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001370641552 |
|---|---|
| Type | Channel |
| Username | @gatubang |
| Description | 본 채널의 게시물은 단순 의견 및 기록용도이고 매수-매도 등 투자권유를 의미하지 않습니다. 해당 게시물의 내용은 부정확할 수 있으며 매매에 따른 손실은 거래 당사자의 책임입니다. 해당 게시물의 내용은 어떤 경우에도 법적 근거로 사용될 수 없습니다. |
| Created | 3 November 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 57 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/gatubang |
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 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 12 other registered channels. This entry also sits inside a group of 6 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 |
|---|---|---|---|
| @gatubang/53937 · this entry14 Aug 2026, 07:46 UTC | @mstaryun/1038314 Aug 2026, 07:46 UTC | 1.00 | under a minute |
| @gatubang/53695 · this entry5 Aug 2026, 22:46 UTC | @triple_stock/167526 Aug 2026, 04:17 UTC | 1.00 | 5.5 hours |
| @gatubang/53695 · this entry5 Aug 2026, 22:46 UTC | @jake8lee/135246 Aug 2026, 03:50 UTC | 1.00 | 5.1 hours |
| @gatubang/53695 · this entry5 Aug 2026, 22:46 UTC | @ym_research/63055 Aug 2026, 22:55 UTC | 1.00 | 9 minutes |
| @EarlyStock1/849812 Nov 2026, 12:36 UTC | @gatubang/55138 · this entry12 Nov 2026, 13:10 UTC | 1.00 | 34 minutes |
| @gaoshoukorea/6567011 Nov 2026, 02:40 UTC | @gatubang/55114 · this entry11 Nov 2026, 02:50 UTC | 1.00 | 10 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @free_life59 | 22 (8/8 hand-verifiable sample passed) | 1.00 | 6 minutes | this entry (12–10) |
| @mstaryun | 8 (8/8 hand-verifiable sample passed) | 1.00 | 14 minutes | @mstaryun (5–3) |
| @cahier_de_market | 11 (8/8 hand-verifiable sample passed) | 1.00 | 18 minutes | @cahier_de_market (7–4) |
| @triple_stock | 9 (8/8 hand-verifiable sample passed) | 1.00 | 40 minutes | @triple_stock (5–4) |
| @jake8lee | 15 (8/8 hand-verifiable sample passed) | 1.00 | 21 minutes | this entry (11–4) |
| @Kyaooo | 11 (8/8 hand-verifiable sample passed) | 1.00 | 34 minutes | this entry (8–3) |
| @mimi_ATH | 14 (8/8 hand-verifiable sample passed) | 1.00 | 4 minutes | @mimi_ATH (14–0) |
| @kkkontemp | 24 (8/8 hand-verifiable sample passed) | 1.00 | 18 minutes | @kkkontemp (24–0) |
| @nje2e | 21 (8/8 hand-verifiable sample passed) | 1.00 | 33 minutes | this entry (11–10) |
| @ym_research | 5 (5/5 hand-verifiable sample passed) | 1.00 | 14 minutes | @ym_research (4–1) |
| @EarlyStock1 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 21 minutes | @EarlyStock1 (4–2) |
| @bornlupin | 19 (8/8 hand-verifiable sample passed) | 1.00 | 18 minutes | @bornlupin (16–3) |
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. 6 of the 6 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 198 comparable posts for this entry, running 5 August 2026 to 12 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.
Of the group of 6 channels, the one whose matching posts we hold earliest is @kkkontemp. 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 13 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.
This channel is in a group of 6 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 17:47 | 14,537 | -6 |
| 10 Nov 2026, 11:51 | 14,543 | -3 |
| 9 Nov 2026, 01:59 | 14,546 | +4 |
| 7 Nov 2026, 18:09 | 14,542 | -5 |
| 6 Nov 2026, 16:25 | 14,547 | -11 |
| 5 Nov 2026, 13:57 | 14,558 | -9 |
| 4 Nov 2026, 12:35 | 14,567 | -3 |
| 3 Nov 2026, 10:45 | 14,570 | -5 |
| 2 Nov 2026, 13:06 | 14,575 | -3 |
| 1 Nov 2026, 12:08 | 14,578 | -3 |
| 31 Oct 2026, 14:38 | 14,581 | -2 |
| 30 Oct 2026, 13:05 | 14,583 | -9 |
| 29 Oct 2026, 10:57 | 14,592 | -4 |
| 28 Oct 2026, 12:15 | 14,596 | -1 |
| 27 Oct 2026, 11:56 | 14,597 | -3 |
| 26 Oct 2026, 13:54 | 14,600 | -3 |
| 24 Oct 2026, 11:40 | 14,603 | -3 |
| 23 Oct 2026, 13:06 | 14,606 | -7 |
| 22 Oct 2026, 13:40 | 14,613 | -6 |
| 20 Oct 2026, 07:10 | 14,619 | first reading |
501 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 73 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 51 of 113 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 | 501 (5 August 2026 – 13 November 2026) |
| Views total | 189,612 |
| Reactions total | 280 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 07:43 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.
1,095 reactions across 220 posts, in 6 distinct kinds. The most used accounts for 65.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 717 | 65.5% | |
| 👍 | 177 | 16.2% | |
| 🔥 | 125 | 11.4% | |
| 😍 | 43 | 3.93% | |
| 🎉 | 23 | 2.10% | |
| 💯 | 10 | 0.913% |
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 249 of the 501 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,120 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 501 most recent posts we hold, published 5 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: 2 of 113 posts held from the last 30 days (1.77%) 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).
삼가 고인의 명복을 빕니다.
❤25
Signed 카가
안녕하세요. '체리형부'의 동생입니다. 경황이 없어 이제야 무거운 소식을 전하게 되어 죄송합니다. 지난 11월 6일 금요일, 저희 형님께서 하늘나라로 긴 여행을 떠나셨습니다. 형님께서는 떠나시기 직전까지도 이곳에 계신 분들을 많이 생각하셨습니다. 마지막까지 본인을 믿고 함께해 주신 분들께 '정말 감사했다'는 말을 꼭 전해달라 당부하셨고, 본의 아니게 끝까지 함께하지 못해 너무 미안하다는 말씀도 남기셨습니다. 생전 형님께 이곳은 단순한 교육 공간이 아니라, 마음을 다해 진심을 나누던 가장 소중한 자리였습니다. 곁에서 지켜본 동생으로서 형님이 이곳 분들께 얼마나 진심이셨는지 알기에 더욱 마음이 아픕니다. 체리형부님을 대신하여, 그동안 형님을 믿고 아껴주시며 마지막 길까지 함께해 주신 이곳의 모든 분들께 머리 숙여 깊은 감사의 말씀을 드립니…
❤18
Signed 카가
Photo, posted without a caption
❤1
Signed 카가
✅ 이억원 금융위원장, 증안펀드 가동 신중론…“한시적이고 예외적인 것” https://n.news.naver.com/mnews/article/366/0001204597?sid=001
Signed 카가
무슨 영화도 아니고...ㄷㄷㄷ
🎉2
Signed 카가
https://biz.chosun.com/international/international_economy/2026/11/13/WJ5POQMZZ5G3FALHFLA2VX5VMU/ 젠슨 황 엔비디아 최고경영자(CEO)와 부적절한 관계를 맺은 중국계 여성 앨리스 황(중국명 황러·黄樂)이 중국 최고 정보기관인 국가안전부 내 반도체 전담 공작 조직 요원인 것으로 알려졌다.
😍4
Signed 카가
살다가 이메일이 안되는 날이 올줄은 ... 인프라를 더 깔아라! 🙃
👍6
Signed 카가
좋은 아침입니다!🫡
❤8😍2
Signed 카가
TPU 탑재 HBM이 16GB에서 384GB로 늘었다 | 엔비디아 다음 HBM 큰손 ▶ 구글은 2013년 음성 검색 계산 때문에 TPU를 직접 설계했다. TPU 한 개에 붙는 HBM은 2018년 v2 16GB에서 2026년 8i Max 384GB로 늘었다. ▶ 앤트로픽은 TPU 장비 5년 임대료로 약 1,612억 달러를 약정했고, 모건스탠리는 2027년 HBM을 엔비디아(37.3%) 다음으로 많이 사는 회사를 구글(36.0%)로 추정했다. https://www.youtube.com/watch?v=GFJfOXN4B0Y&list=PLHcPrvlX3LAs 구글 Google $GOOGL 엔비디아 NVIDIA $NVDA TPU HBM 삼성전자 005930 SK하이닉스 000660 앤트로픽 #구글 #엔비디아 #TPU #HBM #삼성전자 #SK하이닉…
Signed 카가
$NVDA - 속보: 엔비디아 CEO 젠슨 황 즉시 사임 엔비디아, 대규모 경영진 개편 발표: 🔸 젠슨 황, CEO, 사장 및 이사회 멤버직 즉시 사임 🔸 콜레트 크레스 엔비디아 CFO, 임시 CEO 임명 🔸 하비 C. 존스, 이사회 의장 임명 🔸 내부 및 외부 후보 고려하여 차기 CEO 물색 시작 황의 사임으로 그가 공동 창립한 AI 칩 거대 기업에서의 33년 경영 시대가 막을 내림
Signed 카가
https://news.einfomax.co.kr/news/articleView.html?idxno=4444469
❤1
Signed 카가
매출은 45배, 컴퓨트 비용은 10배 | 앤트로픽 IPO 로드쇼 ▶ 앤트로픽은 11월 10일 공개한 상장 로드쇼 영상에서 최근 6개 분기 동안 매출이 45배 넘게 늘어나는 사이 컴퓨트 인프라 비용은 10배 늘었다고 밝혔습니다. 올해 1~9월 매출총이익률은 85%, 장기 조정 영업이익률 목표는 35% 이상입니다. ▶ 상장 신고서(S-1/A)에 적힌 컴퓨트·인프라 약정은 약 9,009억 달러이고, 그중 약 4,516억 달러가 2030년 말까지 나갈 돈입니다. 3분기 한 분기 매출은 170억 달러였습니다. ▶ 공모가 범위는 주당 70~78달러, 8억 2,500만 주입니다. 미국 시간 11월 18일 공모가를 정하고 19일 나스닥에서 종목 코드 ANT로 거래를 시작합니다. https://www.youtube.com/watch?v=YSyARcx_E8…
Signed 카가
Showing the 12 most recent of 501 posts we hold for @gatubang. 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.
We recorded 1 post on @gatubang as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 93 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 6 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.
@gatubang named 1 handle 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.
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 6 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.
“가투방(DCTG) 저장소” (@gatubang), 14,537 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/gatubang.
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.