Telegram RegisterThe public register of Telegram

Channel

SOSO搜搜官方频道📢

@sosooo

2 usernames

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

179,877subscribers

+13 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001364879469
TypeChannel
Usernames@sosooo @sosopindao
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/sosooo

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Growth

179,774179,892179,8336 August 2026 — 179,864 subscribers6 August 2026 — 179,817 subscribers7 August 2026 — 179,829 subscribers8 August 2026 — 179,806 subscribers9 August 2026 — 179,774 subscribers9 August 2026 — 179,785 subscribers10 August 2026 — 179,884 subscribers10 August 2026 — 179,892 subscribers10 August 2026 — 179,880 subscribers11 August 2026 — 179,874 subscribers11 August 2026 — 179,876 subscribers12 August 2026 — 179,877 subscribers179,8776 August 202612 August 2026
12 measurements spanning 6 days, net +13. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 179,756–179,910 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:13179,877+1
11 Aug 2026, 23:52179,876+2
11 Aug 2026, 22:42179,874-6
10 Aug 2026, 23:47179,880-12
10 Aug 2026, 21:54179,892+8
10 Aug 2026, 01:03179,884+99
9 Aug 2026, 21:47179,785+11
9 Aug 2026, 20:52179,774-32
8 Aug 2026, 19:57179,806-23
7 Aug 2026, 17:16179,829+12
6 Aug 2026, 16:04179,817-47
6 Aug 2026, 12:47179,864first reading

Engagement

24 posts held, back to 18 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.46%
avg views ÷ 179,877 subscribers
Avg views / post
15,200
15 posts measured
Reaction rate
5.55%
reactions ÷ views · ER floor
Posts in window
16
of 24 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held24 (18 June 20258 August 2026)
Views total228,230
Reactions total12,676
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 18:02 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

17,225 reactions across 22 posts, in 30 distinct kinds. The most used accounts for 31.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥5,39831.3%
2,46314.3%
🤣2,36613.7%
👍1,3357.75%
🥰8985.21%
🔥8845.13%
🤩8765.09%
😍8705.05%
💯8454.91%
🎉8404.88%
690.401%
💔580.337%
🌭370.215%
😱310.18%
😭300.174%
👏290.168%
👌250.145%
210.122%
😐210.122%
😨210.122%
10 further kinds1080.627%

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 22 of the 24 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 17,225reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 18 June 2025 to 8 August 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.

Recent posts

8 Aug 2026, 18:59 UTC≈8,220 views18 reactionsread 12 August 2026
Forwarded from @BotGramCN

🫡 @Botgram 商城现已支持支付宝付款 商城新增支付宝人民币支付通道,买家下单后可直接使用支付宝完成付款,无需准备 USDT,购买会员群、付费内容、卡密及定制服务更加方便。 目前支持: • 🫡支付宝:单笔 ¥1–1000 • 🫡支付宝(备用):单笔 ¥5–500 • 🏦OKPay USDT:继续正常支持 支付宝收款需由店主提交资料并通过平台审核,审核通过后即可自动出现在商城付款页面。 打开 Botgram,进入「商城 → 支付宝收款」即可申请开通。

18

6 Aug 2026, 23:02 UTC≈10,900 views45 reactionsread 12 August 2026

📢 SOSO 开始治理频道换壳与买卖 近期发现,有人购买已经收录的频道,修改频道名字后,继续继承原来的搜索排名,用旧频道的收录资格给新内容卡位。 这不仅影响正常运营的频道主,也会降低搜索结果的可信度。 即日起,已收录频道一旦修改频道名字,原收录状态和搜索排名将自动失效,必须按新的频道名字和内容重新提交审核。 收录资格不能买卖,也不能继承。让认真运营的频道获得应有的曝光。

👍346❤‍🔥4👏1

6 Aug 2026, 16:56 UTC≈9,410 views15 reactionsread 12 August 2026
Forwarded from @BotGramCNPhoto

