三角洲行动物品ID与名称
👍1
Channel
@WoShiZB
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
268subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002196207150 |
|---|---|
| Type | Channel |
| Username | @WoShiZB |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/WoShiZB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 09:05 | 268 | +1 |
| 8 Aug 2026, 09:00 | 267 | no change |
| 7 Aug 2026, 12:33 | 267 | first reading |
14 posts held, back to 25 July 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 pageof 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. It is computed over the 9 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 14 (25 July 2026 – 7 August 2026) |
| Views total | 3,230 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:00 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.
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.
24 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 45.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 11 | 45.8% | |
| ❤ | 5 | 20.8% | |
| 🤡 | 5 | 20.8% | |
| 👎 | 3 | 12.5% |
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 9 of the 14 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 24reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 25 July 2026 to 7 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.
三角洲行动物品ID与名称
👍1
TG协议工具箱 1. 一键批量登录,发送验证码完成登录,支持2FA,随机设备伪装(WitchMagic品牌),输出session文件与JSON数据包 2. 会话转移换设备,旧session在新设备登录,自动监听777000获取验证码,支持销毁旧session 3. 所罗门极速Session生成器,快速创建.session文件 4. API反向做号,通过外部API获取验证码和密码,批量自动化登录生成session 5. 批量加群退群,所有账号一键加入或退出指定群组/频道 6. 批量群发消息,所有账号向目标发送消息,支持重复发送和媒体附件 7. 批量点赞,所有账号对消息做出表情反应,支持随机表情和多目标 8. 批量转发消息,所有账号将指定消息转发到目标群组 9. 批量启动机器人,所有账号对指定机器人发送/start命令 10. 批量修改资料,支持昵称、用户名、简介、姓名、头像的统一下发 11. 批量隐私设置,7种隐私项一键锁定为仅…
👍2
JS三角洲Pak解包工具 全部开源 作者JS 搬运带作者 windows版本
Lua源码 作者js
👍2
如何解除 苹果IOS 敏感内容 限制? 方法一: 🔘web网页版登录链接 https://web.telegram.org/k/ 浏览器打开官网 登陆账号 (验证码 在app内) 成功登入Telegram 网页版后,点选左上角“选单”按钮 ➊点击左上角的 Settings ➋点击 Privacy and Security ➌找到 Sensitive content ➍把 Disable filtering 前面的选项勾上 √ ➎重启 iOS 客户端即可 方法二: 🔘电脑端操作方法:下载Telegram Desktop最新版,windows电脑端,官方下载链接: https://desktop.telegram.org ✔️操作: 登录Telegram PC客户端后 ➊点击「Settings/设置」 ➋点击「Privacy and Security/隐私与安全」 ➌找到「Sensitive content/敏感内容」…
(首发)将文件中的指令复制发送Deepseek,Deepseek回答 ok 代表已经成功,然后发送(取消Latex格式回答)接下来的对话将无限制,但也不要有特别敏感的提示词,可以用谐音词,比喻来形容,对话不会受到限制。
APK 加固工具 免费使用本地版本 防 AI 脱壳 防脱壳网站脱壳 动态不知道自己测试 勿倒卖免费使用 不建议大体积应用加固 纯本地无任何远程 https://pan.baidu.com/s/1yF5GMduehPUVo3U0FsGkpg?pwd=6666
Video, posted without a caption
🤡5
用 iptables 屏蔽 35+ 个腾讯反作弊/遥测/广告服务器域名,封锁 HTTPS(443) 端口,只放行 HTTP(80) 和游戏端口(17500),使反作弊数据无法上报 逐层删除游戏缓存、日志、TSS/TPNS/Ano 反作弊数据、PCDN 上报文件、UE4 资源缓存,保留核心游戏文件以维持运行 篡改设备序列号,删除 SSAID 匿名标识,在 rmnet_data0 接口添加随机 IP,清零内核连接追踪参数,使设备指纹彻底改变,绕过封禁 具有过上号人脸 以及上号数据变化小黑屋问题 请理性看待 放data目录下给777权限执行 如果更改ip出现了NO IP 之类的以及去wifi那里改ip 数据流量的话开飞行模式一分钟 建议游戏大厅启动这个清理脚本 BUG/反馈 @Ledttkxbot
❤2👍2
设备信息查看器 用于查看设备信息 例如机型 cpu等等 可用于看伪装有没有生效
👍2
MOSE加密 ✓ 支持ELF可执行文件加固 ✓支持 Shell脚本源码加固 ✓ 支持(.so)文件加固 ✓ 完整性校验与防篡改机制 官方频道 https://t.me/MoseCheat 卡密随便输 永久公益
❤2
File, posted without a caption
Showing the 12 most recent of 14 posts we hold for @WoShiZB. 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 — 403,084 of 1,336,469entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“@WoShiZB” (@WoShiZB), 268 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/WoShiZB.
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.