https://m.blog.naver.com/crush212121/224358911321

Channel
적절한 지식과 검증된 판단, 체리형부
@Valuefs1
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
8,619subscribers
-48 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001742145268 |
|---|---|
| Type | Channel |
| Username | @Valuefs1 |
| Description | Valuefs.com 본 채널의 게시물은 단순 의견 및 기록용도이고 매수-매도 등 투자권유를 의미하지 않습니다. 해당 게시물의 내용은 부정확할 수 있으며 매매에 따른 손실은 거래 당사자의 책임입니다. 해당 게시물의 내용은 어떤 경우에도 법적 근거로 사용될 수 없습니다. |
| Created | 20 January 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/Valuefs1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 01:53 | 8,619 | -11 |
| 22 Aug 2026, 23:22 | 8,630 | -9 |
| 19 Aug 2026, 16:22 | 8,639 | -4 |
| 16 Aug 2026, 21:15 | 8,643 | -8 |
| 13 Aug 2026, 17:38 | 8,651 | -17 |
| 10 Aug 2026, 13:55 | 8,668 | -1 |
| 7 Aug 2026, 10:37 | 8,669 | +2 |
| 7 Aug 2026, 05:30 | 8,667 | no change |
| 7 Aug 2026, 05:24 | 8,667 | first reading |
Engagement
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 26 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈3,340
- Videos
- ≈3
- Links
- ≈4,500
Lifetime counters from Telegram’s own channel header, read 27 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
체리형부 반도체 사이클 시리즈 (총 54편) 시리즈는 총 100편을 목표로 쭉 지속됩니다 기업별 종합DB(엑셀)는 비공개 텔레그램 채널에 공유 중입니다 ━━━━━━━━━━━━━━ 핵심 종목 엔비디아 (수요 진앙) https://m.blog.naver.com/crush212121/224339901601 마이크론 (제조사 진앙) https://m.blog.naver.com/crush212121/224339849786 SK하이닉스 (선단층, 대장의 관점) https://m.blog.naver.com/crush212121/224345703277 TSMC (Q시계의 원점, 제분소의 관점) https://m.blog.naver.com/crush212121/224349958366 ASML (겨울이 없었던 회사) https://m.blog.n…
■ [체리형부] ETF High Beta 시리즈 같은 급락장을 정반대로 받는 두 회사 1편 에프앤가이드 레버리지 ETF의 High Beta https://m.blog.naver.com/crush212121/224358336103 2편 고려신용정보 인버스 ETF의 High Beta https://m.blog.naver.com/crush212121/224358347098 ━━━━━━━━━━━━━━ ■ 시리즈의 질문 7월 급락장에서 어떤 회사는 매출 기반이 3주 만에 45% 깎였고 어떤 회사는 하루 +21% 신고가를 찍었다 방향이 아니라 증폭이 갈랐다 이 시리즈는 그 증폭의 구조를 공시로 확인한 기록 ━━━━━━━━━━━━━━ ■ 1편 에프앤가이드 53% 2분기 영업이익률, 사상 최대 분기 78조 6월말 지수 추종 ETF 잔액…
https://m.blog.naver.com/crush212121/224358347098
https://m.blog.naver.com/crush212121/224358336103
■엔비디아 공식 파트너사 분석 시리즈 (1~3편 완결) https://www.news1.kr/politics/president/6238838 1편 아이크래프트 5주 만에 1년치 일감을 받은 회사 https://m.blog.naver.com/crush212121/224358068107 2편 에스넷시스템 잔고를 보지 말고 재고를 보라 https://m.blog.naver.com/crush212121/224358122871 3편 MDS테크 소문은 AI 서버, 실체는 기계 속 작은 두뇌 https://m.blog.naver.com/crush212121/224358140301 ━━━━━━━━━━━━━━ ■ 왜 지금 이 3개사인가 이유 하나. 돈이 지금 움직이고 있습니다 2조 805억 정부가 올해 GPU 9,704장을 사들이는 사업 규모 …
https://m.blog.naver.com/crush212121/224358140301
https://m.blog.naver.com/crush212121/224358122871
https://m.blog.naver.com/crush212121/224358068107
https://m.blog.naver.com/crush212121/224357426645
https://m.blog.naver.com/crush212121/224357416271
https://m.blog.naver.com/crush212121/224357196051
Showing the 12 most recent of 20 posts we hold for @Valuefs1. 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 — 1,131,403 of 1,622,561entries 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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“적절한 지식과 검증된 판단, 체리형부” (@Valuefs1), 8,619 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/Valuefs1.
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.