https://naver.me/xONREZwC
💊4❤2🥱1

Channel
@davidstocknew
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
17,257subscribers
-232 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001242341370 |
|---|---|
| Type | Channel |
| Username | @davidstocknew |
| Description | Global Macro & Sector Data support. 행복한 데에는 가족만 한 것이 없고 즐거운 데에는 친구만 한 것이 없으며, 돈 버는 데는 주식소리통만 한 데가 없다. |
| Created | 11 February 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/davidstocknew |
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 57% 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 |
|---|---|---|---|
| @macro_OK/10196 Aug 2026, 01:12 UTC | @davidstocknew/52154 · this entry6 Aug 2026, 01:12 UTC | 1.00 | under a minute |
| @davidstocknew/52160 · this entry6 Aug 2026, 03:08 UTC | @macro_OK/10206 Aug 2026, 03:08 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @macro_OK | 5 (5/5 hand-verifiable sample passed) | 1.00 | 16 minutes | @macro_OK (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. 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 32 comparable posts for this entry, running 5 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 @macro_OK. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 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 |
|---|---|---|
| 7 Nov 2026, 03:57 | 17,257 | -4 |
| 6 Nov 2026, 06:39 | 17,261 | +12 |
| 5 Nov 2026, 06:07 | 17,249 | -2 |
| 4 Nov 2026, 08:16 | 17,251 | +1 |
| 3 Nov 2026, 05:50 | 17,250 | -2 |
| 2 Nov 2026, 07:47 | 17,252 | -3 |
| 1 Nov 2026, 06:26 | 17,255 | -5 |
| 31 Oct 2026, 04:58 | 17,260 | -5 |
| 30 Oct 2026, 08:06 | 17,265 | -5 |
| 29 Oct 2026, 06:10 | 17,270 | +5 |
| 28 Oct 2026, 06:15 | 17,265 | -3 |
| 27 Oct 2026, 02:44 | 17,268 | -7 |
| 24 Oct 2026, 22:25 | 17,275 | -13 |
| 23 Oct 2026, 18:56 | 17,288 | -7 |
| 22 Oct 2026, 16:48 | 17,295 | +3 |
| 21 Oct 2026, 11:44 | 17,292 | +18 |
| 20 Oct 2026, 06:16 | 17,274 | +18 |
| 19 Oct 2026, 03:39 | 17,256 | -7 |
| 18 Oct 2026, 02:18 | 17,263 | -2 |
| 17 Oct 2026, 03:40 | 17,265 | first reading |
698 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 65 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 106 of 135 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 698 (5 August 2026 – 7 November 2026) |
| Views total | 193,424 |
| Reactions total | 766 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 16:19 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 7 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 2 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.
2,536 reactions across 443 posts, in 39 distinct kinds. The most used accounts for 59.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,499 | 59.1% | |
| 👍 | 182 | 7.18% | |
| 🥱 | 155 | 6.11% | |
| 😭 | 84 | 3.31% | |
| 🤔 | 66 | 2.60% | |
| 👏 | 63 | 2.48% | |
| 🙏 | 52 | 2.05% | |
| 😱 | 50 | 1.97% | |
| ❤🔥 | 49 | 1.93% | |
| ✍ | 39 | 1.54% | |
| 🤣 | 36 | 1.42% | |
| 🔥 | 33 | 1.30% | |
| 😢 | 28 | 1.10% | |
| 💯 | 25 | 0.986% | |
| 🤯 | 19 | 0.749% | |
| 😁 | 18 | 0.71% | |
| 👀 | 15 | 0.591% | |
| 🍾 | 13 | 0.513% | |
| 😨 | 13 | 0.513% | |
| 🎃 | 12 | 0.473% | |
| 19 further kinds | 85 | 3.35% |
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 471 of the 698 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,574 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 698 most recent posts we hold, published 5 August 2026 to 7 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: 43 of 136 posts held from the last 30 days (31.6%) 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://naver.me/xONREZwC
💊4❤2🥱1
📊 헬스케어 (-0.06%) 섹터 ETF는 당일 -0.06%로 S&P500(+0.31%)보다 약했지만, 1주 0.0%로 시장(-2.7%)보다 선방했습니다. 상승 31·하락 30으로 폭은 대체로 균형을 이뤘습니다. VIX 25.6과 하이일드 OAS 3.48%(+16bp) 등 위험회피 신호 속에서 섹터 공통 재료는 약했고 CRL·PODD·CNC 등 개별 이슈가 컸습니다. 지켜볼 점은 HUM·CNC의 의료비 흐름과 SOLV의 ERP 주문 반전 정상화 여부입니다. 1. 투자클럽 31개 종목 점검 Cramer와 Jeff Marks가 투자클럽 보유 31개 종목을 점검했고, 기사에서 FedEx와 Kimberly-Clark를 매수 후보로 언급했습니다. 존슨앤드존슨과 일라이 릴리는 추가 하락을 기다리라는 의견이 나왔습니다. 💡 대형 제약주에 대한 투자클럽…
👍1
☀️ 미장 마감 브리핑 · 11/6(금) 종가 🔴 DEFCON 1단계 · 위기 · 종합 69.5점 (2026-11-07 06:47 갱신) ▲ 상승 섹터 정보기술 +1.9% · 커뮤니케이션서비스 +1.8% · 경기소비재 +0.4% ▼ 하락 섹터 필수소비재 -1.3% · 부동산 -0.7% · 금융 -0.6% 🧭 S&P500은 +0.31%(7,376.9)로 마감했지만 VIX 25.6(-2.54)과 하이일드 OAS 3.48%(+16bp) 속에 5일 상승 종목 비율은 43%로 상승 폭은 좁았다. 정보기술(+1.45%)만 뚜렷이 오른 반면 필수소비재(-1.28%)·소재(-0.73%)·부동산(-0.68%)은 밀려 섹터 간 흐름이 엇갈렸다. 섹터 공통 재료는 약했고, 10년물 4.86%와 스프레드 흐름 속에서 정보기술의 데이터센터 가이던스와 유틸리티의…
👍1🥱1
📊 경제지표 속보 11.07 05:30 ⭐⭐ 🇺🇸 CFTC 원유 투기적 순포지션 (CFTC Crude Oil speculative net positions) 실제 80.3K (이전 74.3K) ⭐⭐ 🇺🇸 CFTC 금 투기적 순포지션 (CFTC Gold speculative net positions) 실제 179.5K (이전 186.5K) ⭐⭐ 🇺🇸 CFTC 나스닥100 투기적 순포지션 (CFTC Nasdaq 100 speculative net positions) 실제 42.9K (이전 48.8K) ⭐⭐ 🇺🇸 CFTC S&P500 투기적 순포지션 (CFTC S&P 500 speculative net positions) 실제 -129.4K (이전 -134.4K) 📌 Bilanx Research 📎 주식소리통 NEO
📊 경제지표 속보 11.07 05:00 ⭐⭐ 🇺🇸 소비자신용 (Consumer Credit (Sep)) 실제 27.84B 예상 13.40B 🔺 예상 상회 (+107.8%) (이전 8.19B) 📌 Bilanx Research 📎 주식소리통 NEO
📊 경제지표 속보 11.07 03:00 ⭐⭐ 🇺🇸 베이커휴즈 전체 시추기 수 (U.S. Baker Hughes Total Rig Count) 실제 604 (이전 603) 📌 Bilanx Research 📎 주식소리통 NEO
📊 경제지표 속보 11.07 03:00 ⭐⭐ 🇺🇸 베이커휴즈 원유 시추기 수 (U.S. Baker Hughes Oil Rig Count) 실제 463 (이전 462) 📌 Bilanx Research 📎 주식소리통 NEO
📊 경제지표 속보 11.07 00:00 ⭐⭐ 🇺🇸 미시간대 1년 기대인플레이션 (Michigan 1-Year Inflation Expectations (Nov)) 실제 4.3% (이전 4.7%) ⭐⭐ 🇺🇸 미시간대 5년 기대인플레이션 (Michigan 5-Year Inflation Expectations (Nov)) 실제 3.4% (이전 3.5%) ⭐⭐ 🇺🇸 미시간대 소비자기대지수 (Michigan Consumer Expectations (Nov)) 실제 50.9 예상 49.5 🔺 예상 상회 (+2.8%) (이전 48.8) ⭐⭐ 🇺🇸 미시간대 소비자심리지수 (Michigan Consumer Sentiment (Nov)) 실제 51.0 예상 48.1 🔺 예상 상회 (+6.0%) (이전 48.0) 📌 Bilanx …
❤1
📊 경제지표 속보 11.06 22:30 ⭐⭐⭐ 🇺🇸 시간당 평균임금 (전월비) (Average Hourly Earnings (MoM) (Oct)) 실제 0.4% 예상 0.3% 🔺 예상 상회 (+0.1%p) (이전 0.3%) ⭐⭐⭐ 🇺🇸 비농업고용지수 (Nonfarm Payrolls (Oct)) 실제 165K 예상 65K 🔺 예상 상회 (+153.8%) (이전 60K) ⭐⭐⭐ 🇺🇸 실업률 (Unemployment Rate (Oct)) 실제 4.1% 예상 4.2% 🔽 예상 하회 (-0.1%p) (이전 4.2%) ⭐⭐ 🇺🇸 시간당 평균임금 (전년비) (Average Hourly Earnings (YoY) (YoY) (Oct)) 실제 3.1% 예상 2.9% 🔺 예상 상회 (+0.2%p) (이전 3.2%) ⭐⭐ …
오늘 시장 많이 힘드셨죠..? 이번주 일요일에는 저녁 7시 <매크로 데프콘 라이브>가 진행될 예정이고, 다음주 화요일 오후 1시 <투마토> 라이브를 진행해보려고 합니다. 전업투자자 김승민 위원님과 김성훈 이사님 두 분을 같이 모시고 시청자 분들이 남겨주신 질문들을 드려볼 예정입니다. 여기 게시글에 승민위원님과 성훈이사님에게 시장에 대해서 물어보고 싶은 것들을 남겨주세요. 사실 질문이 있으시기보다는 이렇게 시장이 빠진 상황에서는 막막한 마음이 더 많으실 수도 있을 거라 짐작됩니다. 그냥 여러분의 현 상황을 공유해주셔도 괜찮습니다. https://youtube.com/post/Ugkx9ZVOwOkmebb3ex12O11NZTNhyhj7vI9j?si=Q8A-TsT-xIPPGD9U
❤15🥱4🤣2✍1👨💻1
지금 시작합니다!
🥱8❤3👍2🤣1
[속보] 정부, 주식 신용융자 담보비율 의무 3개월 한시 면제 https://n.news.naver.com/mnews/article/011/0004679457 https://t.me/davidstocknew 주식소리통
🥱5😱5❤2
Showing the 12 most recent of 698 posts we hold for @davidstocknew. 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.
@davidstocknew edited 8 posts 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.
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 4 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.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“주식소리통 NEO by Bilanx Research” (@davidstocknew), 17,257 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/davidstocknew.
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.