犯罪服刑记录 已测试稳定回单 当天隔天回 空给图收费 独家源头收单 代理拿价

Channel
吉祥源头批发查档业务
@jxtyc1
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
15,192subscribers
-5,169 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003003553649 |
|---|---|
| Type | Channel |
| Username | @jxtyc1 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/jxtyc1 |
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 79% 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 |
|---|---|---|
| 19 Sept 2026, 17:36 | 15,192 | -1,662 |
| 17 Sept 2026, 07:16 | 16,854 | -984 |
| 15 Sept 2026, 09:19 | 17,838 | -845 |
| 13 Sept 2026, 19:21 | 18,683 | -943 |
| 11 Sept 2026, 22:39 | 19,626 | -670 |
| 9 Sept 2026, 11:39 | 20,296 | -69 |
| 6 Sept 2026, 04:19 | 20,365 | -1 |
| 4 Sept 2026, 02:41 | 20,366 | +5 |
| 2 Sept 2026, 16:46 | 20,361 | +1 |
| 31 Aug 2026, 21:54 | 20,360 | -1 |
| 29 Aug 2026, 23:24 | 20,361 | no change |
| 29 Aug 2026, 22:00 | 20,361 | first reading |
Engagement
22 posts held, back to 5 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 10 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.67%
- avg views ÷ 15,192 subscribers
- Avg views / post
- 254
- 8 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 9
- of 22 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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 22 (5 August 2026 – 2 September 2026) |
| Views total | 2,031 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:20 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.
Recent posts
立案详情带同案人 立案详情带同案人 立案详情带同案人 立案详情带同案人 早报晚上回 最晚明天
吉祥源头批发查档业务 pinned «源头自营业务 批量机主欢迎谈价格 批量卡反欢迎谈价格 批量预留欢迎谈价格 批量法人欢迎谈价格 批量码反欢迎谈价格 黑奴上线只要批量单子有量有价 专注各类批量单子,任何批量单子都可以来谈价格 我这里保单质量,效率、出单率,包过要素,只出真品,成为你保障业务的稳定后盾,老客户都知道。信誉当头,只做口碑!»
源头自营业务 批量机主欢迎谈价格 批量卡反欢迎谈价格 批量预留欢迎谈价格 批量法人欢迎谈价格 批量码反欢迎谈价格 黑奴上线只要批量单子有量有价 专注各类批量单子,任何批量单子都可以来谈价格 我这里保单质量,效率、出单率,包过要素,只出真品,成为你保障业务的稳定后盾,老客户都知道。信誉当头,只做口碑!
移动专线定位 ⚡️⚡️⚡️⚡️ 出必准,人在秒单子 老二网定位 ⚡️⚡️⚡️⚡️ 出必准,联通移动,一小时左右 老三网定位 ⚡️⚡️⚡️⚡️ 晚上22点开,联通移动电信
立案详情,带同案人,隔天回 同案人数出全部 空给图收一半
司法原图直出 真反诈平台 带经办 几率给流水 不保证 不是外面的接口货 复查单子都可来 来点质量单 来点质量单 明天下午回
个人所得税 ⚡️⚡️⚡️ (只能出未注册的) 比医保社保好用一百倍 默认一年记录可指定,天花板级别业务 带工资带单位,看工作,看敏感,看收入必备,人在就秒 税务局业务恢复⚡️⚡️⚡️ (未注册个税的) (对公和发票目前不行) 公司社保单位缴费明细 公司社保员工个人缴费明细 公司财务监事各职人员 在职员工参保人员 财务报表 指定一年
⚡️⚡️自营⚡️⚡️ 银行卡卡反⚡️⚡️ 剩菜卡反⚡️⚡️⚡️ 条子卡反⚡️⚡️⚡️ 无名卡反⚡️⚡️⚡️ ———————————————— 银行卡预留号⚡️⚡️ 剩菜预留⚡️⚡️ 条子预留⚡️⚡️⚡️ ———————————————— 支付宝码反⚡️⚡️ 一系列业务欢迎盘口,同行,车队,盘总前来对接. 我这里保单质量,效率、出单率,包过要素,只出真品,成为你保障业务的稳定后盾,长期合作可验百单,老客户都知道。信誉当头,只做口碑!
公网微反一件套,明天回 公网微反一件套,明天回 公网微反一件套,明天回
⚡️⚡️中国银行柜台流水开 源头直出代理同行问价 有量价优
全头全户 ⚡️⚡️ 单头全户 ⚡️⚡️ 目前最全数据 非实时刑侦数据 当天回单,人在就秒,板子找我拿 不接受扯皮,数据全户,并非刑侦
Showing the 12 most recent of 22 posts we hold for @jxtyc1. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“吉祥源头批发查档业务” (@jxtyc1), 15,192 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/jxtyc1.
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.