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.
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 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 (2 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. 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 622 comparable posts for this entry, running 5 August 2026 to 16 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 @macro_OK. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 17 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.
64 measurements spanning 100 days, net -216. 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 17,207–17,534 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)
Subscribers
Change
14 Nov 2026, 11:54
17,273
-1
11 Nov 2026, 09:56
17,274
+20
9 Nov 2026, 14:57
17,254
+9
8 Nov 2026, 10:08
17,245
-12
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
first reading
Engagement
893 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 84 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
8.84%
avg views ÷ 17,273 subscribers
Avg views / post
1,530
330 posts measured
Reaction rate
0.425%
reactions ÷ views · ER floor
Posts in window
331
of 893 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 281 of 330 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 17 November 2026
Posts held
893 (5 August 2026 – 17 November 2026)
Views total
504,171
Reactions total
1,918
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 05:45 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
Photos
≈7,160
Videos
≈70
Links
≈47,700
Lifetime counters from Telegram’s own channel header, read 17 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.
Video runtime
49s
Average length
25s
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.
Reaction mix
3,688 reactions across 618 posts, in 45 distinct kinds. The most used accounts for 50.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1,878
50.9%
🥱
423
11.5%
👍
341
9.25%
😭
126
3.42%
🤣
101
2.74%
🤔
89
2.41%
👏
71
1.93%
😱
64
1.74%
❤🔥
59
1.60%
✍
56
1.52%
😁
55
1.49%
🙏
55
1.49%
🔥
38
1.03%
😢
34
0.922%
😨
34
0.922%
👌
30
0.813%
💯
25
0.678%
🤯
25
0.678%
😐
16
0.434%
🍾
15
0.407%
25 further kinds
153
4.15%
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 646 of the 893 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 3,726 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 893 most recent posts we hold, published 5 August 2026 to 17 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: 99 of 331 posts held from the last 30 days (29.9%) 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).
5. 크레스
임시 CEO 콜레트 크레스는 2013년부터 재무보고를 책임진 CFO입니다.
외부 신임 경영자가 이전 경영진의 문제를 정리하는 상황과는 차이가 있습니다
보수적 가이던스는 미래 전망을 신중하게 제시하는 것입니다.
빅 배스는 당기 손실·비용을 과도하게 인식해 이후 실적 회복을 더 두드러지게 만드는 이익조정입니다. 정상적인 손상차손이나 충당금과도 구분해야 합니다.
크레스가 젠슨황을 아예 무덤까지 보내버릴려고 한다면 회계 장부를 첨부터 보수적으로 다 뜯어고쳐서 나올 것입니다.
유대인을 믿어도 될까요?
4. 관전 포인트
4분기 매출 예상치는 1248.8억 달러, 전분기 대비 +14.4%입니다.
반면 조정 매출총이익률은 전분기 74%에서 71.9%로 하락할 것으로 보고 있습니다.
지금 삼전닉스의 표독?함으로 가격이 너무 많이 올랐기 때문에 이미 회사 측에선 마진이 조금 줄어들 것이라고 예고를 하긴 했습니다.
핵심은 하락 자체보다 매출 가이던스가 기대를 웃도는지, 가격 인상을 통한 2028년 마진 회복 전망이 유지되는지를 봐야 한다는 것입니다.
3. 시스템 트레이딩....
실적이 딱 나왔을때 주가가 딱 오른다고 거기서 까딱 넘어가면 위험할 수 있습니다.
대부분 시스템 트레이딩으로 주가가 오르내리거든요 실적이 나왔을 때 말이에요
공식 adjusted EPS 컨센은 2.47달러고 비공식 기대치인 위스퍼는 2.6달러입니다. 위스퍼 넘버가 공식 컨센보다 5.3% 높은 수준입니다.
그래서 공식 컨센보다 EPS가 높게 나온다고 바로 돈을 넣지 마시고 위스퍼 넘버랑 같이 보시면 좋을 것 같다는 말씀입니다.
2. 매출 구조
3분기 전체 매출은 1091.5억 달러, 그 중 데이터센터가 1018.5억 달러입니다. 약 93.3퍼센트가 데이터센터에서 나오는 구조죠.
고객층을 나누면
-> 하이퍼스케일러
-> AI 클라우드 산업 기업 고객
으로 나눌 수 있습니다.
저 고객들의 CAPEX 투자가 어땠나요? 역대급이었고 계속 늘려간다고 했었죠? 체력이 언제 떨어질지는 모르겠지만..실적은 무조건 좋을 것입니다.
지속성에 대해서 질문이 있을 것입니다.
1. 옵션시장이 반영한 내재변동성은 +- 10퍼
엔비디아가 내일 오전 6시쯤 실적을 발표하죠. 이때 엔비디아의 방향에 따라 전체 지수 방향이 결정 될 것입니다.
옵션 가격에서 추정한 특정 기간의 주가 변동폭은 약 10퍼대가 나오더라고요. 아래로 10퍼 찍히면 대곰탕 아니겠습니까?
내재변동성은 현재 옵션 가격이 성립하려면 주가가 얼마나 흔들려야 하는지를 역산한 값입니다.
따라서 이는 주가가 반드시 범위 안에 머문다는 뜻도 아니고.. 실적 발표를 포함한 기간의 불확실성이 옵션 가격에 반영돼 있다는 사실만 챙겨가면 되겠져
Showing the 12 most recent of 893 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.
Posts edited after publishing
@davidstocknew edited 9 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.
First edit seen
9 August 2026
Most recent edit
15 November 2026
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 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.
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 14 November 2026 — this
entry's latest reading, not the date you are reading this.
“주식소리통 NEO by Bilanx Research” (@davidstocknew), 17,273 subscribers as measured 14 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.