좋은 관점이네여

Channel
트레이딩 관점 공유하는 방
@crypto_nasdaq_trading
On this record: Growth · Engagement · Posts · Citations · Cite this entry
78subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002813851297 |
|---|---|
| Type | Channel |
| Username | @crypto_nasdaq_trading |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/crypto_nasdaq_trading |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 15:43 | 78 | -1 |
| 9 Aug 2026, 19:30 | 79 | no change |
| 7 Aug 2026, 11:28 | 79 | first reading |
Engagement
20 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 10.1%
- avg views ÷ 78 subscribers
- Avg views / post
- 7.9
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 20 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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (6 August 2026 – 8 August 2026) |
| Views total | 158 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 19:30 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
근거는 예전에 올렸던거 재탕입니다 2. AI 수요 지속가능성 7월 어닝콜에서 드러났듯 메타·구글·마이크로소프트·아마존이 모두 CAPEX를 늘리기로 하며, AI 수요 트렌드는 우상향하고 AI 경쟁은 계속된다는 확신이 시장에 자리 잡았습니다. 그런데 이런 확신에도 불구하고 초반 CAPEX 증가 소식에 코스피는 반도체주와 함께 힘을 쓰지 못했는데요. 제 생각에는 시장이 이미 'CAPEX 증가'를 확신하고 이를 선반영해 두었기 때문입니다. 즉 "계속 쓸 거냐"는 질문은 이미 답이 나왔고, 시장은 더 이상 같은 질문을 하지 않습니다. 이제 던지는 질문은 다릅니다. "그래서 쓴 게 돈이 되냐?" 그 답은 7월 29일 시장이 어디에 반응했는지에 있다고 봅니다. 마소는 애저 성장률이 40%에서 43%로 오르며 클라우드로 투자 부담을 흡수했고, 아시다시피…
마이크론 샌디 있으니께 ㅇㅇ
그냥 닉 sell 전자 buy 하든지 그게 아니면 미장만 매매하는게 나을듯
이런거 볼때 코리아 디스카운트는 유효함
다음주 일정 (8일): 버크셔 실적 10일: TSMC 7월 매출, 로켓랩, ASTS, PLG, QUBT, HIMS, USAR 실적(장후) 11일: 한국 1~10일 수출입, 미국 7월 기존주택판매, 일본 휴장, SE, ONON 실적(장전), 코어위브, 슈퍼마이크로, 루멘텀 실적(장후) 12일: 미국 CPI, 네비우스 실적(장전), CSCO, COHR, CBRS 실적(장후) 13일: 미국 PPI, 샌디스크 Investor Day, TPR 실적(장전), AMAT, FIGR 실적(장후) 14일: 미국 7월 소매판매, 8월 소비자심리지수, 기대인플레이션, 유로존 2분기 GDP
물타서 207까지 내렸다. 단가까지 올리거라 미장아
ㄷㄷ 힝 속았지?의 속았지 패턴
https://www.inews24.com/view/1993001 아니라곤 하는데..
흠..
-SK하이닉스, 청주 M17 공장에 19조 1천억 원 투자 예정 -SK하이닉스, 용인 FAB 2에 35조 2천억 원 투자 예정 -SK하이닉스, 한국 내 메모리 반도체 확장 등에 54조 원 투자 예정
⚡️⚡️⚡️ SK하이닉스, 주당 375원 분기 배당확정
Showing the 12 most recent of 20 posts we hold for @crypto_nasdaq_trading. 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
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“트레이딩 관점 공유하는 방” (@crypto_nasdaq_trading), 78 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/crypto_nasdaq_trading.
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.