3 measurements spanning 3 days, net -10. 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 4,404–4,417 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 19:31
4,405
-9
8 Aug 2026, 04:52
4,414
-1
7 Aug 2026, 07:45
4,415
first reading
Engagement
22 posts held, back to 4 August 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 6 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
3.10%
avg views ÷ 4,405 subscribers
Avg views / post
137
22 posts measured
Reaction rate
8.25%
reactions ÷ views · ER floor
Posts in window
22
of 22 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
Window
Rolling 30 days · latest post in window 8 August 2026
Posts held
22 (4 August 2026 – 8 August 2026)
Views total
3,007
Reactions total
248
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 18:16 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
248 reactions across 22 posts, in 7 distinct kinds. The most used accounts for 38.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
95
38.3%
🔥
71
28.6%
🥰
58
23.4%
😱
10
4.03%
😢
9
3.63%
😁
4
1.61%
👏
1
0.403%
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 22 of the 22 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 248reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 4 August 2026 to 8 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.
✔️X 수익화 정책 변경, 기존 계정도 새 프로그램 신청 필요
X가 기존 Revenue Sharing을 종료하고 Original Content Rewards 프로그램으로 전환합니다.
트윗원문
기존
• 수익화 조건을 충족한 계정이 조회수 기반으로 수익 배분
• 다른 콘텐츠를 인용·재가공한 게시물도 상대적으로 수익화 가능
변경 후
• 직접 만든 오리지널 콘텐츠의 조회수만 보상 대상
• 단순 복사, 짜깁기, 최소 수정, 타 플랫폼 재업로드 콘텐츠는 제외
• 단순 조회수가 아니라 Premium 이용자의 홈 타임라인 유효 노출이 중요
• 최근 90일 인증 사용자 홈 조회수 50만회 + 인증 팔로워 500명 이상 필요
• 기존 수익화 계정도 9월 8일부터 새 프로그램에 다시 신청해야 함
✍️즉, 앞으로는 “얼마나 많이 퍼왔느냐”보다 직접 만든 글…
정말 도움을 요청드리고 싶어 이렇게 올립니다.
정말 무거운 마음으로 이 글을 올리게됩니다.
저희 아버지는 대형회사에서 IT담당 임원으로 계십니다. 메모리가격 인상에 따라 계약을 재체결하는 과정에서 높은가격으로 재 계약을 진행하는 과정에서 제대로 진행되지 못하고 최종 결재자가 되시면서 감사에서 계속해서 회사에 수백억에 가까운 손해를 입혔다고 압박을 받으시는것 같습니다.
결론이 나지 않았지만 수백억을 추징을 당할 수 있다는 압박감에… 좋지못한 선택을 시도하셨습니다.
혹시 이와관련하여 상담을 할 수 있거나 관련 전문가를 알고 계신분이 있다면 지나치치지마시고 한번만이라도 조언을 주시면 너무나도 감사하겠습니다.
제가 지금 당장 못하더라도 꼭 평생에 걸쳐서라도 보은하겠습니다
빗썸(Bithumb) 공지
유니베이스(UB) 원화 마켓 추가
2026-08-06 10:19:07
🥰4❤2🔥2
Showing the 12 most recent of 22 posts we hold for @MBMDiary. 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 — 802,602 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.
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
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Москва 24/7 @msk7days · 2,223,004 Telegram ranks this channel #57 of 67 here — alongside 66 others — read 10 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“리무의 일기장” (@MBMDiary), 4,405 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/MBMDiary.
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.
