Posted without readable text
❤1

Channel
@weiti
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
20,437subscribers
-7,000 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001198472546 |
|---|---|
| Type | Channel |
| Username | @weiti |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/weiti |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 20:56 | 20,437 | -4,967 |
| 17 Sept 2026, 16:16 | 25,404 | -896 |
| 15 Sept 2026, 13:58 | 26,300 | -381 |
| 13 Sept 2026, 23:19 | 26,681 | -122 |
| 12 Sept 2026, 03:56 | 26,803 | -217 |
| 9 Sept 2026, 22:00 | 27,020 | -213 |
| 6 Sept 2026, 16:19 | 27,233 | -109 |
| 4 Sept 2026, 03:18 | 27,342 | -55 |
| 2 Sept 2026, 18:18 | 27,397 | -40 |
| 1 Sept 2026, 19:28 | 27,437 | no change |
| 1 Sept 2026, 16:46 | 27,437 | first reading |
53 posts held, back to 28 August 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 7 pages of 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 16 of 49 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 26 September 2026 |
|---|---|
| Posts held | 53 (28 August 2026 – 26 September 2026) |
| Views total | 24,493 |
| Reactions total | 38 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 11:03 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.
39 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 56.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 22 | 56.4% | |
| 🎉 | 7 | 17.9% | |
| 💯 | 5 | 12.8% | |
| 🤩 | 5 | 12.8% |
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 17 of the 53 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 53 most recent posts we hold, published 28 August 2026 to 26 September 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.
Posted without readable text
❤1
国庆节假日业务通知 持续更新 🪱🐛🦋 柜台及无盲流水系列 建设银行、农业银行 27号最后一车 29日全部回完 农业柜台流水卡反 10月8日开工,10.7日可报单 邮政柜台流水卡反 10月8日开工,10.7日可报单 工商柜台流水卡反 正常营业 ,10月1-4日放假 中国柜台流水卡反 正常营业,9月28日开工 广发柜台卡反 正常营业,9月28日开工 公户无盲流水 10月8日发车,可预收单 微提好友提取 正常营业 9月28日 节前最后一批 支付宝微信流水 正常营业 9月28日 节前最后一批 手机轨迹 正常营业 警务通人脸 正常营业 立案详情 正常营业 9月28日出单 公网名下卡 正常营业 9月28日出单 卡反预留系列 正常营业 不放假 出入境记录 正常营业 不放假 社保文档 正常营业 不放假 名下常用号 正常营业 不放假
❤1
警务通 人脸识别 🐤🐣🦅 提供照片:默认出最高相似度 提供照片+名字:对上默认出 提供照片+名字+地区:对上一条默认出 提供照片+名字+地区+年龄:对上一条默认出 有备注不对可以不出 不出不收费 精准人脸点射 美颜 照片不清晰 可能会识别错误 出单不扯皮 接受了报 当天隔天回 批量来谈优势
开卡专线流水源头收 🦉🦇🐝 今晚12点发车 国庆节前回单 本车 只有利息不收费 🦕🦕🦕 对私开卡 🐤🐧🐒🦅 🔥 仅限私户 不限银行 空不收 其他都收 保真不保漏 对私公职人员敏感收费扣单,报单自行检查
全部回完 新单中秋节后出 9月28日 立案详情 持续稳定 🦉🦇🐝 注意 没有标记(逃) 就是到案 🐦🐒🐒🦅 周一出单 注意 同案人数出全部 🦕 文档拍照 空收一半 案件号 案件时间 案件详情 立案单位
❤1
公户全部回完 新单可以排队 源头公户流水 新车节后10月8日发 无盲公户流水发车(10月8日发车) 源头公户,有量有价 支持所有银行 小额贷🦕 一月 🐣🦆🐒🦅 二月🐥🐒🐒🦅 六月 🐥🐣🐒🦅 一年🪿🐒🐒🦅 两年 🦆🐒🐒🦅 三年🦆🐣🐒🦅 开卡 🐦⬛️🐒🐒🦅 空不收 其他都收 保真不保漏 1.银行有上限7000条数 2.对公国企敏感不要,私自改名发现扣单不接受扯皮 3.小额贷只收单月,上限1000条不扯皮
手机轨迹系列 🦉🦇🐝 开普勒手机轨迹版 出全部 🦆🐒🦅 一年内所有轨迹 满5条出单收费 免单 回单时间 : 当天/ 隔天回单 保真不保漏 开普勒版本因设备识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑,所以个别位置会有误导识别现象,产生经纬跳跃 结果以总体较多出现的位置为准。 经纬度替换位置 可以用这个链接替换: https://api.map.baidu.com/lbsapi/getpoint/index.html?qq-pf-to=pcqq.c2c
🔥🤑报单前可以看看马儿频道🤑🔥 🐙 源头微信好友提取带备注 稳定 🐙 源头微信公众号用户提取 稳定 🐙 微信支付宝流水反炸版本 开收 🐙 微信流水提取带对手ID号 20号 🤭 公网微反/QQ收款码反查 稳定 😔 天花板卡反预留一条龙秒 在线秒 😎 源头十四大柜台流水系列 稳定 🫤 刑侦无盲三天回银行流水 稳定 😭 各柜台名下银行卡及带鱼 稳定 👮 开同人轨飞火单开大关联 稳定 📱 机主法人地址网逃各系列 ✔️ Tg官方实名认证服务 已验证 👮 个人信息 / 个人资产 手机轨迹 通话记录 手机定位 刑侦全户 婚姻记录 学籍学历 名下护照 社保文档 盖章社保 名下车辆 反诈边控 刑侦地址 公网名下卡 出入境记录 🏃 跑路排行榜各种套路大神 🤖 最顺手的核验机器人 🤖 更好用的记账机器人 自助下单看到都会安排 更新至24号 💁联系马儿 🤖双向机器…
❤2
手机轨迹系列 🦉🦇🐝 开普勒手机轨迹版 出全部 🦆🐒🦅 一年内所有轨迹 满5条出单收费 免单 回单时间 : 当天/ 隔天回单 保真不保漏 开普勒版本因设备识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑,所以个别位置会有误导识别现象,产生经纬跳跃 结果以总体较多出现的位置为准。 经纬度替换位置 可以用这个链接替换: https://api.map.baidu.com/lbsapi/getpoint/index.html?qq-pf-to=pcqq.c2c
公户回单 周四新车 继续发 无盲公户流水发车(周四9.24日 晚发车) 全网唯一,有量有价 支持所有银行 小额贷🦕 一月 🐣🦆🐒🦅 二月🐥🐒🐒🦅 六月 🐥🐣🐒🦅 一年🪿🐒🐒🦅 两年 🦆🐒🐒🦅 三年🦆🐣🐒🦅 开卡 🐦⬛️🐒🐒🦅 建设银行 农业银行 半年 🐣🦆🐒🦅 一年 🐥🐦🐒🦅 两年 🐥🦆🐒🦅 三年 🪿🐦🐒🦅 开卡 🦆🐒🐒🦅 🔥 仅限公户 开卡至今10年 空不收 其他都收 保真不保漏 1.部分银行有上限8000条数 2.对私公职人员敏感收费扣单,报单自行检查 3.对公国企敏感不要,私自改名发现扣单不接受扯
❤1
全部回完 长期稳定 立案详情 持续稳定 🦉🦇🐝 老条回归 周每天晚上出单 注意 没有标记(逃) 就是到案 🐦🐒🐒🦅 周一出单 注意 同案人数出全部 🦕 文档拍照 空收一半 案件号 案件时间 案件详情 立案单位
无盲公户流水发车(9.21日 晚发车) 全网唯一,有量有价 支持所有银行 小额贷🦕 一月 🐣🦆🐒🦅 二月🐥🐒🐒🦅 六月 🐥🐣🐒🦅 一年🪿🐒🐒🦅 两年 🦆🐒🐒🦅 三年🦆🐣🐒🦅 开卡 🐦⬛️🐒🐒🦅 建设银行 农业银行 半年 🐣🦆🐒🦅 一年 🐥🐦🐒🦅 两年 🐥🦆🐒🦅 三年 🪿🐦🐒🦅 开卡 🦆🐒🐒🦅 🔥 仅限公户 开卡至今10年 空不收 其他都收 保真不保漏 1.部分银行有上限8000条数 2.对私公职人员敏感收费扣单,报单自行检查 3.对公国企敏感不要,私自改名发现扣单不接受扯
Showing the 12 most recent of 53 posts we hold for @weiti. 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.
@weiti edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“内马尔源头业务通知-关注看价格” (@weiti), 20,437 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/weiti.
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.