Telegram RegisterThe public register of Telegram
Telegram profile photo for Karen医生の日常

Channel

Karen医生の日常

@KarenMoeMoe

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

9,370subscribers

+23 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001077688074
TypeChannel
Username@KarenMoeMoe
Created2 October 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/KarenMoeMoe

Growth

9,3429,3709,3566 August 2026 — 9,347 subscribers6 August 2026 — 9,347 subscribers9 August 2026 — 9,342 subscribers12 August 2026 — 9,358 subscribers16 August 2026 — 9,370 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net +23. 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 9,338–9,374 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 03:159,370+12
12 Aug 2026, 06:349,358+16
9 Aug 2026, 05:019,342-5
6 Aug 2026, 14:309,347no change
6 Aug 2026, 11:049,347first reading

Engagement

34 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.97%
avg views ÷ 9,370 subscribers
Avg views / post
841
34 posts measured
Reaction rate
0.958%
reactions ÷ views · ER floor
Posts in window
34
of 34 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. It is computed over the 21 of 34 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 August 2026
Posts held34 (31 July 202615 August 2026)
Views total28,588
Reactions total199
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 08:53 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.

What this channel posts

Video runtime
18s
Average length
18s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

199 reactions across 20 posts, in 18 distinct kinds. The most used accounts for 17.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💅3417.1%
3115.6%
😇2814.1%
😱2713.6%
👍199.55%
😁157.54%
🥰94.52%
🤡84.02%
👏63.02%
🥴63.02%
👨‍💻31.51%
🤯31.51%
👎21.01%
🔥21.01%
😨21.01%
🤣21.01%
10.503%
😢10.503%

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 21 of the 34 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 199reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 34 most recent posts we hold, published 31 July 2026 to 15 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

15 Aug 2026, 00:53 UTC396 viewsread 15 August 2026

繁中中英混用挺多的,之前看繁中涩涩小说部分内容真的很难快速阅读理解下去(

15 Aug 2026, 00:52 UTC361 views3 reactionsread 15 August 2026

給所有這幾天上工的PGY:隨時檢查護理紀錄! 我在某區域醫院PGY時,半夜被call病人急救。後來ROSC去ICU。我睡不著覺點護理紀錄看,護理紀錄寫好幾次打給我,我都說續觀,然後最後一次護理師去看,發現心跳停止摳我,我才出來。 我大為震驚,因為我完全沒接到電話! 隔天早上我立刻往上報這件事,查了監視器發現是外傭半小時內好幾次到護理站求救,說阿公喘,但護理師都在聊天,把外傭打發回去,也沒打給我,最後一次真的去才發現病人已經咖掉。 我們病房的住院醫師學長暴怒,帶著我去找阿長興師問罪,阿長在我們面前刪掉護理紀錄,說沒這件事,但沒按儲存。一個學長把阿長推開,另一個學長按取消然後拿出手機拍螢幕,阿長才跟我鞠躬道歉。 後來寫紀錄的小夜護理師一邊哭,一邊說是三個大夜班學姊教她這樣寫的。 我的主治醫師事後轉述,院層級討論這件事的時候,醫師端都大怒,要求火掉這幾個護理師,但護理部說「平常你們住院醫師犯錯,我們也不會要求開除住院醫師啊

😱3

15 Aug 2026, 00:50 UTC335 views2 reactionsread 15 August 2026
Forwarded from @ddjddjdgjPhoto

本來我也恨國 後來中醫調理好了

👏2

15 Aug 2026, 00:50 UTC333 views4 reactionsread 15 August 2026

https://fxtwitter.com/dearemon/status/2083460003487465535?s=20

💅3🤣1

15 Aug 2026, 00:49 UTC317 viewsread 15 August 2026
Forwarded from @langrenshudongPhoto

Photo, posted without a caption

15 Aug 2026, 00:48 UTC319 views1 reactionsread 15 August 2026
Forwarded from @pingrangTVPhoto

大哥铁腚是个硬汉😨

🤯1

15 Aug 2026, 00:45 UTC349 viewsread 15 August 2026
Photo

侃山雕 (Twitter/X) 今天做了一例感染性心内膜炎,左冠窦和无冠窦各有一个感染破口,再晚些做指定要主动脉夹层,往近端破的话可能人就去了。感冒发烧还是要早诊断早治疗,不要硬抗啊。

15 Aug 2026, 00:45 UTC341 views3 reactionsread 15 August 2026
Forwarded from @ibuki_KitakubuPhoto

Photo, posted without a caption

😁3

Showing the 12 most recent of 34 posts we hold for @KarenMoeMoe. 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,122,902 of 1,481,243entries 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

Named by 3 registered channels — 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.

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.

每日沙雕墙
@woshadiao · 115,392
Telegram ranks this channel #24 of 52 here — alongside 51 others — read 14 August 2026
竹新社
@tnews365 · 156,603
Telegram ranks this channel #48 of 59 here — alongside 58 others — read 12 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“Karen医生の日常” (@KarenMoeMoe), 9,370 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/KarenMoeMoe.

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.