Telegram RegisterThe public register of Telegram

Channel

MIKU的小窝 🪭🎄

@onelazyfish

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

11,047subscribers

-7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001532276772
TypeChannel
Username@onelazyfish
Description🐟🐟🐟🐟🐟🐟~ 想法想法想法想法~
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/onelazyfish

Growth

11,04711,05511,0517 August 2026 — 11,054 subscribers8 August 2026 — 11,055 subscribers9 August 2026 — 11,054 subscribers10 August 2026 — 11,051 subscribers11 August 2026 — 11,048 subscribers12 August 2026 — 11,047 subscribers7 August 202612 August 2026
6 measurements spanning 5 days, net -7. 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 11,046–11,056 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:2411,047-1
11 Aug 2026, 08:3811,048-3
10 Aug 2026, 07:1411,051-3
9 Aug 2026, 05:0311,054-1
8 Aug 2026, 06:3211,055+1
7 Aug 2026, 09:4511,054first reading

Engagement

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

ERR · 30 days
16.4%
avg views ÷ 11,047 subscribers
Avg views / post
1,810
10 posts measured
Reaction rate
0.83%
reactions ÷ views · ER floor
Posts in window
10
of 21 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 9 of 10 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 8 August 2026
Posts held21 (18 May 20268 August 2026)
Views total18,130
Reactions total137
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 04:28 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

Photos
102
Videos
3
Links
147

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

226 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 17.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤯3917.3%
👍3615.9%
🥰3113.7%
😱3013.3%
😨2410.6%
229.73%
🤣187.96%
🤔177.52%
🔥52.21%
🤓41.77%

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

Measured over the 21 most recent posts we hold, published 18 May 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.

Recent posts

8 Aug 2026, 07:14 UTC≈1,000 views4 reactionsread 13 August 2026

https://t.me/PhantomInjector/45 推广一下隔壁频道的去签名☺️

4

Signed 无法想象的想法 ​  小美人鱼

5 Aug 2026, 23:21 UTC≈1,520 views21 reactionsread 13 August 2026

数值知道了2.7,现在回钾回到了5.8

👍183

Signed 无法想象的想法 ​  小美人鱼

5 Aug 2026, 16:11 UTC≈1,610 views23 reactionsread 13 August 2026

低钾血症,血液钾浓度2.几的

🤯18😱5

Signed 无法想象的想法 ​  小美人鱼

5 Aug 2026, 12:58 UTC≈1,670 views23 reactionsread 13 August 2026

急诊ing

😱23

Signed 无法想象的想法 ​  小美人鱼

5 Aug 2026, 10:07 UTC≈1,710 views11 reactionsread 13 August 2026

改完了,我也准备去医院了,现在腿废了,跟残疾人一模一样

🤔11

Signed 无法想象的想法 ​  小美人鱼

5 Aug 2026, 10:06 UTC≈1,620 viewsread 13 August 2026
Photo

折 花 令 V P N 链接【 cutt.ly/urxa52cd 】 🌐2Gb/s大带宽的端口 🏬流媒体全解锁 💬月付10块100G,且有0.2x低倍率节点 🎉三网合一,不惧晚高峰跨网限速 顶级中转机场,你们可以看评论区的测速图,速度拉满,我觉得不用多说,所以速度方便不用担心。 机场有问题可以发工单,也可以私聊机场主 @zhaihuavpn ,也可以在评论区问

Signed 无法想象的想法 ​  小美人鱼

5 Aug 2026, 10:00 UTC≈1,570 views10 reactionsread 13 August 2026
File

版本号:7.1.7 过签名:MT2 修改内容:移除大部分广告,移除了邮箱列表插入广告,移除了更新检测,将QQ登陆强制改为网页登陆 技术支持:deepseek 辅助分析,奶喵 弹窗技术支持 可能的bug:用户头像不显示,弹窗弹出无效

7👍3

Signed 无法想象的想法 ​  小美人鱼

2 Aug 2026, 03:19 UTC≈2,500 views34 reactionsread 13 August 2026
Photo

🤯20🤣9🤓41

Signed 无法想象的想法 ​  小美人鱼

31 Jul 2026, 17:58 UTC≈2,480 views4 reactionsread 13 August 2026

转载个隔壁的,凑个热闹

👍4

Signed 无法想象的想法 ​  小美人鱼

31 Jul 2026, 17:58 UTC≈2,450 views7 reactionsread 13 August 2026
Forwarded from @cxapkFile

基于api102重构的模块,目前模块适配的软件还不全,只有部分软件加入了。 软件采用全新UI和逻辑,欢迎使用。 UI设计/开发 @Duanxa 模块代码 @cxapk

👍61

Signed 无法想象的想法 ​  小美人鱼

11 Jul 2026, 07:16 UTC≈4,230 views0 reactionsread 13 August 2026

能研究出来怎么把adsdk处理掉,但是研究不明白为什么还能检测到非官方apk🤐

Signed 无法想象的想法 ​  小美人鱼

11 Jul 2026, 05:50 UTC≈4,040 viewsread 13 August 2026

很好,沟槽的签名校验😠 (Tips,这里是指MT的过签不支持滴滴,所以走了个歪路来尝试过签,然后…过签炸了) 没事了,我是笨比

Signed 无法想象的想法 ​  小美人鱼

Showing the 12 most recent of 21 posts we hold for @onelazyfish. 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.

Forward network

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.

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

“MIKU的小窝 🪭🎄” (@onelazyfish), 11,047 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/onelazyfish.

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.