Telegram RegisterThe public register of Telegram
Telegram profile photo for 起点交易 · 最新资源推送

Channel

起点交易 · 最新资源推送

@xindian

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

60,397subscribers

-7,104 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001219247845
TypeChannel
Username@xindian
Description╭——— 起 点 核 心 通 道 ———╮ ▪ 官方公告: @QiDian ▪ 公群导航: @DianPu ▪ 最新资源: @XinDian ▪ 供需导航: @Hqwe00 ▪ 内部供需: @Qdvip ▪ 公群入驻: @Dian ▪ 供需客服: @Qdkf3 ▪ 专群客服: @Qdkf1 ▪ 自助专群: @Qdbot ▪ 纠纷专员: @Xtra ▪ 官方仲裁: @Dang ╰——— 安 全 · 高 效 · 稳 定 ———╯
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live21 October 2026
Measurements held46
Confirmed unchanged1 time, most recently 21 October 2026
On Telegramt.me/xindian

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 39% 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

60,39767,50163,9496 August 2026 — 67,501 subscribers7 August 2026 — 67,466 subscribers8 August 2026 — 67,422 subscribers9 August 2026 — 67,356 subscribers10 August 2026 — 67,297 subscribers11 August 2026 — 67,222 subscribers12 August 2026 — 67,155 subscribers13 August 2026 — 67,089 subscribers14 August 2026 — 67,020 subscribers16 August 2026 — 66,911 subscribers17 August 2026 — 66,821 subscribers18 August 2026 — 66,760 subscribers19 August 2026 — 66,711 subscribers20 August 2026 — 66,695 subscribers21 August 2026 — 66,638 subscribers23 August 2026 — 66,528 subscribers24 August 2026 — 66,438 subscribers25 August 2026 — 66,332 subscribers26 August 2026 — 66,259 subscribers27 August 2026 — 66,241 subscribers28 August 2026 — 66,169 subscribers29 August 2026 — 66,107 subscribers30 August 2026 — 66,036 subscribers31 August 2026 — 65,932 subscribers1 September 2026 — 65,855 subscribers2 September 2026 — 65,741 subscribers3 September 2026 — 65,655 subscribers5 September 2026 — 65,498 subscribers9 September 2026 — 65,249 subscribers11 September 2026 — 64,999 subscribers13 September 2026 — 64,796 subscribers15 September 2026 — 64,687 subscribers16 September 2026 — 64,486 subscribers19 September 2026 — 64,258 subscribers26 September 2026 — 63,418 subscribers4 October 2026 — 62,282 subscribers9 October 2026 — 61,716 subscribers13 October 2026 — 61,260 subscribers14 October 2026 — 61,139 subscribers15 October 2026 — 61,014 subscribers16 October 2026 — 60,869 subscribers17 October 2026 — 60,796 subscribers18 October 2026 — 60,763 subscribers19 October 2026 — 60,672 subscribers20 October 2026 — 60,542 subscribers21 October 2026 — 60,397 subscribers6 August 202621 October 2026
46 measurements spanning 76 days, net -7,104. 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 59,331–68,567 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)SubscribersChange
21 Oct 2026, 07:1860,397-145
20 Oct 2026, 04:2560,542-130
19 Oct 2026, 06:2560,672-91
18 Oct 2026, 08:3860,763-33
17 Oct 2026, 11:2760,796-73
16 Oct 2026, 13:2860,869-145
15 Oct 2026, 15:0661,014-125
14 Oct 2026, 14:3561,139-121
13 Oct 2026, 06:3761,260-456
9 Oct 2026, 03:0061,716-566
4 Oct 2026, 13:3762,282-1,136
26 Sept 2026, 05:4063,418-840
19 Sept 2026, 06:3864,258-228
16 Sept 2026, 19:4064,486-201
15 Sept 2026, 01:2064,687-109
13 Sept 2026, 09:5564,796-203
11 Sept 2026, 13:5964,999-250
9 Sept 2026, 00:0165,249-249
5 Sept 2026, 17:5665,498-157
3 Sept 2026, 16:4065,655first reading

Engagement

104 posts held, back to 22 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 154 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.37%
avg views ÷ 60,397 subscribers
Avg views / post
2,040
31 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
31
of 104 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 October 2026
Posts held104 (22 July 2026 – 17 October 2026)
Views total63,162
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Oct 2026, 07:33 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.

What this channel posts

Photos
≈1
Links
≈1,130

Lifetime counters from Telegram’s own channel header, read 21 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

17 Oct 2026, 05:08 UTC≈21,700 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D53 看见源头天眼查 G安 开房 流水 全能查 押金1011U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+FC8iAr4NSaVkMjMx 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

16 Oct 2026, 13:09 UTC875 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D333🏆微信加人一号多加同意就算50 押金1000u 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+FX5cZG81rOc0Yjhk 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

16 Oct 2026, 05:39 UTC853 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D505花火集团微信拉手 押金1000U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+VUzXsO82A180YjE1 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

16 Oct 2026, 01:32 UTC807 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D370 南宫集团PG打人头充值秒返现700 押金1000U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+9P5XXKy-zg0xMjYx 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

15 Oct 2026, 17:29 UTC784 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D506 领先者·出售全行业/渗透/爬虫/指定APP精准数据公群 押金1111U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+XqcNoqSuIPQxNGNl 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

15 Oct 2026, 05:44 UTC815 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D325万象国际注册送28扶持最高反1400 押金3888U 😃😃😃😃😃 😃😀😀😀😃 ————————— 公群通道:https://t.me/+_GXg0-7ToO85MjA1 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

15 Oct 2026, 01:47 UTC796 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D500 夏花集团 盘口直收招聘粉 单价30 安全可靠 押金1000U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+Ayv9J3LxUKo4Mzdl 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

14 Oct 2026, 21:58 UTC769 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D228 免实名注册卡、流量卡各种国外卡 已押1888U 😃😃😃😃😃 😄😀😀😀😃 ————————— 公群通道:https://t.me/+EMATRbnkYRs3NDI1 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

14 Oct 2026, 15:02 UTC779 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D527 租号首选·和尚云机ZM 700-1200 押金1000U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+3yhcflvCW2FlODI1 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

13 Oct 2026, 15:26 UTC901 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D456 创亿【场地直收】手机口260u全网最高价 押金1000U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+kOgOqz9ns5I5YjRl 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

13 Oct 2026, 05:33 UTC953 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D488 MY色料盘口招人头/平台卡车 押金4000U 😃😃😃😃😃 😄😄😄😄😃 ————————— 公群通道:https://t.me/+L7gwcYqkdKhkZjk0 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

11 Oct 2026, 15:36 UTC≈1,160 viewsread 21 October 2026

😃😀😃😀😃·😀😃😃😀 D57 · 全球苹果🆔贷 24小时在线接单 操作简单下款快 随借随还 押金1088u 😃😃😃😃😃 😄😄😀😀😃 ————————— 公群通道:https://t.me/+uAq6xf_n854yYTMx 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

Showing the 12 most recent of 104 posts we hold for @xindian. 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 21 October 2026 — this entry's latest reading, not the date you are reading this.

“起点交易 · 最新资源推送” (@xindian), 60,397 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/xindian.

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.