Telegram RegisterThe public register of Telegram
Telegram profile photo for 잠이보약이다

Channel

잠이보약이다

@zamboyak

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

1,125subscribers

+2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002746556938
TypeChannel
Username@zamboyak
CreatedBetween 1 June 2025 and 31 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/zamboyak

Growth

1,1231,1251,1246 August 2026 — 1,123 subscribers6 August 2026 — 1,123 subscribers13 August 2026 — 1,125 subscribers6 August 202613 August 2026
3 measurements spanning 7 days, net +2. 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 1,123–1,125 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:581,125+2
6 Aug 2026, 12:041,123no change
6 Aug 2026, 03:061,123first reading

Engagement

17 posts held, back to 16 June 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
148.4%
avg views ÷ 1,125 subscribers
Avg views / post
1,670
5 posts measured
Reaction rate
0.707%
reactions ÷ views · ER floor
Posts in window
5
of 17 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held17 (16 June 20263 August 2026)
Views total8,349
Reactions total59
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 12:04 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.

Reaction mix

196 reactions across 16 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
196100.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 16 of the 17 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 196reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 16 June 2026 to 3 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

3 Aug 2026, 23:13 UTC745 views21 reactionsread 6 August 2026
Photo

간만에 기록말고 생각을 적어봤음 https://blog.naver.com/sanoulzig/224367404943

21

1 Aug 2026, 06:30 UTC≈4,840 views20 reactionsread 6 August 2026
Photo

7월 월말기록 https://blog.naver.com/sanoulzig/224364877659

20

30 Jul 2026, 14:43 UTC871 views7 reactionsread 6 August 2026

疾如風(질여풍), 徐如林(서여림) 달릴때는 바람처럼 달리고, 머물때는 숲처럼 고요히 머물며. 侵掠如火(침략여화), 不動如山(부동여산) 적을 칠때는 불과 같이 치고, 움직이지 않을때는 산과 같이 하며.. 難知如陰(난지여음), 動如雷霆(동여내정) 숨어 있을때는 어둠처럼 보이지 않게 하고, 움직일때는 우뢰처럼 거세다.. [출처] 不動如山(부동여산) |작성자 알바트로스

7

30 Jul 2026, 14:43 UTC763 views8 reactionsread 6 August 2026

하락으로 한참 괴롭히고 난 후엔 사람들이 사더라도 소극적으로 산다고 생각해서 자리가 좋다면 비중빵 생각해볼듯. 난 아직 수익 버퍼가 있다..

8

22 Jul 2026, 14:27 UTC≈1,130 views3 reactionsread 6 August 2026
Photo

저 우세강도를 중앙으로 다시 맞추려면 구글 실발에서 메모리에게 레전드 호재가 뜨고 마이크론도 오르되 하닉이 개폭룡적 오버퍼폼 하는 미래선 뿐인건가 https://codojun.com/micron-vs-sk-hynix

3

13 Jul 2026, 07:46 UTC≈3,390 views10 reactionsread 6 August 2026
Photo

1. 내일 더 빠지기 (120 이평) 2. 한번 반등하고 다음 날 더 빠지기 (120 이평) 3. 내일부터 반등 4. AI 사이클 끝 수고 2>1>3>4 순으로 가능성 높다고 생각했음

10

13 Jul 2026, 06:58 UTC≈1,320 views6 reactionsread 6 August 2026
Photo

오랜만에 다시 삼 선물 + 현물 샀는데 내일 반등하면 좀 던질듯 60일선까진 가줬으면 좋겠네

6

7 Jul 2026, 09:59 UTC856 viewsread 6 August 2026
Forwarded from @economicrypto

https://blog.naver.com/economicrypto/224339455037

23 Jun 2026, 13:25 UTC≈2,680 views4 reactionsread 6 August 2026
Photo

코스피에 살림차린 남(코살남)께서 잘 설명해주심 https://m.blog.naver.com/dream_350/224324997842

4

23 Jun 2026, 08:51 UTC≈1,180 views9 reactionsread 6 August 2026
Forwarded from @eqmirae

[숏감마 이해하기] • 1억으로 2배 레버리지 ETF 매수 → 운용사는 2억 익스포저 유지 필요 • 기초자산 10%↑ → ETF 자산 1.2억 → 2배 맞추려면 2.4억 필요 → 0.4억 더 산다 (올랐는데 더 매수) • 반대로 떨어지면 → 판다 (내렸는데 더 매도) • 오르면 사고 내리면 파는 = 시장 따라가며 변동성 증폭 → 이게 숏감마 • 운용사가 옵션 판 것도 아닌데, 레버리지 ETF 일일 리밸런싱 구조 자체가 숏감마와 동일 *미래에셋증권 전략/퀀트 t.me/eqmirae

9

21 Jun 2026, 13:26 UTC≈7,350 views27 reactionsread 6 August 2026

글썼어여 제목으로 어그로좀 끌었음 https://blog.naver.com/sanoulzig/224322786715

27

20 Jun 2026, 10:11 UTC≈1,500 views9 reactionsread 6 August 2026
Photo

어짜피 버블 가격 먹으려면 주도주를 사야한다는 컨센이 점점 확산하기만 하니까 (엔트로피마냥) 결국 점점 더 쏠림 삼전보다도 하닉 차트가 더 쏘고 이걸 사람들이 인지함. 그러면 앞으로도 하닉>삼전 이지 않을까..? 삼전은 개별호재 있을때 단타용이라 생각 (26일 배당락일) 사진출처 : https://blog.naver.com/onejejuwave/224321656172

9

Showing the 12 most recent of 17 posts we hold for @zamboyak. 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 — 643,521 of 1,481,217entries 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

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

“잠이보약이다” (@zamboyak), 1,125 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/zamboyak.

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.