The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Channel
菠萝查档
@boluo64
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
784subscribers
-72 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001834498231 |
|---|---|
| Type | Channel |
| Username | @boluo64 |
| Created | Between 1 October 2022 and 22 June 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/boluo64 |
Topic
Hacking & security — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 06:25 | 784 | -6 |
| 20 Oct 2026, 21:59 | 790 | -3 |
| 14 Oct 2026, 16:37 | 793 | -6 |
| 8 Oct 2026, 05:16 | 799 | -7 |
| 26 Sept 2026, 19:37 | 806 | -10 |
| 11 Sept 2026, 17:21 | 816 | -7 |
| 3 Sept 2026, 08:57 | 823 | -11 |
| 27 Aug 2026, 11:47 | 834 | -8 |
| 21 Aug 2026, 08:25 | 842 | -5 |
| 15 Aug 2026, 07:46 | 847 | -9 |
| 7 Aug 2026, 15:40 | 856 | no change |
| 7 Aug 2026, 10:17 | 856 | first reading |
Engagement
18 posts held, back to 22 June 2023 — 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 18 posts for this entry, the most recent from 16 March 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
318 reactions across 15 posts, in 15 distinct kinds. The most used accounts for 63.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🖕 | 203 | 63.8% | |
| 🤣 | 30 | 9.43% | |
| ❤ | 19 | 5.97% | |
| 👍 | 17 | 5.35% | |
| 🤬 | 16 | 5.03% | |
| 😡 | 11 | 3.46% | |
| 💊 | 4 | 1.26% | |
| 🕊 | 4 | 1.26% | |
| 🤪 | 4 | 1.26% | |
| 🏆 | 3 | 0.943% | |
| 💅 | 2 | 0.629% | |
| 💔 | 2 | 0.629% | |
| 💘 | 1 | 0.314% | |
| 😈 | 1 | 0.314% | |
| 🤔 | 1 | 0.314% |
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 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 318 reactions 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 22 June 2023 to 16 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.
Recent posts
开工 全户 微反一件套 二件套 人脸识别 电信百分百 猎魔 名下车 支百 开同 人鬼 大关联 法人批量 邮政 顺丰 业务及基本都在欢迎咨询 @boluo68
Photo, posted without a caption
❤6👍1
全户正在回单,要报的速度,现在还可以秒 @boluo68
👍1
全户开秒美团 饿了么带单号稳定回 精准人脸开秒 联通秒到晚上1点 车轨5+1拍照每天出 婚姻秒 个户秒 名下号稳定当天回 车小档秒 猎魔每天秒 护照反秒 网逃 名下车 每天都秒 不需要等 婚姻秒 个户小秒 神父秒 疫苗手机号常用号秒 车小档秒 以上基本秒开 急单来报 欢迎律师 催收 公群商家合作 欢迎内部人员合作 一起赚钱 需要联系 @boluo68
免费接码机器人 https://t.me/c_sms_bot?start=5720294292
😡3💅2💘1
美团饿了么一体地址 @boluo68 带单号 订单内容 收货地址 昨天点的外卖今天都能出 找人必备,准过快递地址
😡3🤬2👍1
所有业务开工
🤬5❤4💔1
移动电百联通秒可以出历史机主价格秒杀市场需要来车小档优势价全户开真地址个户银行卡预留飞火开同一体微提好友微反手机号人脸识别16头猎魔 三网名下号快递地址民政双图婚姻开房记录都是优势价 @boluo68
🖕9🏆3❤2😡2👍1
新线支百出单率极高,优势价格,凌晨秒单
🖕17🤪2💔1😈1
v反低价收一波,条子已读就秒 @boluo68
🤬9❤4👍4🕊2🤪2🖕1
虽然咱是干的黑产干查档,但是咱也是信誉办事,不出假单,出空就退,上家跑路我垫付
🖕35🤣12😡3💊1
Showing the 12 most recent of 18 posts we hold for @boluo64. 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.
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“菠萝查档” (@boluo64), 784 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/boluo64.
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.