Channel
@baekobaeko
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
8,269subscribers
-27 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001506734499 |
|---|---|
| Type | Channel |
| Username | @baekobaeko |
| Created | 10 July 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/baekobaeko |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 07:57 | 8,269 | -7 |
| 12 Aug 2026, 21:54 | 8,276 | -10 |
| 9 Aug 2026, 20:33 | 8,286 | -5 |
| 6 Aug 2026, 17:00 | 8,291 | -5 |
| 6 Aug 2026, 03:03 | 8,296 | no change |
| 6 Aug 2026, 02:03 | 8,296 | first reading |
33 posts held, back to 30 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 11 pagesof 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 27 of 33 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 33 (30 July 2026 – 12 August 2026) |
| Views total | 42,031 |
| Reactions total | 72 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 16:35 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.
60 reactions across 20 posts, in 2 distinct kinds. The most used accounts for 70.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 42 | 70.0% | |
| 👍 | 18 | 30.0% |
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 27 of the 33 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 72reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 33 most recent posts we hold, published 30 July 2026 to 12 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.
**네오클라우드 선두주자 crwv nbis 실적발표 인상깊은점만 노트 crwv> - 2020년에 만든 A100 29년까지 계약완료 (감가상각 ㅗ) - crwv cds 하락 (네오클라우드중 부채가 제일 많은 회사) - 이번 분기에 체결한 계약은 지난 계약보다 마진률이 최대 10%까지 상승함 nbis> - 2분기 신규 계약은 capex 회수기간 1년 10개월로 단축 (과거 최소 2년) - 적자폭 83퍼 감소시킴 공통 주장> - 언제든 팔 수 있다, 다만 늦게 팔수록 우리가 이득이다 => 최근 spacex 가 앤트로픽한테 비싸게 팔아넘긴걸 보고 느낀게 있는듯 / 실제로 장기계약이 아닌 단기계약 형태로 신규계약을 잡는중 네오클라우드의 상승에 훈풍이 불어오는 듯 하다
❤2
$NBIS 실적 대박 오늘 NBIS 실발이 있었고, 지금 엄청 오르고있는데 실적 잘 나오는거랑 별개로 기존 시장의 예상이 1MW당 850만달러 예상했는데 까보니 단기 계약들이 1MW당 4000만달러로 대충 4배 이상 단가로 계약이 되어버림. -> 데이터센터 사업들 완전 잘된다 -> 데이터센터 벨류체인 Long SKT가 데이터센터 목표가 5GW라고했는데 NBIS 단가 대입하면 1년 매출이 280조 SKT 지금 시가총액이 20조....
❤1
아님말고^^ https://n.news.naver.com/article/214/0001517352
❤3👍1
😃Perp-Dex Day with ReboundX 루마페이지 오픈 감사하게도 많은 이스포츠 트레이딩의 오리지널격이 된 콘텐츠를 KBW에서 더욱 크게 구성하게되었습니다! 아직 공개 안 된 파트너들부터 자리잡은 "진짜" 1티어 프로젝트들과 더욱 거대하고 파격적으로 온오프라인 혜택도 준비해보았습니다! Perpdex섹터는 RWA를 업고 더욱 커질거라고 생각 중 트레이더 라인업, 굿즈 라인업, 행사 이벤트 부스 소식은 일단 신청해두시고 확인하기! 참가 프로젝트 라인업 Variational, Lighter, Aster, Extended ??? / ??? / ??? / ??? 곧 공개 정보 일시: 2026년 9월 28일 월요일 위치: 서울 강남 · 상세 주소는 승인자에게 개별 공개 인원: 600명 (승인 전용) Event Highlights -스…
❤1
좌우지간 가감없이 남겨주시는 돈타쿠님의 생각 감사한입 https://blog.naver.com/dontakoo/224374860678
❤4
오디세이 후기 처음으로 용아맥에서 봄. 완전 재밌고 천만 넘지않을까. 3시간 완전 녹음. 보면서 어렸을때 봤던 내용 계속 생각남. 레전드 명작이다 이런건 모르겠고 그냥 재밌게 보기 되게 좋음. 다크나이트 약간 아래라고 생각.. 걍 어디가서 영화 추천해달라하면 자신있게 얘기할수있을듯... 근데 뭔가 중간 서사들이 찍먹만 하는 느낌이라(원작이 그렇지만)영화말고 드라마였다면싶은 욕심이 있음.
👍5❤3
아오....왜 오늘 공시를 쳐 해서...
❤3
환율 개박는중 이번에 느낀게 환율이라는게 심리가 참 많이 작용하고 예측이 어려운것 같습니다. 유튜브에서 극단적으로 환율 예측하는 사람들은 다 거르는게 좋은듯...
❤5
이정도면 존나 천재 맞는거같음 민주당은 약간 사람 긁는법을 아는듯
❤4👍3
하이닉스 분기배당 0.02% 주주환원 공시는 언제하니...!!
❤1
개인적인 생각으로 SK하이닉스의 나스닥 솔리다임 신규 IPO와 주주환원 공시가 없는건 이재명 당선부터 상법개정을 시작으로 이어져온 국내기업이 미국기업처럼 주주친화적으로 바뀔거라는 10%의 믿음을 0%로 만든게 아닐까... 물론 아직 주주환원 공시는 나온게 없고, 솔리다임 IPO가 크게 영향 없을거라는 말도 있지만 그냥 국장이 국장했구나라는 인식을 준 느낌 하이닉스가 미국에 adr 상장시켜놓고도 국장에서 하던짓 하는데 주주친화적으로 바뀔거라는 기대를 할수가 없는 상황 아닐까....
❤3
취소취소
❤1👍1
Showing the 12 most recent of 33 posts we hold for @baekobaeko. 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 — 295,592 of 1,481,502entries 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.
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 1 registered channel — 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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“백호의 투자갤러리” (@baekobaeko), 8,269 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/baekobaeko.
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.