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 13 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 1 other registered channel. This entry also sits inside a group of 4 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.
Matching posts — open both and compare (1 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. 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 56 comparable posts for this entry, running 31 July 2026 to 4 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 4 channels, the one whose matching posts we hold earliest is @shsmallcap. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key 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.
Channels linked by matching posts
This channel is in a group of 4 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.
27 measurements spanning 96 days, net +603. 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 5,253–6,036 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
10 Nov 2026, 00:19
5,946
+13
6 Nov 2026, 23:49
5,933
+11
3 Nov 2026, 23:48
5,922
+11
31 Oct 2026, 16:17
5,911
+19
28 Oct 2026, 16:00
5,892
+12
25 Oct 2026, 17:07
5,880
+12
22 Oct 2026, 17:56
5,868
+20
19 Oct 2026, 05:08
5,848
+7
15 Oct 2026, 22:50
5,841
+13
12 Oct 2026, 12:18
5,828
+11
5 Oct 2026, 17:17
5,817
+27
28 Sept 2026, 14:20
5,790
+75
19 Sept 2026, 04:42
5,715
+86
14 Sept 2026, 17:19
5,629
+67
11 Sept 2026, 13:19
5,562
+35
6 Sept 2026, 23:40
5,527
+7
2 Sept 2026, 18:42
5,520
+31
31 Aug 2026, 03:45
5,489
+2
28 Aug 2026, 13:24
5,487
+6
25 Aug 2026, 22:29
5,481
first reading
Engagement
60 posts held, back to 31 July 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 10 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
26.2%
avg views ÷ 5,946 subscribers
Avg views / post
1,560
24 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
24
of 60 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
60 (31 July 2026 – 4 November 2026)
Views total
37,409
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
5 Nov 2026, 01:37 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.
Recent posts
Telegram’s own ‘edited’ marker: 1 of 24 posts held from the last 30 days (4.17%) 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).
★ Daily Market Digest - 2026년 11월 5일 시황 강진혁 ☎️02-3772-2329 ▶ Daily Review Summary
- 미국 시장은 중간선거 불확실성 해소에 강세 불구 DC 지연 우려에 반도체는 부진. S&P500 +1.6%, NASDAQ +1.4%, Dow +3.0%
- 민주당의 상하원 장악 속 하원의장 후보의 이란전 종전 필요 언급. WTI 90$ 하회
- 민주당의 전통적 공화당 우세+DC 개수 상위 지역 Texas 승리 등에 DC 지연 우려
- 빅테크, 불확실성 해소+과잉투자 완화 통한 현금흐름 개선 기대(AMZN +6.2%)
- 반도체(SOX -3.1%)와 네오클라우드(CRWV -9.9%) 등 AI주는 낙폭 확대
- Blue Wave 트레이드에 태양광(FSLR +4.6%)↑ vs 방산(LMT -6.9%…
『[국내주식전략] 5문 5답으로 살펴보는 Blue Wave』
시황 강진혁 ☎️02-3772-2329
- Q1. 중간선거 이후 주식시장과 장기 금리의 경로는?
- Q2. 의회 구도는 미국 정책에 어떤 영향을 미치나?
- Q3. ‘행정부 공화+의회 민주’ 구도에 따른 셧다운 발생 가능성은?
- Q4. 데이터센터 인허가는 실제로 어떤 영향을 미칠까?
- Q5. 장단기 업종·종목 전략은 어떻게 가져가야 하나?
※ 원문 확인: http://bbs2.shinhansec.com/board/message/file.pdf.do?attachmentId=354765
위 내용은 2026년 11월 5일 07시 51분 현재 조사분석자료 공표 승인이 이뤄진 내용입니다. 제공해 드린 조사분석자료는 당사 고객에 한하여 배포되는 자료로 어떠한 경우에도 당사의 허락 없이,…
『ETF 미식기행; 방어주 로테이션 국면 진단』
글로벌 퀀트 박우열 ☎ 02-3772-2324
- 이달의 Kick: 방어 업종 ETF 로테이션
- Hot Pick: 국면 진단 및 선호 팩터 ETF
- Side Dish: 국내외 ETF 자금 흐름
※ 원문 확인: http://bbs2.shinhansec.com/board/message/file.pdf.do?attachmentId=354764
위 내용은 2026년 11월 5일 07시 46분 현재 조사분석자료 공표 승인이 이뤄진 내용입니다.
제공해 드린 조사분석자료는 당사 고객에 한하여 배포되는 자료로 어떠한 경우에도 당사의 허락 없이 복사, 대여, 재배포 될 수 없습니다.
국내 주식 마감 시황 - 11월 4일
『Blue Wave 순환매, 변동성 속 상승 사수』
시황 강진혁 ☎️02-3772-2329
코스피 5,683.80 (+0.62%), 코스닥 714.95 (+1.50%)
중간선거 개표 진행 가운데 증시 변동성 확대
금일 KOSPI, KOSDAQ은 각각 0.6%, 1.5% 상승했습니다. 간밤 미국은 반도체 전반 반발 매수세 유입(SOX +2.6%)되면서 반등했고 장 마감 후 발표된 실적도 긍정적이었습니다. AMD(시외 +5.0%)는 데이터센터 매출(+97% YoY) 급증에 호실적 기록했고 매출 가이던스(170억$)도 기대치 상회했습니다. SMCI(시외 +7.2%) 역시 견조한 실적과 함께 FY27 매출 가이던스 상향했습니다(중간값 685→770억$). 이에 KOSPI 장초 3%대 상승했지만 중간선거 개…
『[국내주식전략] KRICS: 산업분류 변화에서 지수·ETF 영향까지』
투자전략부 김기백 ☎️02-3772-2649
- KRICS 도입: 국내 산업구조를 반영한 분류체계 개편
- KRICS의 주요 변화: 모빌리티 신설과 섹터 통합
- KRICS 산업 분류를 적용한 대표지수 편출입 예상
※ 원문 확인: http://bbs2.shinhansec.com/board/message/file.pdf.do?attachmentId=354739
위 내용은 2026년 11월 4일 09시 24분 현재 조사분석자료 공표 승인이 이뤄진 내용입니다. 제공해 드린 조사분석자료는 당사 고객에 한하여 배포되는 자료로 어떠한 경우에도 당사의 허락 없이, 복사, 대여, 재배포 될 수 없습니다.
『퀀트분석; 3분기 실적 중간점검: 엇갈린 이익』
퀀트 이정빈 ☎ 02-3772-2919
- 2026년 3분기 실적 개선은 반도체 대형주가 주도
- KOSPI 영업외손익 악화가 영업이익과 순이익 괴리를 확대
- 향후 실적 평가는 영업이익 성장과 순이익의 질을 구분할 필요
※ 원문 확인: http://bbs2.shinhansec.com/board/message/file.pdf.do?attachmentId=354731
위 내용은 2026년 11월 4일 07시 50분 현재 조사분석자료 공표 승인이 이뤄진 내용입니다.
제공해 드린 조사분석자료는 당사 고객에 한하여 배포되는 자료로 어떠한 경우에도 당사의 허락 없이 복사, 대여, 재배포 될 수 없습니다.
국내 주식 마감 시황 - 11월 3일
『미국 중간선거 D-day』
시황 강진혁 ☎️02-3772-2329
코스피 5,648.79 (-3.59%), 코스닥 704.39 (-4.08%)
AI 노이즈에 재차 5,600p선 접근
KOSPI, KOSDAQ 각각 3.6%, 4.1% 하락했습니다. 유가 진정에도 재차 부각된 AI 노이즈에 아시아 시장 약세였습니다(일본 휴장, 대만 -3.6%). Meta(-1.3%)·Oracle(-8.8%)의 회사채 등을 통한 각 200억$ 자금 조달 추진 보도는 AI 자본 제약 우려를 자극했고 Apple(시외 -2.8%)의 기대 하회한 GPM 가이던스(45~46%)로 메모리 비용 부담도 부각됐습니다. Anthropic 수정 S-1에서는 매출 상승세(+46.7% QoQ)에도 8,954억$의 지출 약정 부담도 함께 확…
마켓레이더(11월 3일, 오전) 리서치본부 주식전략팀
『유가보다 무거운 AI 투자 부담』
시황 강진혁 ☎️02-3772-2329
KOSPI는 2.5% 하락한 5,714.4p. 유가 진정에도 AI 자본 제약 노이즈에 반도체 중심 전일 상승분 반납
KOSDAQ은 2.2% 하락한 718.4p. Micro 악재 유입에 투심 재차 위축되며 대형주 동반 매물 출회
KOSPI는 2.5% 하락한 5,714.4p. 유가 진정에도 AI 자본 제약 노이즈에 반도체 중심 전일 상승분 반납
:美-이란 협상 진전+이란 최고지도자→대통령 대화 권한 위임 소식 등에 WTI 7%대 하락하며 100$ 하회
:META(-1.3%)·ORCL(-8.8%)의 회사채 등 통한 각 200억$ 조달 추진 보도는 AI 자본 제약 우려 자극
:AAPL(시외 -2.8%), 신제품 호조…
Showing the 12 most recent of 60 posts we hold for @shStrategy. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“[신한 리서치본부] 주식전략/시황/퀀트” (@shStrategy), 5,946 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/shStrategy.
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.
![Telegram profile photo for [신한 리서치본부] 주식전략/시황/퀀트](https://cdn.tgregister.com/av/ce/ce6d4690f6f4a9690cd49411fcf81a661d2c203ecdcf47025bbef96cbb9f79e2.jpg)