Telegram RegisterThe public register of Telegram

Channel

이하루의 주식하루

@harulee_1004

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

728subscribers

+0 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-1003182313428
TypeChannel
Username@harulee_1004
Description바꿀 수 없는 것은 받아들이는 평온을 바꿀 수 있는 것은 바꾸는 용기를 또한 그 차이를 구별하는 지혜를
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/harulee_1004

Growth

7287 Aug 2026, 19:37 — 728 subscribers8 Aug 2026, 02:05 — 728 subscribers7 Aug 2026, 19:378 Aug 2026, 02:05
2 measurements taken within a single day. 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 727–729 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 02:05728no change
7 Aug 2026, 19:37728first reading

Engagement

20 posts held, back to 28 July 2026the 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
74.7%
avg views ÷ 728 subscribers
Avg views / post
544
20 posts measured
Reaction rate
0.701%
reactions ÷ views · ER floor
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. It is computed over the 13 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (28 July 20267 August 2026)
Views total10,883
Reactions total56
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:05 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
169
Videos
1
Links
119

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

56 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 55.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3155.4%
😢916.1%
👍814.3%
😁35.36%
🤯23.57%
🫡23.57%
🔥11.79%

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 13 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 56reactions 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 28 July 2026 to 7 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.

Recent posts

6 Aug 2026, 11:49 UTC325 viewsread 8 August 2026
Photo

사진 보시면 딥시크는 원래 다른 서드파티 제공 업체에 비해서 거의 절반 가격에 염가로 API 사용이 가능했습니다. 오픈웨이트 API 가격을 무식하게 올린다면 굳이 왜 딥시크 자체 API를 필요가 없습니다. 그냥 다른 서드파티 기업에서 딥시크 가중치 받아서 서빙해주는거 쓰지 그래서 결국 키미처럼 상업용 라이선스 조건을 붙여서 키미 K3를 활용해 서비스를 운영하면서 직전 12개월 매출이 2,000만 달러(약 294억 원)를 초과하는 기업은 문샷 AI와 별도 라이선스 계약을 의무적으로 체결해야 한다고 명시를 하는 방식이 맞는거 같은데 이건 시간문제지 언젠간 할거 같구요. API 가격을 올리는게 정당화 되려면 기존 가격이 클라우드 서빙 가격에 훨씬 못 미치는 염가였기에 올리려고 했거나 or 클로즈드를 하고 싶어하는거라는건데.. 둘 다 뭐 나쁜

6 Aug 2026, 11:30 UTC244 viewsread 8 August 2026
Forwarded from @HANAchina

>>딥시크 가격 인상…중국 AI 모델의 ‘공짜 점심’도 끝났다 •딥시크는 8월 6일 API 서비스 가격을 큰 폭으로 인상한다고 발표 •주요 배경은 AI 에이전트 등 신규 애플리케이션 확산으로 토큰 사용량이 급증한 데다, AI 연산 비용도 지속적으로 상승하고 있기 때문 •그동안 딥시크는 ‘가격 파괴자’ 전략으로 업계 전반의 가격 인하 경쟁을 촉발했지만, 이제는 보다 지속 가능한 수익 모델을 위한 가격 정책으로 전환 •이는 중국 대형 AI 모델 업계가 ‘적자를 감수하며 사용자를 확보하는 단계’에서 ‘수익성을 검증하는 단계’로 진입하고 있음을 의미하며, 앞으로의 경쟁은 비용 통제와 모델 성능 간 균형에 더욱 집중될 것 >DeepSeek涨价,国产大模型"免费午餐"到头了! https://wallstreetcn.com/articles/377884

5 Aug 2026, 13:44 UTC182 views1 reactionsread 8 August 2026
Forwarded from @skitteam

[SK증권 반도체 한동희, 손 건] 삼성전자·SK하이닉스, 주주환원 강화 의지 표명 ▶️ 삼성전자 입장 "재무 건전성 유지와 성장 투자를 지원하면서도 지속 가능한 방식으로 주주환원 강화 방안을 검토 중" "매우 곧(very soon) 세부 내용을 공유할 것" ▶️ SK하이닉스 입장 "역대 최고 수준의 현금 창출 능력을 바탕으로 투자 및 재무 건전성을 유지하면서 주주환원을 의미 있게 확대할 수 있다고 판단" "연말까지 구체적인 주주환원 계획 준비 중" "추가 주주환원을 위한 다양한 옵션 검토 중" ▶️ URL: https://buly.kr/7QOgnnh * SK증권 리서치 IT팀 채널 : https://t.me/skitteam

👍1

