Telegram RegisterThe public register of Telegram
Telegram profile photo for 桃子查档批发源头供货

Channel

桃子查档批发源头供货

@lxtcd

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

74subscribers

+18 since we began measuring on 29 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003232214786
TypeChannel
Username@lxtcd
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live12 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/lxtcd

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 28 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 the other topics.

Growth

56746529 August 2026 — 56 subscribers30 August 2026 — 57 subscribers8 September 2026 — 58 subscribers17 September 2026 — 60 subscribers2 October 2026 — 64 subscribers13 October 2026 — 62 subscribers21 October 2026 — 66 subscribers28 October 2026 — 67 subscribers4 November 2026 — 72 subscribers12 November 2026 — 74 subscribers29 August 202612 November 2026
10 measurements spanning 75 days, net +18. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 53–77 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 14:1174+2
4 Nov 2026, 01:2572+5
28 Oct 2026, 00:1567+1
21 Oct 2026, 07:0666+4
13 Oct 2026, 04:2762-2
2 Oct 2026, 21:2064+4
17 Sept 2026, 08:2060+2
8 Sept 2026, 13:1658+1
30 Aug 2026, 11:3757+1
29 Aug 2026, 20:0056first reading

Engagement

20 posts held, back to 11 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 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 28 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

28 Aug 2026, 11:26 UTC20 viewsread 29 August 2026

空车,在秒 有单上!! 专门处理剩菜,其他渠道出不来的单

20 Aug 2026, 12:37 UTC34 viewsread 29 August 2026
Photo

个人所得税🥰🥰🥰 默认一年记录可指定 带工资带单位 当天回 人在秒 用途:看工作,看敏感,看收入

20 Aug 2026, 12:36 UTC33 viewsread 29 August 2026

高德打车记录 🥰🥰🥰 姓名+身份证+个户 强登录频所有打车记录

8 Aug 2026, 15:44 UTC45 viewsread 29 August 2026

近期市场核验频繁拉闸、补齐系列涨价 这边依旧原价,出单率、效率不变 丝毫没有影响!! 区别所有假支百冒充真支百以好充次的渠道。

5 Aug 2026, 10:55 UTC53 viewsread 29 August 2026

车牌反车主 🥰🥰🥰 回单: 车主名字+身份证号码+预留手机号 空不收 回单很快 基本秒

4 Aug 2026, 06:03 UTC55 viewsread 29 August 2026

美团最新10条 全天在线秒 时间➕地址😃😃😃😃 时间➕地址➕商品😃😃😃😃 提供手机号码报单 一年内(一条也正常收费)

3 Aug 2026, 12:19 UTC52 viewsread 29 August 2026

此版本湖北开同是湖北身份证 全国范围,并非市面上只能出湖北省内登记过的

3 Aug 2026, 07:41 UTC129 viewsread 29 August 2026

全网独家湖北单省全业务‼️ 湖北刑侦全🥰🥰🥰 全头 带户号 真刑侦!! 湖北开同🥰🥰🥰🥰 湖北单开🥰🥰🥰🥰 湖北飞火🥰🥰🥰🥰 湖北天眼找人《监控记录》 湖北名下车辆《车牌号 无遗漏》 全省业务通杀 详细需求咨询 ⚠️敏感扣单收费 0手源头 同行拿价 批量来问

2 Aug 2026, 03:29 UTC305 viewsread 29 August 2026

四网无盲机主🥰🥰🥰 支付宝百分百机主🥰🥰🥰 报单格式: 手机号 手机号+模糊名 手机号+全名 ➡️区别市面一切破解支百、公网补支百、跑全国支百。 同价位出单率天花板‼️ 源头直收,代理问价

30 Jul 2026, 04:49 UTC52 viewsread 29 August 2026

带定位链接手机轨迹🥰🥰🥰 手机号码封禁🥰🥰🥰 继续收

30 Jul 2026, 04:37 UTC43 viewsread 29 August 2026

全网支三批三陆续拉闸、限制等情况 出单依旧稳定、不影响出单率、速度。 价格不变 继续上单

Showing the 12 most recent of 20 posts we hold for @lxtcd. 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 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.

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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“桃子查档批发源头供货” (@lxtcd), 74 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/lxtcd.

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.