Channel
@bigme_pro
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
790subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001822284812 |
|---|---|
| Type | Channel |
| Username | @bigme_pro |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/bigme_pro |
Technology — 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 91% 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 |
|---|---|---|
| 11 Oct 2026, 21:16 | 790 | -1 |
| 30 Sept 2026, 17:20 | 791 | -1 |
| 16 Sept 2026, 00:41 | 792 | -1 |
| 8 Sept 2026, 02:38 | 793 | +1 |
| 29 Aug 2026, 08:46 | 792 | -3 |
| 16 Aug 2026, 01:58 | 795 | -2 |
| 8 Aug 2026, 01:36 | 797 | no change |
| 7 Aug 2026, 20:25 | 797 | first reading |
20 posts held, back to 5 June 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 20 posts for this entry, the most recent from 9 July 2025. An engagement rate over an empty window would be a number about nothing.
33 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 45.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 45.5% | |
| 👍 | 8 | 24.2% | |
| 🥰 | 8 | 24.2% | |
| 😈 | 2 | 6.06% |
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 13 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 33 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 5 June 2024 to 9 July 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.
👺 订阅更新提示 1️⃣ 最近通报频繁，原有的线路隐藏，更新订阅之后自动消失，并不在维护 2️⃣ 新增 vless 协议并搭配最优的线路，需要搭配相应的软件使用 软件地址： https://mihomo.party/ https://github.com/clash-verge-rev/clash-verge-rev 3️⃣ 软路由用户及时更新内核，使用 mihomo 内核即可支持，如果你无法获取到，可以自行设置订阅 ua 为 verge 即可 4️⃣ 安卓使用 https://github.com/MetaCubeX/ClashMetaForAndroid 5️⃣ 苹果小火煎兼容，圈 x 兼容 6️⃣ 缺失的冷门节点将在未来陆续添加回来 ps：如果你使用不支持的软件，可以工单提交你的数字货币地址 / 留下支付宝账户姓名，我们进行退款
❤6😈2👍1
EMBY 迁移中，好叻
EMBY 服务商会在近期迁移到 9950x 的机器，到时候也会三十分钟之内的不可用，提前逼逼一下
❤4
有一个入口有波动，处理中
稍微挤一点，今晚上 有一个移动入口闪断有点恶心，打算不用了 三线入口专线还是一倍率
Emby母鸡正在迁移，为了保持迁移前后数据一致性，开号机器人已经暂停使用，等迁移完成，自然就可以开号了 母鸡从hz的欧洲换到美国，cdn线路从德国换到快车道美国节点
❤1
准备一次扩容，半小时后，应该是无感的； 为扩容前的准备，原广东移动入口已经下线，导致总带宽下降，所以现在有点卡， 等新入口上线，会有所改善 无感的，并不需要做什么操作
2月28日，十一点之前，有一个广州移动入口，要维护一下，顺利的话，断线十秒钟，不顺利的话 断线五分钟
Fileball 播放如果403，就更新一下，因为这个软件更新了！
机器维护了，上游现在 好了已经
emby故障，已经反馈了 8号又故障了，已经反馈了和催促
Emby机器人误报通知，已经修复，原因是订阅WAF规则出错了，现在已经修复，如果万一有影响您的账户，请重新开一下账户，对不起；没影响，就忽略！ ⚠️你的订阅链接疑似失效，请检查你的订阅，否则你的emby账号将会被禁用⚠️
❤2
Showing the 12 most recent of 20 posts we hold for @bigme_pro. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“BigME|大米加速” (@bigme_pro), 790 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/bigme_pro.
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.