Telegram RegisterThe public register of Telegram
Telegram profile photo for 米寳的宝宝们

Channel

米寳的宝宝们

@mibaodebaobao

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

950subscribers

+0 since we began measuring on 2 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003967896574
TypeChannel
Username@mibaodebaobao
Description个人账号 @mibao39756 双向 @mibao69832bot 个人频道
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 October 2026
Last confirmed live2 October 2026
Measurements held2
On Telegramt.me/mibaodebaobao

Growth

9502 Oct 2026, 09:47 — 950 subscribers2 Oct 2026, 10:22 — 950 subscribers2 Oct 2026, 09:472 Oct 2026, 10:22
2 measurements taken within a single day. 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 949–951 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 10:22950no change
2 Oct 2026, 09:47950first reading

Engagement

20 posts held, back to 22 September 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
52.0%
avg views ÷ 950 subscribers
Avg views / post
494
18 posts measured
Reaction rate
0.079%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 6 of 18 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 October 2026
Posts held20 (22 September 2026 – 2 October 2026)
Views total8,891
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Oct 2026, 10:22 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
17
Videos
7
Links
16

Lifetime counters from Telegram’s own channel header, read 2 October 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.

Video runtime
28s
Average length
7s

Measured directly from 4 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 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩133.3%
🤣133.3%
🥰133.3%

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

Measured over the 20 most recent posts we hold, published 22 September 2026 to 2 October 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

2 Oct 2026, 07:50 UTC133 viewsread 2 October 2026
Photo

💐💐💐开奖了💐💐💐 仙女宫天河米寶半价优惠奶茶抽奖 开奖了! 本期总参与人数: 436 1- 往事不隨風 (消息数 81)(翻倍1) 获得:1课半价优惠需在仙女宫写报告 2- Justin Fox (消息数 77)(翻倍1) 获得:100元优惠券 3- 啊水 (消息数 77)(翻倍10.0) 获得:100元优惠券 4- 金龙鱼 (消息数 42)(翻倍11.0) 获得:18.8元奶茶红包 5- X·Poise (消息数 53)(翻倍4.0) 获得:18.8元奶茶红包 谨祝中奖用户大吉大利万事顺意

2 Oct 2026, 07:07 UTC162 viewsread 2 October 2026
Photo

🎰 天河 米寶的半价优惠 📮 参与条件: 🎫 加入-广州·红人录 🎫 加入-广州凤吟修车茶馆备用群 🎫 加入-广州凤吟修车娱乐资源私密1 🎫 加入-米寳的宝宝们 🎫 加入-广州凤吟桩机报告 🎫 加入-广州凤吟修车茶馆 └ 🎟️ 发言数大于 15 条 🎫 加入-广州凤吟修车娱乐资源 🎁 奖品内容: 💰️ 100元现金红包 × 1 ⚠️ 抽奖说明: 中奖主动联系老师兑奖,开奖后三天内有效。 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年10月06日 20时00分00秒

2 Oct 2026, 06:53 UTC150 viewsread 2 October 2026

欢迎加入广州凤吟修车茶馆! 聊天交友,谈论出击,有多种游戏玩法。每日福利拉满,更设有报告门槛会员群为兄弟解决出击烦恼 🌱 农场游戏:播种快乐,简单操作,收获积分,随时来经营你的小农场,与老师互动。 ♠️ 德州扑克:牌逢对手,智趣相投,纯娱乐积分开牌,杜绝赌博。 米寶 已在凤吟视频验证上榜人照一致,可放心出击 点击下方连接可一键验证 https://t.me/GZFYLB/4098

2 Oct 2026, 04:15 UTC221 viewsread 2 October 2026

国庆快乐 感冒好了 状态很好 约起来哥哥门

27 Sept 2026, 05:53 UTC633 views0 reactionsread 2 October 2026
Photo

🎰 仙女宫天河米寶半价优惠奶茶抽奖 📮 抽奖条件: 🎫 加入-广州资源榜פּוּמְבֵּי『备胎』 🎫 加入-广州仙女宫中转站 🎫 加入-广州仙女宫 🎫 加入-米寳的宝宝们 🎫 加入-广州资源榜 🎫 加入-广深出师报告 🎫 加入-广州戒色宫『备胎』 🎟️ 要求活动期间群内发言数 20 🍀 每10分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: 1课半价优惠需在仙女宫写报告 × 1 100元优惠券 × 2 18.8元奶茶红包 × 2 💡 活动说明: 1:兑奖联系 @mibao39756 2:水群率越高中奖率越高喔 3:更多红包关注 @QMqun 4:半价出击需在仙女宫写报告否则拉黑抽奖 5:❗️群内严禁胡言乱语禁用脚本刷信息 6:❗️半价中奖即临时拉黑,提交报告后再解除 📅 开奖日期:(UTC+8) 2026年10月02日 15时50分52秒

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

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.

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

“米寳的宝宝们” (@mibaodebaobao), 950 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/mibaodebaobao.

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.