Telegram RegisterThe public register of Telegram
Telegram profile photo for Hatsune Mikuの小屋

Channel

Hatsune Mikuの小屋

@MikudesuChannels

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

2,836subscribers

+28 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003390896006
TypeChannel
Username@MikudesuChannels
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/MikudesuChannels

Growth

2,8072,8362,821.57 August 2026 — 2,808 subscribers7 August 2026 — 2,808 subscribers8 August 2026 — 2,809 subscribers11 August 2026 — 2,807 subscribers14 August 2026 — 2,836 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +28. 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 2,803–2,840 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:182,836+29
11 Aug 2026, 13:522,807-2
8 Aug 2026, 05:212,809+1
7 Aug 2026, 20:022,808no change
7 Aug 2026, 19:332,808first reading

Engagement

18 posts held, back to 11 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.8%
avg views ÷ 2,836 subscribers
Avg views / post
730
14 posts measured
Reaction rate
0.484%
reactions ÷ views · ER floor
Posts in window
14
of 18 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 8 of 14 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 2 August 2026
Posts held18 (11 July 20262 August 2026)
Views total10,226
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 20:02 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
3m 57s
Average length
40s

Measured directly from 6 videos 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

3,086 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 98.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🫡3,03298.3%
👍260.843%
😁110.356%
😭60.194%
50.162%
🤡30.097%
😱20.065%
🥰10.032%

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 9 of the 18 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 3,086reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 11 July 2026 to 2 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 18 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MikudesuChannels. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 11 July 2026 to 2 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

2 Aug 2026, 16:07 UTC371 views4 reactionsread 7 August 2026
Photo

诸神真的是从小看到大了😭

🫡2😁2

2 Aug 2026, 06:06 UTC503 views3 reactionsread 7 August 2026

到底是哪个出生一直刷我的弹弹api 尼玛的 凌晨两点配额全给我干完了 谁都别好好用了 下个版本弹幕功能上服务器验证 请求数高的离谱的IP直接飞了 此更新为破坏性更新 需要更新到最新版本才能使用默认的弹弹弹幕功能 如果有自建的则无需升级

🤡3

28 Jul 2026, 14:44 UTC884 views5 reactionsread 7 August 2026
File

无限城 简日字幕 自己外挂看吧 子集化好了 没做歌词 AI机翻 不喜勿喷 换好了 带歌词的版本 已Fin 只要是BDREMUX或者BDRip的鬼灭之刃无限城都适配

👍32

27 Jul 2026, 10:04 UTC798 viewsread 7 August 2026
Video

默认线路HK节点测速 网络:中国移动600M Wifi 节点良心云HK高速1号

27 Jul 2026, 10:04 UTC675 viewsread 7 August 2026
Video

默认线路新加坡节点测速 网络:中国移动600M Wifi 节点:良心云新加坡专线1号

27 Jul 2026, 10:03 UTC586 viewsread 7 August 2026
Video

默认线路美国节点测速 网络:中国移动600M Wifi 节点:良心云美国节点

27 Jul 2026, 10:02 UTC580 viewsread 7 August 2026
Photo

群U说想看看临镜新出的ONE EMBY如何 测评来也 “三无”卖点: 无售后客服 无求片支持 无直连线路 实际看下来 影视资源大概落后1个季度左右 我是根据电视剧和日漫的最新看出来的 然后... 好像没啥好说的 毕竟1元1个月 说白了这个价格能看就行 线路很不错 除了日本IP和国内IP不能链接 我挂良心云都起飞的速度 不说非常非常流畅 肯定也是很流畅的水准了 良心云的美国延迟巨高 然后速度跑满美国单线程 我觉得很足够了 港美新三个节点的表现都很好 网站开号 没TG也能轻松注册使用 👉🏼注册链接 👉🏼默认线路HK节点测速视频 👉🏼默认线路新加坡测速视频 👉🏼默认线路美国测速视频

25 Jul 2026, 18:07 UTC668 views1 reactionsread 7 August 2026

LinWeb更新了 地址在: https://t.me/MikudesuChannels/555 账户并进服务器管理,深浅切换挪到右上角,手机上补回返回键和下滑关闭 账户原来是左栏底下一个头像,唯一的动作是退出登录;而「服务器管理」 对非管理员整个隐藏。同一件事被拆成了两处,普通账号那边还剩一个死 角、并且没有任何地方能看出自己连在哪台服务器上。合成一个:服务器 标签常驻,账户卡排在最前 —— 它只读本地会话,是这一页上唯一不会 「不可用」的卡,管理员那些卡继续各自报各自的权限。深浅切换从导航 栏里挪到顶栏最右:它是个设置,不是第四个目的地。 手机上补的三件事,都是「缩小版 PC」缺的范式,不是尺寸问题: * 系统返回键。以前按返回直接离开整个应用。现在每个覆盖层押一个 history 条目,条目之间可互换 —— 不关心哪个条目属于哪一层,只 保证条目数不少于打开的层数,所以「菜单关闭的同时它打开的对话框

👍1

23 Jul 2026, 08:30 UTC823 viewsread 7 August 2026
Photo

LinWeb 1.1版本更新上线 努力黏住Emby官方网页端的脚底板 增加了移动端的布局 之前完全没做 现在做了 手机也能用了 还有一些大大小小的更新 看 Commit 7cc0084 和 Commit 4d490a2 有问题 有建议 ISSUE区见 随缘修 随缘加 👉仓库地址 👉DEMO地址 说明一下 国内网盘好像就123网盘可以用 因为他家直链不管UA 可以网页直接下 如果看不了 先确保你的浏览器(Edge/Chrome)是最新版 切记! 如果要使用该WEB端 一定要征求腐竹的意见! 一定要征求腐竹的意见! 一定要征求腐竹的意见! 否则封号了别来找我 GithubPages部署 因为CF会被屏蔽 后续可能会做:滚木

22 Jul 2026, 10:42 UTC909 views6 reactionsread 7 August 2026
Photo

作者自己做测试 已被封禁 所以一定要和腐竹申请 问问行不行

😁6

Showing the 12 most recent of 18 posts we hold for @MikudesuChannels. 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 — 960,517 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

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

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.

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.

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

“Hatsune Mikuの小屋” (@MikudesuChannels), 2,836 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/MikudesuChannels.

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.