Channel
@migukstocksailor
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
374subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002178300819 |
|---|---|
| Type | Channel |
| Username | @migukstocksailor |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/migukstocksailor |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:23 | 374 | -1 |
| 8 Aug 2026, 06:18 | 375 | no change |
| 7 Aug 2026, 18:01 | 375 | first reading |
20 posts held, back to 21 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 1 pageof 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 5 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 20 (21 July 2026 – 4 August 2026) |
| Views total | 1,870 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:18 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.
6 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 66.7% | |
| 💩 | 1 | 16.7% | |
| 🔥 | 1 | 16.7% |
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 5 of the 20 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 July 2026 to 4 August 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.
Classic Jevons paradox in action — token costs collapse thanks to Chinese models, but total compute demand and expenditure will just keep rising. The real winners are the ones who can deliver frontier performance at near-commodity prices. https://x.com/halvinebukachi/status/2084752788416803141?s=46 똑똑한 맨유팬..
모델별 api 가격 사이트 https://api.chat/models/
❤2
Asia's leverage boom is rapidly reversing: Margin debt in South Korea has declined -$4 billion from its June peak, to $22 billion, the lowest since mid-April. At the same time, stock margin loans in China have dropped -$59 billion, to $385 billion, the lowest since the 2nd week of April. Similarly, in Taiwan, margin debt has fallen -$4 billion from its July peak, to $15 billion, the lowest since mid-May. Combined…
🇺🇸🇯🇵 자, 이제 작동 방식이 이거예요. 연준이 금리를 유지하고 일본은행이 국내 부채 위기를 촉발하지 않고 금리를 인상할 수 없을 때, 미국 재무부가 일본의 통화 정책을 인수하게 되는 거죠. 미국 정부가 엔화 시장에 직접 개입하는 건 제 생각엔 전형적인 "양자 협력"이 아니에요. BOJ의 망가진 외환 프레임워크에 대한 사실상의 구제 금융이에요. 일본 중앙은행은 폭주하는 수입 인플레이션과 감당할 수 없는 국채 부채 사이에 스스로를 가두었어요. 일본이 통화를 방어하기 위해 장기 미국 국채를 대량 매도하는 걸 막기 위해, 우리 30년 만기 수익률을 5.24%로 치솟게 하는 걸 막기 위해, 이번 주 내내 그랬던 상황이죠. 미국 재무부가 그들을 위해 환율을 관리하기 위해 개입하는 거예요. 이건 완전히 미친 짓이에요! 우리를 여기 붙잡고 있는 게…
💩1
https://youtu.be/gf0cPrinP9w?si=7_04wmMh5gUPtHo1
📌 L3해리스, 미사일 사업부 IPO 2027년으로 연기 • 당초 2026년 말 상장 → 2027년 중반 이후로 연기 • 이유 : 현재 IPO 시장이 기업가치를 제대로 인정하지 못함 - 국방예산 불확실성 - 미국 중간선거 - 금융시장 변동성 • 하지만 사업은 오히려 호황 - 미국 2대 대형 고체로켓모터 업체(L3해리스·노스럽그러먼) PAC-3·THAAD용 고체로켓모터 7년 공급계약 체결 - 200억 달러 이상 신규 계약 협상 중 성사 시 수주잔고 3배 확대 전망 - 상반기 매출 17억 → 20억 달러 증가 CEO 코멘트 "사업은 매우 좋지만 시장이 가치를 인정하지 못하고 있다." https://breakingdefense.com/2026/07/l3harris-postpones-missile-unit-ipo-until-mid-2027/
❤1
MTD -67 YTD 80 ... ㅋㅋㅋㅋㅋ
레오폴드 아셴브레너의 투자자 서한 파트너 여러분께, 이번 달 저희는 여러분의 기대에 미치지 못했습니다. 저희는 결코 발생해서는 안 될 수준의 영구적인 자본 손실 위험에 매우 가까이 다가갔습니다. 결과적으로는 투자자 여러분과 펀드를 보호할 수 있는 해결책을 마련했지만, 저희가 펀드를 운용하는 원칙은 애초에 그런 상황 자체를 만들지 않는 것입니다. 변동성은 장기 투자 수익을 얻기 위해 치러야 하는 대가입니다. 지난 2년 동안 저희는 간헐적인 큰 조정을 겪으면서도 뛰어난 성과를 거두었습니다. 하지만 펀드는 언제나 큰 손실을 감내한 뒤에도 다시 일어설 수 있는 구조여야 합니다. 이번 일을 통해 반드시 필요한 교훈을 얻고, 이를 조직에 반영하는 것을 제 가장 중요한 과제로 삼겠습니다. 현재 상황을 말씀드리겠습니다. 7월 한 달 동안 포트폴리오는 큰…
2026.07.29 07:43:54 기업명: SK하이닉스(시가총액: 1,104조 6,887억) A000660 보고서명: 연결재무제표기준영업(잠정)실적(공정공시) 매출액 : 793,187억(예상치 : 835,194억/ -5%) 영업익 : 605,426억(예상치 : 636,668억/ -5%) 순이익 : 938,202억(예상치 : 513,232억+/ 83%) **최근 실적 추이** 2026.2Q 793,187억/ 605,426억/ 938,202억 2026.1Q 525,763억/ 376,103억/ 403,459억 2025.4Q 328,267억/ 191,696억/ 152,460억 2025.3Q 244,489억/ 113,834억/ 125,975억 2025.2Q 222,320억/ 92,129억/ 69,962억 공시링크: https://dart.fss…
https://x.com/gavinsbaker/status/2082166566280642676?s=46&t=xqAS5Xg0kII_7JxezPKEHw https://t.me/kkkontemp/2542
#BE 통상적으로 4q는 계절성이 있는 분기였기 때문에 Product 매출 4q25 = 1q26 플랫 그러나 2q26 다시 qoq 50% 증가 정상적 램프업 중 ->숏리포트 등에 대한 반박 가능
❤1
특이사항은 제품 매출은 컨센 ~40% 상회 , 서비스+설치+전력 판매는 컨센 미스 Gpt 답변 요약하면 장비(연료전지)매출 컨센 40%가 핵심 + 나머지는 매출 인식 방식 차이 + 전력 소유 모델 차이 등으로 인해 앞으로도 분기별 변동성이 심할 수 있음 1. 이번 실적의 핵심은 제품 매출 급증이 전체 실적 서프라이즈를 만들었다는 점임. 2. 제품 매출은 컨센서스를 약 40% 상회했지만 설치·서비스·전력판매는 모두 예상치를 하회함. 이는 제품·설치·서비스 매출이 같은 시점에 함께 인식되는 구조가 아니기 때문임. 3. 블룸은 장비 인도 시 제품 매출을 크게 인식하지만, 설치 매출은 공사 진행에 따라 후행할 수 있음. 특히 대형 데이터센터에서는 설치를 고객이나 외부 EPC가 맡아 블룸의 설치 매출이 적을 수 있음. 4. 서비스 매출은 장비…
Showing the 12 most recent of 20 posts we hold for @migukstocksailor. 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“뉴욕 찍먹 투자” (@migukstocksailor), 374 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/migukstocksailor.
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.