极点云检 · ObeliskScan - 让账号检测更简单 【主程序】最新版本:v1.2.3 新增: ✅ 代理可按每条账号自动匹配地区:代理用户名里写 {country}、{city} 等占位,账号表对应列带上国家/城市即可。 ✅ 账号导入支持五列:账号、密码、国家、网络编号、城市(冒号或 ---- 分隔),与代理占位联动。 优化: ✅ 代理与导入说明弹窗已重写;开始检测前会检查占位与账号信息是否匹配,缺信息时提前提示。 ✅ 未使用占位的固定代理、原有两列/三列导入格式不变。 📌【怎么用】 1)账号文件按行写:[email protected]:密码:ID:AS6739:jakarta(五列,后三列按需填写) 2)代理按代理商格式填写,在用户名需要变化处写 {country}、{city} 等 3)导入账号 → 填代理 → 测试连通性(可选)→ 开始检测 软件内代理区、导入弹窗旁点 ? 可看完整说明与示例。 …

Channel
极点云检 · ObeliskScan | Twitter(x) / Insgram 账号检测/强改
@ObeliskScan
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,310subscribers
+1,149 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003975262700 |
|---|---|
| Type | Channel |
| Username | @ObeliskScan |
| Created | Between 1 April 2026 and 7 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/ObeliskScan |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 10:20 | 1,310 | -23 |
| 29 Sept 2026, 19:19 | 1,333 | +1,147 |
| 15 Sept 2026, 06:41 | 186 | +5 |
| 8 Sept 2026, 14:39 | 181 | +7 |
| 30 Aug 2026, 20:25 | 174 | +14 |
| 23 Aug 2026, 13:53 | 160 | -1 |
| 8 Aug 2026, 17:01 | 161 | no change |
| 7 Aug 2026, 19:33 | 161 | first reading |
Engagement
20 posts held, back to 7 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 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
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 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 1 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 7 June 2026 to 6 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
极点云检 · ObeliskScan - 让账号检测更简单 【官方说明】关于近期「出号变少」的反馈 我们已核对:推特、Instagram 、facebook检测的的核心逻辑未做调整,近期更新也未改动核心检测逻辑。 同一套软件,不同批次、不同线路,结果会有正常波动——这往往与导入数据本身、代理质量与匹配度有关,并不等同于「软件变差了」。 建议更新主程序与对应检测插件后,换一批干净样本、换稳定代理小量试跑对比;仍有疑问可私信 @yaseceo @okgeceo 协助排查。 极点云检,只为极致效率。
这两天休息有事留言即可 问题反馈留言 看到会回复⚡️ 休息是为了更好的效率💡
极点云检 · ObeliskScan - 让账号检测更简单 【主程序】最新版本:v1.2.2 优化: ✅ 工作台导入后即可显示账号总数,扩展信息勾选与结果列展示更统一。 ✅ 日志标签与平台统计展示若干优化。 修复: ✅ 大批量检测结果实时展示与断点续跑稳定性多项修复。 ✅ 长时间大批量运行下的程序稳定性若干修复。 【插件更新】😎Twitter (X) 登录检测 · v1.0.2 修复: ✅ 推特大批量高并发检测时偶发闪退问题若干修复。 【插件更新】😎Instagram 登录检测 · v1.0.1 修复: ✅ Instagram 大批量高并发检测时偶发闪退问题若干修复。 【插件更新】😎Instagram 2FA 管理 · v1.0.4 修复: ✅ Instagram 账号维护流程在高并发场景下的稳定性若干修复。 📍如果更新了最新的插件必须更新主程序 更新方式: 自动更新:已有旧版本的用户,启动软件即可触发…
🤩所有插件维护工作已全部完成。客户端版本为1.2.0至1.2.1的用户,请务必执行卸载并重新安装插件的操作。同时,建议您尽快将客户端升级至1.2.1版本,以确保获得最佳体验。
🚀 极点云检 · ObeliskScan - 让账号检测更简单 🚀 【主程序】最新版本:v1.2.1 新增: ✅ 登录页与标题栏可直接发现新版本;未登录时也可在登录页检查并下载更新。 优化: ✅ 导出目录支持自定义,默认保存至「文档」;首次导出会提示确认保存位置。 ✅ 程序本地数据存放位置优化,从旧版本升级后会自动迁移 修复: ✅ 登录与人机验证体验若干修复。 【插件】 Instagram 2FA 管理 · v1.0.1 优化: ✅ 若干流程稳定性与兼容性提升。✅ 更新方式: 主程序:已有旧版本的用户,启动软件即可触发自动更新(须为 Windows 正式版且已登录)。新用户或无法自动更新的用户,请下载本消息附件中的主程序安装包。 插件:打开软件 →「插件」页 → 找到「Instagram 2FA管理」→ 点击更新。 极点云检,只为极致效率。 购买/续费请联系:@yaseceo @okgeceo
⛓ 打开 ObeliskScan 只有黑屏? 如果你看到的是「窗口一片黑、没有按钮文字,但程序没有闪退」,通常不是软件坏了。 ✅ 常见原因 电脑缺少运行所需组件,界面暂时显示不出来。 ✅ 怎么处理 1️⃣ 若软件有弹窗,点「打开官方下载」安装组件 2️⃣ 安装完成后关闭软件 3️⃣ 再重新打开 ObeliskScan 💡 按上面步骤安装即可。 ⬅️ 也可以 [点击下载] 在运行环境中安装. 仍无法解决请联系客服 🙏
🚀 ObeliskScan V1.2.0 | 极点云检 发布 🚀 Status: Live | Version: 1.2.0 | Target: Multi-Platform Automation ————————————————————————————————— 号商全链路生产力工具,这次,我们定义暴力流作业。 🟢 【核心重磅】2FA 暴力强改模块 (Instagram 首发) • 无视原验证 强行绕过目标账户原有的所有安全盾,直接切入核心修改流程。 • 遇到原账号验证,也能继续推进。 换绑手机、绑定邮箱、修改密码、解除关联—— 在新客户端里一站完成。 (💡 Facebook 2FA 强改模块已在内测阶段,即将轰炸上线!) 【架构重组】全新客户端 · 顶级跑号体验 🟢 双色原生 UI: 独家支持【深黑 / 纯白】高质感双模界面,大批量挂机进度可视化,视觉极其舒适。 🟢 底层架构重构: 核心引擎重写,并发性能飙…
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @ObeliskScan. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“极点云检 · ObeliskScan | Twitter(x) / Insgram 账号检测/强改” (@ObeliskScan), 1,310 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/ObeliskScan.
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.