5 Aug 2026, 02:55 UTC349 viewsread 8 August 2026

HBF던 CXL이던 뭐가 됐던 아키텍쳐적으로 메모리 기업에게 우위를 주는 계층이 많이 확보되면 좋죠.

5 Aug 2026, 02:53 UTC358 viewsread 8 August 2026

ALAB 컨콜 중 CXL 코멘트 "In CXL, we are seeing renewed momentum as industry is recognizing its potential to unlock performance and utilization benefits in agentic AI applications." CXL에서는 업계가 에이전틱 AI 애플리케이션에서 성능·활용도 개선 잠재력을 인식하면서 다시 모멘텀이 살아나는 것을 확인하고 있습니다. "Looking into 2027, we expect to ship both standard and custom Leo CXL memory controllers in volume across general-purpose compute and AI inferencing applications to t

4 Aug 2026, 13:49 UTC397 views7 reactionsread 8 August 2026

일단 전반적으로 사피엔이 해자가 있는건 맞죠. 메타가 LOE도 버리고, 로드러너도 버렸는데 사피엔만큼은 못?(안?)버리고 있잖아요. 이거부터가 저는 사피엔 자체의 포지션이 매력적이라고 봅니다. 근데 그거랑 별개로 지금 당장 봐야하냐..?는 시장이 스마트글라스에 공감을 해줄 유즈케이스가 필요하다고 봐요(마치 클로드 코드 같은). 애플, 구글, 삼성이 스마트글라스에 들어오면서 좀 이런 케이스들을 발굴해주지 않을까 싶습니다.(물론 지금은 뭐가 그 케이스일지 예측조차 못하지만요)

7

4 Aug 2026, 13:47 UTC385 views5 reactionsread 8 August 2026

제가 사피엔은 최근에 커버를 안했는데, 가장 큰 이유는 뭔가 좀 킬러 유즈케이스가 나오는 기점에서 베팅해보는게 좋을거 같아요

👍3🫡2

4 Aug 2026, 13:46 UTC229 views4 reactionsread 8 August 2026
Forwarded from @darthacking

2026.08.04 14:25:08 기업명: 사피엔반도체(시가총액: 2,113억) A452430 보고서명: 단일판매ㆍ공급계약체결 계약상대 : 북미 Big Tech 기업 계약내용 : 디스플레이구동칩 공동개발 및 공급 계약 공급지역 : 미주지역 계약금액 : 72억 계약시작 : 2026-07-21 계약종료 : 2027-10-28 계약기간 : 1년 3개월 매출대비 : 42% 공시링크: https://dart.fss.or.kr/dsaf001/main.do?rcpNo=20260804900308 최근계약 : https://www.awakeplus.co.kr/board/contract/452430 회사정보: https://finance.naver.com/item/main.nhn?code=452430

👍31

4 Aug 2026, 02:29 UTC523 views6 reactionsread 8 August 2026

제네락이라고 미국에서 지엔씨랑 똑같은 산업을 훨씬 크게 하는 회사(발전기 커스텀만 1년에 6조)가 있는데 여기 인터뷰 같은거 보면 계속 애프터 서비스 병목에 대한 얘기가 있거든요 📌 GNRC 전문가 콜 — "진짜 병목은 발전기가 아니라 사람" ■ 핵심: DC용 대형 genset 시장 진입의 관건은 하드웨어가 아니라 서비스 인력임 └ 애널리스트 질문(2MW급 신제품·중국 파트너십·하반기 출시)에 전문가는 "그건 일부일 뿐"이라며 논점 전환 └ "발전기를 손에 넣을 수 있느냐가 관건이 아니라, 기술자를 구하는 것이 핵심" ■ 파워젠 기술자 = 디젤 정비 + 전기 기술의 합성 직무 → 자연 공급이 안 됨 └ 엔진·연료·냉각 + 스위치기어·계통 동기화·보호협조를 동시에 다뤄야 함 저는 지엔씨가 결국 여기서 과연 nGW의 애프터 서비스가 가능한

6

4 Aug 2026, 02:26 UTC≈2,540 views5 reactionsread 8 August 2026

개인적인 뷰로는 AIDC 띰에서 phase 1까지는 지엔씨가 제일 강하고 phase2부터는 skt, 네이버가 제일 강할거라고 봅니다. phase 전환 시점은 sk가 테넌트 구해오는 시점일거구요

5

Showing the 12 most recent of 20 posts we hold for @harulee_1004. 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.

Citation-graph rank

Citation-graph rank — 900,300 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“이하루의 주식하루” (@harulee_1004), 728 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/harulee_1004.

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.