📣 @Botgram 双向机器人现已支持「团队话题收件箱」 以前,访客消息主要由 Bot 主人在私聊中接收和回复。现在,你可以把客服 Bot 接入 Telegram 群组,并使用“话题”同时处理多位访客。 👤 一位访客,一个独立话题 每位访客都会进入自己的客服话题,聊天记录互不混淆。客服人员直接在对应话题发送文字、图片、视频、文件或语音,即可回复访客,无需反复引用消息。 👥 更适合多人客服 Bot 主人、群组管理员以及被添加的客服人员,可以在同一个群组内协作处理咨询。多位访客同时发消息,也能快速找到对应会话。 ⚙️ 开启方法 1. 创建一个私密 Telegram 群组 2. 开启群组的“话题”功能 3. 将客服 Bot 添加为管理员,并授予“管理话题”权限 4. 在群组内点击“检查并启用” 也可以打开客服 Bot,点击顶部的「收件方式」,查看当前模式并完成设置。 🔄 两种模式随时切换 - 个人收件箱:创建

10👍5

6 Aug 2026, 13:18 UTC≈12,100 views5,606 reactionsread 12 August 2026
Forwarded from @BotGramCN

BotGram 中文教程索引|从这里开始 按你现在想完成的任务,点击下方按钮直达对应教程: • 第一次使用:先创建你的第一个 Telegram Bot • 做付费业务:开商城、卖视频、卖会员群 • 做私信客服:创建双向机器人/双向转发机器人 • 做免费资源增长:创建网盘机器人/资源发放 Bot BotGram 永久免费创建和运营 Telegram 业务 Bot。教程会按照产品当前界面持续更新,原链接保持不变。 遇到 Botgram 平台 Bug 或想提产品建议:@wumadebot #BotGram教程 #TelegramBot #中文教程

👍654❤‍🔥635🥰635🤩631🎉619😍616💯607603

3 Aug 2026, 14:42 UTC≈11,700 views35 reactionsread 12 August 2026
Forwarded from @BotGramCN

🚀 @Botgram 功能更新 本次更新带来了多项实用功能: 网盘机器人支持多管理员 可邀请多人共同管理机器人,内容发布和日常运营更加方便。 支持强制订阅多个频道/群组 可同时设置多个必订阅频道或群组,用户完成全部订阅后才能领取资源。 商城机器人支持出售视频资源 现在可以直接上架和销售视频内容,满足付费内容、会员资源等运营需求。 支持主动停用/删除机器人 不再使用的机器人,可以直接在管理后台停用或删除,机器人列表更加清晰。 支持导入已有 Telegram 机器人 无需重新创建,直接发送 Bot Token,或转发 BotFather 中包含 Token 的消息,即可将旧机器人接入 Botgram。 🫡 商城机器人即将支持支付宝付款 届时买家可直接通过支付宝完成付款,交易流程更加方便。敬请期待! 立即进入 Botgram 体验新功能 👇 @botgram

👍2012🔥2❤‍🔥1

31 Jul 2026, 21:28 UTC≈17,200 views92 reactionsread 12 August 2026
Photo

📌 关于评论区的恶意抹黑,顺便介绍一下最近在做什么 近期,SOSO升级了风控系统,一批利用虚假流量套取收益的账号被拦截。随后,官方频道评论区便出现了“SOSO骗钱”“平台跑路”等恶意抹黑。 这几条评论倒是提醒了我们:最近一直忙着做产品,好像很久没有介绍自己了。 最近SOSO上线了群管功能。有群的朋友可以顺手试试,反广告、入群验证、群增长都能一起管,争取让大家的群里少养几个机器人。 集团最近还推出了 @botgram,不用写代码,就能创建自己的双向客服、网盘发货和会员商城Bot。收消息、发资源、卖会员,都可以直接在Telegram里完成。 想玩游戏的朋友也可以看看 @okgame:入驻平台先缴押金,游戏统一接入 @okpay,把玩家权益放在前面——放心玩,才好玩。 当然,这些只是集团部分业务。其他产品和业务线真要全部展开,这条公告可能就要写成集团产品手册了。 SOSO目前连接7000万+用户,并获得20万+群/频道的

