Channel
@hibobi
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
410subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001926097081 |
|---|---|
| Type | Channel |
| Usernames | @bobiws888 @hibobi |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/hibobi |
Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 86% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 15:18 | 410 | +1 |
| 16 Sept 2026, 06:17 | 409 | +3 |
| 9 Sept 2026, 01:00 | 406 | -1 |
| 8 Sept 2026, 00:36 | 407 | no change |
| 31 Aug 2026, 04:25 | 407 | -1 |
| 29 Aug 2026, 20:23 | 408 | -1 |
| 24 Aug 2026, 21:49 | 409 | no change |
| 23 Aug 2026, 00:12 | 409 | -2 |
| 17 Aug 2026, 13:06 | 411 | no change |
| 15 Aug 2026, 00:33 | 411 | +2 |
| 9 Aug 2026, 07:16 | 409 | -1 |
| 8 Aug 2026, 05:35 | 410 | no change |
| 7 Aug 2026, 14:19 | 410 | first reading |
15 posts held, back to 8 August 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 2 pages 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 15 posts for this entry, the most recent from 27 February 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
25 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 56.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 56.0% | |
| 👍 | 6 | 24.0% | |
| 🔥 | 3 | 12.0% | |
| custom 5363920802695617184 | 1 | 4.00% | |
| 🎉 | 1 | 4.00% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 11 of the 15 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 8 August 2024 to 27 February 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.
【近期Whatsapp图文效果问题🥰】 ✅【近期客户打的反馈图】👉 ✅本公司Ws图文群发模式送达率均为95%以上，只要数据没问题，随便万100+😵💫 ✅本公司承诺真实百分百发送量，支持埋雷各种硬核测试！不存在偷工减料行为。🥴 ✅出海五年零纠纷，各大出海会员靠谱有保障，Ws知识储备强，专业的技术顾问，靠谱老牌通道，让您少走弯路。🤐 📱客服：@bobiws （博比） @wsbobi(博比） 😀😂😚🤓😀😃😄😁😆🥹😅😂🤣🥲
❤1
一马当先，不止步，万马奔腾，共辉煌。 🦼🩼🛴🚲 🛵🏍️🛺🛞
❤1
博比 WS/RCS/iM群发 WS协议号 pinned a video
【近期有骗子模仿我们导致金钱损失】🥰 🥰请认准唯一商务号！！其余都是假冒！！ 📱客服：@bobiws （博比） @wsbobi(博比） 📱客服：@bobiws （博比） @wsbobi(博比） 📱客服：@bobiws （博比） @wsbobi(博比） 😀😂😚🤓😀😃😄😁😆🥹😅😂🤣🥲
❤3🔥3👍2
【认准五年老牌WS群发】🥰 【Whatsapp群发图文超链】🥰 🥰图片+文案+按钮=效果大爆炸💥 【日发送百万量】 🥰（可用性多样化，巴西BC类，B圈，TG链接，等一切落地页） 支持各种硬核埋雷测试 🥰本公司专注于各类Whatsapp群发业务，有专业的技术顾问，靠谱的通道，让客户少走弯路。 🥰本公司群发老通道，出海四年零纠纷，通道送达率平均值均为95%以上，支持各种硬核埋雷测试验证！！质量为主，服务至上，博比群发为你保驾护航！ 📱客服：@bobiws （博比） @wsbobi(博比） 😀😂😚🤓😀😃😄😁😆🥹😅😂🤣🥲
❤3
【Whatsapp群发自定义图文】🥰 🥰图片+文案+自定义按钮，大大提高进线效果（适合巴西BC类，B圈，TG链接，等一些列落地页） 🥰还未攻破来单秒发送，发送速度正常，支持各种硬核埋雷测试，支持超链，图文超链模式。 🥰本公司专注于各类Whatsapp群发业务，有专业的技术顾问，让客户少走弯路。 🥰本公司群发老通道，出海四年零纠纷，通道送达率平均值均为95%以上，支持各种硬核埋雷测试验证！！质量为主，服务至上，博比群发为你保驾护航！ 📱客服：@bobiws （博比） @wsbobi(博比） 😀😂😚🤓😀😃😄😁😆🥹😅😂🤣🥲
iM（苹果推）卡发,全面恢复,需要的连续 @bobiws 文字图文超链持续发送中,有量直接排,真实发送。
👍1
【Whatsapp群发重大通知】🥰 🥰经过本公司技术半个月各种通宵熬夜的优化，Ws协议发送已经突破官方大风控屏蔽问题，恢复到24年巅峰时期。 🥰还未能做到秒发送，发送速度正常，支持各种硬核埋雷测试，支持普链，超链，图文模式 🥰云控的发送效果，协议的价格，送达率95%以上，实打实发送。 🥰本公司群发老通道，出海三年零纠纷，通道送达率平均值均为95%以上，支持各种硬核埋雷测试验证！！质量为主，服务至上，博比群发为你保驾护航！ 📱客服：@bobiws （博比） @wsbobi(博比） 😀😂😚🤓😀😃😄😁😆🥹😅😂🤣🥲
❤1
【Whatsapp群发重大通知】🥰 🥰经过本公司测试，Ws协议发送已经突破官方大风控问题，有望恢复到24年中秒发疯狂时候，秒发送达率高！ （后续完全解决量级问题大量无限制收单） 🥰群发老通道，出海三年零纠纷，通道送达率平均值均为99%左右，支持各种硬核埋雷测试验证！！质量为主，服务至上，博比群发为你保驾护航！ 📱客服：@bobiws （博比） @wsbobi(博比） 😀😂😚🤓😀😃😄😁😆🥹😅😂🤣🥲
💠苹果推（iM）也恢复正常，量有限，及时安排，完美破解风控问题，送达率接近100%
博比 WS/RCS/iM群发 WS协议号 pinned a photo
💠WS超链（图文模式）发送，已实时优化到最新官方风控版本，可正常大量接单。 💠WS超链（文字模式）发送，已实时优化到最新官方风控版本，可正常大量接单。 💠官方死接待号风控问题还未完全解决，近期逐步一一测试，请尝试不死接待号，或者一年老号。 📱客服：@bobiws （博比） @wsbobi(博比） 😀😂😚🤓😀😃😄😁😆🥹😅😂🤣🥲
❤1
Showing the 12 most recent of 15 posts we hold for @hibobi. 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“博比 WS/RCS/iM群发 WS协议号” (@hibobi), 410 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hibobi.
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.