Channel
@o123456
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
41,730subscribers
+4,050 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001299894578 |
|---|---|
| Type | Channel |
| Username | @o123456 |
| Description | 📣神马搜索官方公告✅ |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/o123456 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 07:53 | 41,730 | +22 |
| 12 Aug 2026, 09:53 | 41,708 | +20 |
| 11 Aug 2026, 06:31 | 41,688 | -237 |
| 9 Aug 2026, 00:55 | 41,925 | +4,245 |
| 7 Aug 2026, 18:30 | 37,680 | no change |
| 7 Aug 2026, 18:23 | 37,680 | first reading |
11 posts held, back to 30 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof 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 25 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 August 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.
Measured directly from 1 video 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.
1,098 reactions across 11 posts, in 29 distinct kinds. The most used accounts for 25.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 278 | 25.3% | |
| ❤ | 243 | 22.1% | |
| 🔥 | 142 | 12.9% | |
| 🎉 | 140 | 12.8% | |
| 😁 | 116 | 10.6% | |
| 🥰 | 29 | 2.64% | |
| 👏 | 22 | 2.00% | |
| 🤩 | 22 | 2.00% | |
| 💩 | 19 | 1.73% | |
| 🆒 | 9 | 0.82% | |
| 🫡 | 9 | 0.82% | |
| 💯 | 8 | 0.729% | |
| 🤮 | 8 | 0.729% | |
| 👻 | 7 | 0.638% | |
| 🍓 | 6 | 0.546% | |
| 😢 | 6 | 0.546% | |
| 👌 | 5 | 0.455% | |
| 😱 | 5 | 0.455% | |
| 🌚 | 4 | 0.364% | |
| ⚡ | 3 | 0.273% | |
| 9 further kinds | 17 | 1.55% |
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 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,098reactions 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 30 July 2025 to 25 May 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.
📣【频道 / 群组使用公告】 💡因 Telegram 偶发限流问题，机器人加入频道或群组后，可能出现以下情况： • ⌛邀请完成后无任何响应 • ⌛没有自动发送设置消息 ⭐️如遇以上情况，请直接在频道或群内发送： /door ➡️系统会自动进行修复并重新触发设置按钮⚙️（仅邀请机器人为管理员的账号可点击设置） ⭐️实用小技巧🔥 @smss ✅ 🖥1️⃣ 修改频道 / 群用户名后 请点击【同步】按钮更新信息. 🔝2️⃣ 开启频道联盟（拉新功能） 开启后可获得内容收录机会，提高曝光与展示。 🔄3️⃣ 邀请助力功能 邀请成员参与助力，可提升频道/群组活跃度与曝光度。 🛡4️⃣ 搜索群组建议开启【反垃圾模式】 开启后可有效减少广告、刷屏及异常消息，提高群组管理效率。
👍26❤21🆒6⚡3👌3🔥3🤝3🫡2
📢 批量续费/竞拍功能说明✅ 🛑批量续费规则 批量续费功能单次最多支持 100条 数据处理。 如超过数量限制，请分批操作，以免出现异常或失败情况。 📜 关键词竞拍规则 ⏰ 时间 • 提前10天提醒 • 前8天：原广告主优先续费 • 后2天：开放竞拍 💰 出价 • 底价 = 正常价格 • 每次加价 ≥ 当前价 +10% • 出价后不可修改/取消 💳 扣款 • 出价即扣营销余额 • 加价补差额 • 不支持优惠/折扣 ⚖️ 结算 • 到期自动结算 • 最高价中标 • 同价先出优先 • 未中标自动退款（营销余额） • 生效：到期后开始，1个月 如在使用过程中遇到任何异常或问题，请及时联系客服处理。 ✅ @smbot 📌 温馨提示：关键词广告价格 随市场行情每日更新，购买/续费价格以 即时标价 为准（每日 北京时间 00:00 更新）。 🏆查询关键词价格指令 /buy 关键词 如举例 /buy 神马 可查询关键词…
❤23😁17👍12🎉11🔥9🤮3🍓2🌚1
✅ 神马搜索功能重磅升级公告📣 本次版本已完成多项核心升级，全面提升搜索体验、管理能力与信息服务质量，重点更新如下： 🔍 一、搜索体验全面优化 🔺精准排序：优先展示与关键词高度匹配的内容 🔺智能降权：打击关键词堆砌等低质量结果 🔺安全过滤：自动屏蔽被 Telegram 标记的诈骗/冒充内容 🔺详情页上线：支持点赞、点踩、助力、举报等互动功能 ⸻⸻⸻⸻ 📂 二、频道与群组目录升级 🔺分类体系动态更新，内容更丰富 🔺搜索范围覆盖名称、简介、标签 🔺默认按成员人数排序，更高效发现优质内容 ⸻⸻⸻⸻ 📰 三、热门资讯重磅升级 🔹聚合多家主流媒体（科技 / 财经 / 娱乐等） 🔹支持分类浏览 + 快速搜索 一键转发分享，获取信息更便捷 🔹热门资讯自动推送至资讯频道 🔹新增虚拟币 和 贵金属行情 ⸻⸻⸻⸻ 🔗 四、链接管理更高效 🔹/link 一键查看全部提交记录（支持翻页） 🔹按状态筛选（待收录 / 已收录 / 已封禁） 🔹支持…
🥰23👏16❤10🔥9👍7🤩7🌚3😈2
🚀 Telegram群管、客服，机器人克隆系统上线，免费使用 无需技术 无需代码 即可拥有自己的机器人 支持功能： 克隆完全属于自己 🤖 群管理 👨💻 客服系统 📢 频道自动推送 ⏰ 定时广告 🧩 一键克隆成自己的机器人 适合： ✔ 群主 ✔ 项目方 ✔ 做广告联盟 ✔ 做机器人变现 👉 立即创建自己的机器人 @CoolFaBot
❤29🤩15🔥8👏6👍3🥰3🤮2💩1
ㅤㅤ🔴🔴🔴🔴🔴🔴🔴🔴 ㅤ⭐️新岁序开,共赴新程.⭐️ 🌟感恩每一位客户与用户的陪伴支持🌟 ✅神马搜索 @smss 携全体员工祝您： ⭐️春风得意马蹄疾⭐️富贵花开满庭芳。⭐️积金累玉，锦衣玉食，福泽绵长，富贵安康.⭐️ ㅤ 🔴🔴🔴🔴🔴🔴🔴🔴
🎉117🔥106👍105❤104😁89🌭3💯3🥰3
🚀 神马搜索 3.0 正式上线 | 系统更新公告 —— 净化生态 · 提升质量 · 共建长期价值 各位联盟者您们好： 为进一步净化平台生态、提升内容质量与用户体验，神马搜索系统已全面升级至 3.0 版本，本次更新重点如下，请务必认真阅读并遵守： ✅【搜索算法全面升级】 系统将大幅压制低质、重复、无价值内容，优质内容获得更高权重与曝光机会。 ⚠️【严厉打击关键词与 Emoji 堆砌】 系统已升级智能识别逻辑，任何形式的违规堆砌行为将被直接降权处理，严重者将限制推荐。 🚫【零容忍广告与同行推广】 禁止在群组、频道内发布同行推广、引流广告等内容。 机器人已开启 24 小时自动巡查，发现即下架，情节严重将直接封号处理。 ℹ️【搜索联盟规则调整说明】 即日起： 加入搜索联盟后不再自动派发代理优惠券（不影响搜索群原有收益机制），请知悉。 🎡【系统性能优化】 搜索与机器人响应速度再次大幅提升，整体操作更流畅、更稳定。 ✨ 平台发…
💩13🫡6😢6❤5😱5🍓4🖕1🤮1
👑新增管理员--管理广告！ 🤝广告代理可授权给广告商参与修改广告【标题和链接】 ⭐️广告商也可随时查看近期投放渠道（搜索群） ✅设置方法—举例关键词广告 1.点击一🎯广告【投放】营销 2.点击—关键词排名广告 3.点击—管理关键词排名广告 4.点击—设置管理员输入（ID）数字 👋🏻如果要删除 输入 删除管理员 即可 神马搜索机器人 ✅@smss ✅ 神马搜索唯一客服机器人 👉 @smbot ✅️ —— 神马搜索联盟官方团队
👍70❤18🎉12😁10🔥7👻2💩1🤮1
📢 招聘 | 普通程序员 | Python 或 TypeScript 开发 我们正在寻找有经验的程序员，加入我们的开发团队，共同打造下一代高效、稳定的系统服务。 🧑💻 岗位要求： • 有使用 Telegram Bot API 的开发经验，了解机器人命令、消息处理、Webhook 等机制 • 熟悉前端框架 Vue 或 React，能独立完成基本页面构建与交互逻辑（优先 Vue） 🌟 加分项： • 熟练掌握 Python或TypeScript，具备良好的编码习惯与模块化设计能力 • 有实际部署、运维经验（Docker / Linux / PM2 等） • 了解 Web3 / 区块链项目架构优先 • 有良好的远程协作能力，自我驱动力强 💼 工作形式： • 远程优先，时间灵活 • 项目制或长期合作皆可协商 • 你将直接参与从系统架构、功能开发到上线的完整流程 📮 应聘方式…
👍51❤14💯4👻3😇2💩1
📢 神马搜索联盟官方公告 尊敬的各位联盟用户与合作伙伴： 🤖 本机器人是全网名列前茅的核心搜索平台 —— 神马搜索引擎，具备 稳定 ✅ 高效 ⚡ 精准 🎯 的核心优势！ 💼 如有推广项目需求的老板，可随时联系 客服或代理 对接资源，快速开启广告合作！ 📌 为维护联盟良好氛围，特此重申： 1️⃣ 群内严禁任何形式的广告轰炸，尤其是刷屏、图片广告等垃圾信息请自觉清理，违规者将被取消联盟； 2️⃣ 严禁涉及 ⚠️ 政治 / 暴力 / 诈骗 / 色情 等违法违规内容，⛔ 一经发现立即清退并永久拉黑； 3️⃣ 我们致力于打造一个 🔐 安全 · 🌐 专业 · ✨ 纯净 的搜索环境，确保每一位成员都能安心使用。 🤝 让我们携手共进，合作共赢！🚀 —— 神马搜索联盟官方团队
❤9🐳2💩1
📢 神马搜索安全提醒公告 尊敬的神马搜索用户： 近期我们接到多位用户反馈，有不法分子假冒“神马搜索”官方客服，以“关键词到期”“账号异常”等理由，通过私信、虚假网站等方式进行诈骗，严重威胁用户财产安全，并损害我司品牌声誉。 为保障广大用户的权益，神马搜索郑重声明： ✅ 我们唯一的官方客服联系方式为：@smbot ✅ 官方信息发布频道为：@o123456 请您务必提高警惕，谨防诈骗，凡涉及账号、资金、关键词等敏感事项，请第一时间通过上述官方渠道核实。 ⚠️ 温馨提示： • 我们从不主动添加用户私聊 • 不会通过任何非官方链接要求付款或操作 • 对假冒行为将保留追责权利 感谢您的理解与支持！ —— 神马搜索安全中心 📅 发布日期：2025年7月30日
❤7👍4🤮1
⚠️ 谨防诈骗，保护账户资金安全！ 💢 我们不会主动私聊你，请勿相信陌生消息！ 💢 不要点击 来路不明的 文件/链接，谨防病毒和钓鱼攻击！ ✅ 神马搜索唯一客服机器人 👇 @smbot ✅ ⚡ 提高警惕，保护信息资金安全！
❤3👻1💩1
Showing the 11 most recent of 11 posts we hold for @o123456. 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.
Citation-graph rank — 825,576 of 1,189,255entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“🔍【神马搜索】公告🔰” (@o123456), 41,730 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/o123456.
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.