https://m.blog.naver.com/kimcharger/224467337002
👍2

Channel
@triple_stock
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
13,417subscribers
+779 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001603630466 |
|---|---|
| Type | Channel |
| Username | @triple_stock |
| Description | 태크밸리 × 더블알파 × IR Technology × Investment × Company 본 채널에서 언급하는 종목들은 매수/매도를 의미하는 것이 아닙니다. 본 채널에서 언급된 종목은 보유 중이거나 아닐 수도 있습니다. 또한 언제든지 사전 예고없이 매수/매도할 수 있습니다. 투자에 따른 책임은 본인에게 있으며 본 채널의 게시물은 어떠한 경우에도 법적 책임을 묻는 근거 자료로 사용될 수 없습니다. |
| Created | 10 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 52 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/triple_stock |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 71% 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 word for word on 1 other registered channel. 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 |
|---|---|---|---|
| @triple_stock/16742 · this entry4 Aug 2026, 22:55 UTC | @cahier_de_market/103664 Aug 2026, 22:58 UTC | 1.00 | 3 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @cahier_de_market | 5 (5/5 hand-verifiable sample passed) | 1.00 | 22 minutes | @cahier_de_market (4–1) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 4 August 2026 to 7 August 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.
Across the whole group of 2, the earliest publisher we hold is @triple_stock — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 8 August 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’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 6 Nov 2026, 07:40 | 13,417 | -4 |
| 5 Nov 2026, 09:11 | 13,421 | +11 |
| 4 Nov 2026, 05:31 | 13,410 | +10 |
| 3 Nov 2026, 02:27 | 13,400 | -8 |
| 2 Nov 2026, 04:50 | 13,408 | +10 |
| 1 Nov 2026, 01:08 | 13,398 | +2 |
| 31 Oct 2026, 00:29 | 13,396 | +30 |
| 29 Oct 2026, 01:27 | 13,366 | -4 |
| 26 Oct 2026, 23:18 | 13,370 | +9 |
| 25 Oct 2026, 20:35 | 13,361 | -3 |
| 24 Oct 2026, 22:56 | 13,364 | -9 |
| 23 Oct 2026, 20:46 | 13,373 | +18 |
| 22 Oct 2026, 17:37 | 13,355 | +44 |
| 21 Oct 2026, 10:58 | 13,311 | -1 |
| 20 Oct 2026, 10:54 | 13,312 | -11 |
| 19 Oct 2026, 12:17 | 13,323 | -1 |
| 17 Oct 2026, 17:18 | 13,324 | +1 |
| 16 Oct 2026, 19:19 | 13,323 | -1 |
| 15 Oct 2026, 22:46 | 13,324 | +1 |
| 14 Oct 2026, 20:11 | 13,323 | first reading |
245 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 55 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.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 245 (4 August 2026 – 6 November 2026) |
| Views total | 150,042 |
| Reactions total | 1,139 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 18: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 6 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.
2,471 reactions across 222 posts, in 32 distinct kinds. The most used accounts for 33.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 819 | 33.1% | |
| 👍 | 541 | 21.9% | |
| 🔥 | 212 | 8.58% | |
| 🙏 | 175 | 7.08% | |
| 😭 | 140 | 5.67% | |
| 👎 | 126 | 5.10% | |
| 👏 | 71 | 2.87% | |
| 🤣 | 60 | 2.43% | |
| 🖕 | 50 | 2.02% | |
| 😱 | 46 | 1.86% | |
| 🤮 | 40 | 1.62% | |
| 😁 | 37 | 1.50% | |
| 👌 | 31 | 1.25% | |
| 🤔 | 29 | 1.17% | |
| 😢 | 25 | 1.01% | |
| 🤯 | 8 | 0.324% | |
| 🐳 | 7 | 0.283% | |
| ⚡ | 6 | 0.243% | |
| 😐 | 6 | 0.243% | |
| ✍ | 5 | 0.202% | |
| 12 further kinds | 37 | 1.50% |
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 225 of the 245 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 2,471 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 245 most recent posts we hold, published 4 August 2026 to 6 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: 8 of 60 posts held from the last 30 days (13.3%) 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).
https://m.blog.naver.com/kimcharger/224467337002
👍2
11월 5일 필라델피아 반도체 지수(SOX)가 12.25% 급락하며 1994년 이후 역대 두 번째로 큰 일일 하락률 기록. 같은 날 변동성 지수(VIX)는 16.6에서 28.2로 상승하며 하루 만에 약 70% 급등. 필라델피아 반도체 지수의 역대 최대 하락률은 2020년 3월 16일 기록한 -15.9%이며, 이번 -12.25% 하락은 2000년 4월 14일의 -11.6%를 넘어서는 수준. VIX의 하루 상승률 70%는 1990년 이후 역대 세 번째로 큰 상승 폭. 역대 최대 상승률은 2018년 2월 5일의 116%이며, 2024년 12월 18일 기록한 74%가 두 번째. 해당 수치는 야후 파이낸스의 일일 종가 데이터를 기반으로 집계했으며, 11월 5일 수치는 미국 증시 마감 약 30분 후 확보한 잠정치 기준.
😭6❤2👎1🔥1🤮1
얼마전부터 소문으로 돌던 이야기를 일런머스크가 확인시켜주네요… 아마도 좀 더 지져분한 이야기가 나올 순 있을 거 같습니다만, 다른 한 편으론 이런 이야기가 나와야 바닥이 확인될 거 같다는 생각도 드네요!
🤮6❤4👎3😱2
https://x.com/MrMikeInvesting/status/2118364772370427985?a=MnVPfvnUyHC12lrjE7w&s=19 제2의 청산?
😱12❤8🤡2💩1
* 야간선물 장중 저점 기준 코스피 환산지수는 딱 5,000 이었네요...
😭10🔥3🤮3❤2👎2🤔2
https://youtu.be/pCYj3PXfpiU?si=y2i5J4ie9yLhI8Yg
🖕6😭5👎3❤1🔥1
* 제발, 오늘 미장부터 반등을 기원합니다!
🙏50👍8🖕7😭5😢3🔥2🕊2🤮2
* 필라델피아 반도체(SOX)는 10월 고점 대비 오늘 저점까지 -27% 하락함. * 7월에 고점대비 -29% 하락했음.
😢21😭8👎6👍5❤2🔥2🖕2🎉1
📮 [메리츠증권 반도체/디스플레이 김선우] 메리츠 김선우입니다. 메모리 산업에 급작스레 찾아온 미 정치 지형도 변화 발 AI 수요 둔화 우려에도 불구하고 끄떡없는 2027년 수급 전망을 예상합니다. 지난 20년간 커머디티 메모리 산업에 있어 수급 변곡점의 발생 원인은 '직접적인 수요둔화'보다, 그를 선행하는 '낙관적 공급 의지'였습니다. 전일 미 중간선거 결과는 그동안 마냥 장밋빛이었던 공급사들의 전망에, 처음으로 물음표가 들어오는 계기입니다. 지금 이 시각 삼성전자/SK하이닉스의 전략마케팅/GSM 조직 내에서는 긴급히 미 지역별 DC 착공 스케쥴과 CSP/프런티어모델 수요 재점검에 나서고 있을 것입니다. 무분별한 공급 계획을 재점검하고, 구속력이 강화된 계약만을 추구하는 건강한 전략 전환을 예상합니다. 지난해/올해 투자 결핍으로 인해…
❤3👎3😭2
* AI 인프라 종목들에 설정된 알고리즘 매도가 1시간 35분 정도 지속이 되었군요. 과도하게 하락한 뒤 반등을 바닥에서 강하게 반등을 시도 중입니다. * 마치 중간선거 개표 결과를 확인하면서 급락하던 아시아 증시의 모습을 보는 것 같습니다.
😭16🙏5👎3🤮3❤2👍2🖕2😁2
●애플이 민주당 스윕의 수혜주로 해석되는 두 가지 이유 1. AI CAPEX의 부담에서 상대적으로 자유롭다 애플의 이익 성장 동력이 데이터센터 건설이 아니라 아이폰 판매 구성, 가격 결정력, 서비스 매출이라는 점. AI 인프라 투자에 대한 시장의 의구심이 커질수록 애플의 사업구조가 상대적으로 매력적이라는 것. 2. 메모리 가격 상승 압력이 완화될 수 있다는 새로운 논리 - 애플은 최근 실적발표에서 메모리 원가 상승으로 12월 분기 매출총이익률에 약 140bp의 부담이 발생할 수 있다고 밝힘. - 그런데 민주당 스윕 이후 데이터센터 건설 속도가 둔화될 수 있다는 전망이 제기됨. - 그렇게 되면 DRAM·NAND 수급 압박이 완화되고, 애플의 원가 부담도 줄어들 가능성이 있다는 전망.
❤10👎4😁4🖕3🤯3🔥2
* 미장이 장초반 급락 출발하고 다 올라왔죠? 이럴 때 그동안 사고 싶었던 좋은 기업을 싸게 살 수 있어야 하겠습니다.
👍13👎5❤3🤮3🔥2
Showing the 12 most recent of 245 posts we hold for @triple_stock. 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.
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 2 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.
@triple_stock 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 43 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“테크밸리 Insight” (@triple_stock), 13,417 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/triple_stock.
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.