한번만 살려주시면 절때 오만해지지 않겠습니다 다시는 몰빵 안 할게요
❤12🖕4🙏4💯3

Channel
@ilhyunNotesonLife
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
583subscribers
+8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004366121297 |
|---|---|
| Type | Channel |
| Username | @ilhyunNotesonLife |
| Created | Between 1 June 2026 and 18 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/ilhyunNotesonLife |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:27 | 583 | +9 |
| 6 Aug 2026, 18:03 | 574 | no change |
| 6 Aug 2026, 07:11 | 574 | -1 |
| 6 Aug 2026, 02:22 | 575 | first reading |
12 posts held, back to 18 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.
| Window | Rolling 30 days · latest post in window 31 July 2026 |
|---|---|
| Posts held | 12 (18 July 2026 – 31 July 2026) |
| Views total | 12,445 |
| Reactions total | 114 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 18:03 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.
114 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 57 | 50.0% | |
| 🖕 | 36 | 31.6% | |
| 👍 | 8 | 7.02% | |
| 🙏 | 4 | 3.51% | |
| 💯 | 3 | 2.63% | |
| 👏 | 2 | 1.75% | |
| 😁 | 2 | 1.75% | |
| 🤬 | 2 | 1.75% |
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 12 of the 12 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 114reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 18 July 2026 to 31 July 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.
한번만 살려주시면 절때 오만해지지 않겠습니다 다시는 몰빵 안 할게요
❤12🖕4🙏4💯3
왜냐면 이 시장을 경험할수록 특정 종목이나 특정 자산군들에 대한 믿음이 얼마나 무참히 박살나는지 보게 된다. 반대로 특정 종목이나 자산군을 믿고 큰 부를 얻게 된 사람도 있다. 그런데 이런 구조가 오래 가냐는 말이다. 다들 내가 하이퍼리퀴드를 알아보고 초기부터 참여해서 안목이 있다는 느낌으로 알고 있는데 전혀 사실이 아니다. 첨부터 하이퍼리퀴드가 잘 될지 안 될지 어떻게 아노 그냥 나는 5년간 계속 반복하다가 어쩌다 하나 터진게 하이퍼리퀴드 였을뿐. 물론 하이퍼리퀴드에 좀 더 공을 들인건 사실이다. 하지만 그것은 비중의 문제 였을뿐. 나는 그때도 다른 프로젝트를 여전히 하고 있었다. 무너지지 않는 구조를 만들자. 나에겐 하나에만 몰두 하는게 아닌 여러 프로젝트에 씨를 뿌려두는게 무너지지 않는 형태였다. 그리고 더 나아가 현금 주식…
❤16🖕4
오늘 배운 점 나대지말자
👏2❤1
오늘은 별 일 없기를 바랍니다. 요즘 같은 때에는 다시 고전으로 돌아가는 ... 카지노에 들어갈 것인지 교회에 들어갈 것인지는 본인의 결정이지 않을까 싶습니다.
🖕2
하락은 내 예상을 가볍게 넘어선다. 분할 매수와 10% 마다 매수같은 원칙적 투자가 필요하다
🖕12❤3
Sticker, posted without a caption
🖕2
먹은거 다 뱉었다
🖕2😁2
아 씨발 왜 옴
❤5🖕2🤬2
오늘 아니면 살 수 없다. 라는 생각 집어 치우기
❤14🖕2
160만원 오면 추매 해야겠다
👍8🖕2❤1
가격만 바뀌었을뿐 반도체와 기업의 본질은 달라지지 않았다. 나는 흔들리지 않는다.
❤5🖕2
이거 생각만 해봤는데, 실제로 하는 미친놈이 진짜 있네
🖕2
Showing the 12 most recent of 12 posts we hold for @ilhyunNotesonLife. 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 — 411,079 of 1,160,990entries 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“조일현 생각 기록” (@ilhyunNotesonLife), 583 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ilhyunNotesonLife.
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.