Channel
@sutui6666
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,566subscribers
-6 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003538149845 |
|---|---|
| Type | Channel |
| Username | @sutui6666 |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/sutui6666 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 16:48 | 6,566 | -2 |
| 12 Aug 2026, 12:05 | 6,568 | -4 |
| 11 Aug 2026, 17:31 | 6,572 | first reading |
12 posts held, back to 11 June 2026 — 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 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 12 (11 June 2026 – 10 August 2026) |
| Views total | 25 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 05:35 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 12 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 11 June 2026 to 10 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.
7、AI 智能评论 “推文监控”和“互动推文”新增 AI 智能回复功能。 支持通用 OpenAI-compatible API。 根据目标推文正文批量生成不同回复。 支持自定义提示词、语言、风格、内容变化和最大长度。 AI 失败时可回退默认评论或跳过。 表格会显示推文正文、实际评论内容及发送结果。 两个模块共用 API 地址、API Key 和模型，提示词等策略独立保存。 使用方法：打开“评论配置”，选择“AI 智能回复”，填写 API 信息并设置提示词，测试成功后保存并启动任务。 注意：API Key 以明文保存在本地，调用 AI 服务可能产生费用。图里测试是deepseek接口 8、更新yescaptcha和2captcha插件版本 9、恢复token重提的稳定性
5、新增批量私信功能，支持用户名自动解析、多账号发送、文案与媒体配置及多种发送模式。选择发送账号分组，填写接收用户名并配置文案后即可开始；如需图片或视频，可选择媒体文件夹，系统将随机分配媒体 6、修复了评论配置配置内容保存不持久的问题
4、重构了代理使用逻辑 新增代理池管理，支持代理分组、批量检测、地区识别、失败清理 账号的代理配置修改为从代理池内选择代理分组进行顺序/随机分配
V12.1 1、优化了微软换绑 微软邮箱文件现已支持 ----、竖线、逗号、分号和 Tab 等多种分隔方式 换绑同时支持了imap 和graqh（会自动选择）并且修复了最近很多微软邮箱需要scope参数的问题 新增微软邮箱文件格式选择，支持“授权信息在前”和“Client ID 在前”两种字段顺序 2、优化微软邮箱解锁功能，将原来的两个微软选项合并为“微软（自动）”，操作更加简单 已同时支持了imap 和graqh两种类型的微软邮箱 3、新增选中账号刷新功能，选中账号后可仅刷新当前分组内所选账号的状态，操作更精准高效。
V11.6 1、浏览器养号修复了浏览趋势推文功能会点击grok的bug 2、限流检测优化 修复了检测大批量账号时只能检测一部分的问题，现在无论多少账号都会全部检测完。 检测速度大幅提升，组内互检和分组检测耗时接近。 检测失败的账号会自动换其他账号重试，尽量确保每个账号都有结果。 新增"检测范围"选项：可选择检测组内所有账号、只检测未标记账号，或只检测选中的账号。 开始检测前会弹窗显示预计工作量和耗时，确认后再执行。 3、批量发推 新增设置为ai生成媒体的标志功能 如图所示 4、定时养粉：修复了账号数较少、目标粉丝数较高（如满配互关）时点击执行直接显示"完成"却没有实际关注的问题，现在均可正常达标。
V11.5更新 「定时养粉」功能 — 更新说明 这个功能是做什么的 帮你给一整组账号批量涨粉。组里的账号互相关注,你只要设定"每个账号要涨多少粉、用几天完成",软件就会自动安排,到期让组内每个账号都达到目标粉丝数。操作很简单:设好目标,每天点一下"执行今日任务"即可。 本次重要优化 1. 涨粉节奏更安全,大幅降低被限制的风险 推特对每个账号短时间内的关注次数有限制。本次优化后,软件会把每个账号的关注任务均匀分摊到每一天,确保单个账号每天的关注量始终保持在安全范围内,不会扎堆。万一某天任务量偏大,软件会自动分批、间隔进行,避免触发推特的限制。 2. 掉号也能保证目标达成(重点) 账号难免会有意外——比如中途失效、被冻结、或你手动移走了一些。以前这会导致其他账号涨不够粉。现在软件每次执行时都会自动重新核算:哪些账号还活着、各自还差多少粉,然后用存活的账号把缺口补上。最终,所有还正常的账号都能达到目标粉丝数。(除非存活账号实在太少…
❤1
V11.4更新 1、新增了定时上粉功能 支持同时增加多个分组 指定上粉数和时间 比如给该分组4天上25个粉 2、修复了新用户初次使用时批量发推会报错id初始化失败的bug 老用户也建议更新 避免出现同样问题 3、账号管理页面和批量发推页面检测限流功能新增指定用于检测的分组的功能 不再使用默认分组进行检测
今天又出现了一个账号被人操控的案例 也是飞机号被人控制了 把真正的客服归档了 然后和虚假账号进行了交易 后续排查中客户说自己修改了2步验证码 并且没发现有其他设备登录 手机使用的苹果并且没使用第三方汉化包 如果手机没问题的话 那就不能排除电脑里有如远控一类的木马存在 这类远控会摸清你的生活习惯 专挑你不在线的时候调整你的飞机 比如归档一些聊天然后伪造新的假聊天等 等你再次上线不仔细研究不会发现任何异常 所以除了之前说的那些防范措施外 各位老板还是要注意一下自己的电脑有没有什么异常 比如鼠标自己在动 有异常的流量消耗 莫名卡顿 cpu占用很高 飞机账号自己开启了自动删除聊天记录等 为了避免这类事情再次发生 在此声明: 本工作室以后不会再直接发送任何收款方式给各位老板 如需与我进行交易 以后无论是续费还是新购买都请通过网页进行付款 地址如下: https://qsacc.com/buy/1 支持支付宝 微信 usdt-trc20 之…
请务必仔细阅读 1、如图所示 建议所有客户自行检查一次 确保账号安全 近期身边有人发生了这样的事情 深感痛心 现在钱都不好挣 所以老板们一定要对自己的资金负责 平时多进行检查 不要让小人钻了这种空子 2、不要通过在tg里搜索客服qsgzs999 来找客服 假冒账号太多 3、任何事情需要联系客服 只有两种途径 第一 进入速推官网 sutuix.com 点击联系客服来拉起与真实客服的聊天 第二 速推软件里设置页面有联系客服的按钮同样可以拉起与真实客服的聊天 4、当您想购买产品时 转账发生前 请一定进入我们的官网 sutuix.com 点击联系客服 看看拉起来的聊天是否和你刚刚聊的是同一个聊天 如果您发现官网拉起的聊天和你刚刚聊的是两个聊天 那么恭喜你 你刚刚聊的是一个骗子 骗子正在使用高仿账号和您聊天 你在转账发生前找到了真实的客服 避免了损失 拯救了你的资金 5、trc20方式付款前 首先进入我们的官网 sutuix.com 点击…
V11.0更新 1、修复了采集页面win10白色背景的bug 2、近期部分节点卡顿频繁 使用自备视频的情况下可能速度很慢 现在自动压缩视频可能有些许提升 3、从此版本后无需再依赖速推更新程序进行更新 已内置更新程序 软件启动时会自检 也可以从设置里的检查更新来实现更新 但是升级到11版本还是需要使用速推更新程序 升级后就不要需要这个独立程序了 请尽快更新到此版本
win10的采集页面白色背景bug 下版本再修复 token重提已经恢复了
V10.9 1、优化了软件启动速度和发推启动速度 增加稳定性 2、批量发推支持了四个互动分别指定数量进行操作 点击按钮进行模式切换 3、新增采集页面 支持批量指定关键词采集推文链接 推文作者 4、新增互fo助手 可以全自动进行指定关键词关注 回关 需要先手动对相关关键词的账号进行关注后再使用此功能
Showing the 12 most recent of 12 posts we hold for @sutui6666. 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 — 215,584 of 1,480,688entries 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 17 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“速推官方频道-专业营销软件” (@sutui6666), 6,566 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/sutui6666.
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.