59👍18💔4👏3🤔3🤣32

30 Jul 2026, 14:23 UTC≈22,000 views6,633 reactionsread 12 August 2026
Photo

SOSO 全新 Logo 即将启用。 新的 Logo,不只是一次视觉升级。 它也代表着 SOSO 从搜索机器人,成长为连接 Telegram 中文生态的平台。 未来,我们会继续做好搜索、做好流量、做好群频道经营。 连接 Telegram 中文生态,让每一个社区都能被发现。 🚀

❤‍🔥4,740👍271240🔥236🤩235😍233💯229🎉221

29 Jul 2026, 11:24 UTC≈14,500 views39 reactionsread 12 August 2026
Photo

🎬 视频搜索升级 现在支持按近3天、近7天、近30天筛选,新发布的视频更容易找到。

20👍10❤‍🔥3💔3💯3

28 Jul 2026, 11:43 UTC≈15,600 views38 reactionsread 12 August 2026

【SOSO 今日更新】 群组置顶广告和品牌广告升级啦: 1. 群组收益加成上线 开启搜索经营的群,只要当天置顶广告成功发出并置顶,当天群搜索收益自动额外增加 30%。 2. 置顶广告内容更好看 群组置顶广告现在可以直接使用更自然的广告文本,支持保留自定义emoji、加粗、链接等 Telegram 原生效果,不再局限于简单标题和链接。 3. 广告按钮更醒目 群组置顶广告、品牌广告的按钮都支持自定义颜色和自定义 Emoji 图标,展示效果更像 Telegram 原生按钮,更容易被用户看到和点击。 这次更新重点是: 让群主收益更高,让广告内容更好看,也让广告点击更明显。

19👍17😭2

27 Jul 2026, 13:51 UTC≈15,800 views21 reactionsread 12 August 2026

@botgram 资源发放(网盘)机器人小功能更新 现在,资源领取又多了一个更顺手的方式:群组口令领取。 频道主可以在频道里直接告诉大家口令,然后让用户去评论区或指定群组发送口令。用户一发,机器人就会回复一个专属领取按钮,点一下就能进入私聊领取资源。 > 用户不用翻链接、不用问管理员, > 在群里发出口令,就能拿到自己的领取入口。 用户体验是这样的: 1. 在群组或评论区发送领取口令 2. 机器人回复一个专属领取按钮 3. 点击按钮进入机器人私聊 4. 按提示领取对应资源 几个贴心细节: - 专属链接只对发送口令的人有效 - 其他人点击这个按钮也无法领取 - 群内按钮消息会在 3 分钟后自动删除 - 资源仍然只在私聊中发放,不会刷屏群聊 这个小更新特别适合频道评论区、验证群、资料领取群使用。 频道主可以把「看完频道内容 → 去评论区发口令 → 加群互动 → 私聊领取资源」串成一个更自然的流量闭环。

14👍6😱1

27 Jul 2026, 09:19 UTC≈12,400 views28 reactionsread 12 August 2026

📢 SOSO 已完成大规模收录治理 过去几天,SOSO 已下架超过 50% 不再持续接入、维护异常、内容低质或疑似批量运营的群组/频道。 搜索流量池正在变得更干净,剩余流量也会更加集中。 如果你是认真运营的群主或频道主,现在就是接入 SOSO、抢占搜索流量的窗口期。 请尽快完成: ✅ 把 SOSO 设为管理员 ✅ 提交群组/频道收录 ✅ 完成 3 天观察期 ✅ 审核通过后获得搜索曝光 SOSO 会继续清理低质和异常运营的群组/频道,把流量留给真正值得被看见的内容。

👍2341

Showing the 12 most recent of 24 posts we hold for @sosooo. 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

Citation-graph rank — 334,030 of 1,151,006entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 registered channels — 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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“SOSO搜搜官方频道📢” (@sosooo), 179,877 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sosooo.

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.