Channel
@baobao_bao_bao
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
48subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001862330043 |
|---|---|
| Type | Channel |
| Username | @baobao_bao_bao |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/baobao_bao_bao |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 18:38 | 48 | -1 |
| 10 Aug 2026, 12:31 | 49 | no change |
| 8 Aug 2026, 07:16 | 49 | first reading |
11 posts held, back to 9 March 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 28 March 2025. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 2 of the 11 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 9 March 2024 to 28 March 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
飞机号被双向限制解封教程 👉第一步： @spambot 👉第二步： 点击/Start 👉第三步： 点击/But I can't message non-contacts! 👉第四步： 点击/No,I'll never do any of this! 👉第五步：发送（ Hello, dear Telegram support, please remove me from the report. I was reported by mistake. Please release my account. I did not disturb anyone, they blocked me by mistake. I promise to I will not and not disturb anyone, and I did not do this. Please release my account. ）（）👆括号…
❤1
我的错，以后回答别人问题前应该先问接不接受先款，不然浪费时间精力。在这里给这位大哥道个歉，我不该点那个举报垃圾信息的，刚刚实在是有点气。我还得修行，精进🙏
#能量 转错退回，目前最大的一笔🥹 感谢各位老板支持
#能量 #转错退回 感谢老板支持，老板很大气！原路退回的话我处理不了，老板就说只要我垫付50U就行，转错71U。原路退回的话就只扣1U手续费就行。🙈也就是老板打赏了我20U😋开心开心
#转错退回 查询的是客户地址的交易记录，支出到转账能量地址65U，收入退回64U。 那些买个 #飞机号 几块钱不敢先款，付了口令没有第一时间回复还自己领的，真别来恶心人了。 txid : 4258ad5ea824280deae91f1712a693e8d72172f5200b62c77f0044fa0eb50dfa
#转账能量 转错55U 退回原地址扣除1U手续费，转错是很常见的，很多钓鱼的就是靠转错赚钱，我这边不赚这种钱。转错了联系我就退回哈
tg骗子非常多！比你穷的骗，比你富的也骗！以前天下还会苦秦，现在只会互害 #吃瓜
转错小额U的，退款后闪兑成TRX提现只需要1trx手续费。放心使用~
#飞机号 好用或者不好用你都不会吃亏，与其一直问我为什么无码，我更喜欢直接退款。无码有写解决办法按照写的来就行，不行就退款很好说的❤️
原路退回会扣除1U手续费，而且比较慢，耐心等待感谢支持🤪老板总是这样神龙见首不见尾，不过是个好老板，也是我心爱的宝贝🫶
转错数量金额大的，支持原地址退款。金额小的支持 @okpay 或新币的 @qianbao 退款
Showing the 11 most recent of 11 posts we hold for @baobao_bao_bao. 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.
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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“生活不易” (@baobao_bao_bao), 48 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/baobao_bao_bao.
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.