安徽房产降降价吧 没单子 机器人出8U名下所有 @fangchanahbot 人工出 5U 名下所有 我在就秒 不秒不要钱 千单都能出 @xiaozjc

Channel
肖教主 通知@xiongsheng
@xiongsheng
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
5,140subscribers
+92 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1004290814565 |
|---|---|
| Type | Channel |
| Usernames | @xiaojiaozhutz @xiongsheng |
| Created | 22 August 2026 — measured — dated from the channel’s first post |
| First recorded | 24 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/xiongsheng |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 |
|---|---|---|
| 16 Sept 2026, 23:38 | 5,140 | +2 |
| 15 Sept 2026, 14:18 | 5,138 | +5 |
| 13 Sept 2026, 00:58 | 5,133 | +2 |
| 11 Sept 2026, 21:16 | 5,131 | +7 |
| 9 Sept 2026, 02:36 | 5,124 | +3 |
| 7 Sept 2026, 20:59 | 5,121 | +20 |
| 3 Sept 2026, 22:39 | 5,101 | +4 |
| 2 Sept 2026, 10:13 | 5,097 | +10 |
| 31 Aug 2026, 14:02 | 5,087 | +4 |
| 30 Aug 2026, 08:25 | 5,083 | +3 |
| 30 Aug 2026, 03:15 | 5,080 | no change |
| 30 Aug 2026, 03:00 | 5,080 | +10 |
| 28 Aug 2026, 05:03 | 5,070 | +19 |
| 25 Aug 2026, 00:15 | 5,051 | +3 |
| 24 Aug 2026, 00:45 | 5,048 | first reading |
Engagement
23 posts held, back to 22 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 2 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.87%
- avg views ÷ 5,140 subscribers
- Avg views / post
- 147
- 15 posts measured
- Reaction rate
- 0.628%
- reactions ÷ views · ER floor
- Posts in window
- 18
- of 23 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. It is computed over the 4 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 23 (22 August 2026 – 30 August 2026) |
| Views total | 2,209 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 03:15 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
6 reactions across 6 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 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 6 of the 23 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 22 August 2026 to 30 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
美团点餐+美团订房 😉😉😉 老渠道回归 美团内部工号直出 无遗漏 提供手机号出美团最新一页的点餐记录以及订房记录 注:点餐只有详情 没有收货地址 加钱可以指定日期或出全部 渠道在线就秒 @xiaojzc
新业务!源头业务! 抖音强登😉😉😉抖音强登😉😉😉 抖音强登😉😉😉抖音强登😉😉😉 录屏回单购物地址 还有银行卡号 还有手机号等 全程录屏回!保真 当天/隔天回单 提供名字 身份证号头就行 @xiaojzc
❤1
Channel name was changed to «肖教主 通知@xiongsheng»
浙江全省名下所有😉😉😉 浙江全省名下所有😉😉😉 有量的老板还是继续来发量就可以了 全省!保真 市场没几个能做的 我这个价格也是独一无二 @xiaojzc
手机轨迹 😉😉😉手机轨迹😉😉😉 手机轨迹😉😉😉手机轨迹😉😉😉 定位链接轨迹 带图定位 @xiaojzc
File, posted without a caption
车小档开 车小档😉😉😉车小档😉😉😉 车小档😉😉😉车小档😉😉😉 车小档 实时数据!回文字 保真 @xiaojzc
公网名下卡 三合一版本 😉😉😉 公网名下卡 三合一版本😉😉😉 公网名下卡 三合一版本带名下公司 名下etc车辆当天隔天稳定回单可以备注一张可以不出/可以排除已知卡保真不保漏 同行代理来拿优势只出储蓄卡 不出信用卡注销异常冻结都不出 过验证的卡才算 联系 @xiaojzc
❤1
美饿一体😉😉😉😉美饿一体😉😉😉😉 美饿一体😉😉😉😉美饿一体😉😉😉😉 美团饿了么一体 保真 带时间 有单来报 @xiaojzc
独家人行征信 😉😉😉😉 板子不发频道 需要看板子私我 非便宜大数据版本 报单提供 名字-身份证-手机号 工作日1-3天回单 包含房贷、车贷、信用卡、网贷记录等 人民银行征信报告有哪些欠款记录就体现哪些记录 敏感可接 自觉说明情况 发现不符合情况扣费不出单 没有告知敏感的直接扣钱 具体价格根据情况决定 用途:婚前调查,相亲对象,男女朋友,奔着结婚目的。还有一些合作伙伴, 一定要查一下,现在很多人都有网贷,不要被那些假大款骗了 售价不代表底价 同行代理私聊询价 ———————— @xiaojzc
❤1
此版大数据征信😉😉😉 此版大数据征信😉😉😉 回弹速度快 十几分钟回 基本人在就秒 @xiaojzc
Showing the 12 most recent of 23 posts we hold for @xiongsheng. 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.
Forward network
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.
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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“肖教主 通知@xiongsheng” (@xiongsheng), 5,140 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/xiongsheng.
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.