Telegram RegisterThe public register of Telegram
Telegram profile photo for 派大星新全球数据库

Channel

派大星新全球数据库

@PAIDX88866

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

5subscribers

-2 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1004484196028
TypeChannel
Username@PAIDX88866
Created27 July 2026 — measured — dated from the channel’s first post
First recorded14 October 2026
Last confirmed live6 November 2026
Measurements held5
Confirmed unchanged3 times, most recently 6 November 2026
On Telegramt.me/PAIDX88866

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 17 October 2026 and assigned it the closest of 31 fixed categories, at 93% 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

586.514 August 2026 — 7 subscribers29 August 2026 — 8 subscribers6 September 2026 — 7 subscribers14 October 2026 — 7 subscribers22 October 2026 — 5 subscribers14 August 202622 October 2026
5 measurements spanning 69 days, net -2. 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 5–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Oct 2026, 17:505-2
14 Oct 2026, 21:237no change
6 Sept 2026, 16:017-1
29 Aug 2026, 12:578+1
14 Aug 2026, 18:457first reading

Engagement

4 posts held, back to 27 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 4 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

17 Aug 2026, 12:56 UTC103 views0 reactionsread 14 October 2026
Photo

👑派大星海外数据 全球优质数据 ⚡️⚡️⚡️⚡️⚡️⚡️ 🔥 专注海外数据两年半,源头数据渗透机房,只出售高品质高质量数据,实力机房品质保证,始终保持着不乱来,不惨水不二次出售! 🔥 数据类型系列: 【车主】【投资】【币圈】【医生】【精聊】【富人】【支付】【华侨】【房产】【股票】【教育】【币安】【海外】【购物】【旅游】【房主】【保险】【航空】【纳税】【博彩】【理财】【珠宝】【酒店】【求职】【亚马逊】【奢侈品】【高收入】【高消费】【高净值】 你想要的都可以安排到位☺️ 🔥国家类型系列: 🔥 你观察半年是我,观察一年还是我,观察三年依然是我,观察久了自然就放心了,做数据,我是认真的, 有需要,随时联系!…

14 Aug 2026, 03:54 UTC100 viewsread 14 October 2026
Forwarded from @KKGX678Photo

供应商品:派大星海外源头数据 商品介绍:技术团队接海外指定站点渗透 高质量高活跃料子、数据类型: 💵【股民】【投资】【理财】【高管】【白领】 💵【基金】【医生】【金融】【兼职】【企业】 💵【退休】【币圈】【车主】【交友】【航空】 💵【领英】【购物】【华侨】【财经】【币安】 💵【股票】【银行】【房主】【招聘】【珠宝】 💵电销,精聊,快杀,短信,群发,拉群专用料,精准料子可筛选年龄 性别 活跃 现跑现筛 只做一手料 专业技术团队护航-定制属于您的数据人群 筛选:【line】【zalo】【ws活跃】【TG活跃】【IOS】【RCS】【IM】【FB】【TK】【VB活跃】 价格:冰点价格 联系人: @PAIDX886 产品频道:https://t.me/PAIDX88866 交易方式:支持KK出海担保交易

12 Aug 2026, 07:01 UTC88 viewsread 14 October 2026
Photo

⚡️⚡️ 派大星源头数据 可实时抓取出精料! ⚡️⚡️⚡️你来要求 我来办事 ⬇️数据类型⬇️ #美国 #TG 美国TG用户 超精准客源 可去黑 可去T 筛选性别 定制一切需求 每天稳定供应! 联系方式:😀😀😂认准:@PAIDX886 😘😘😘😘📱📱📱📱📱📱📱📱

Showing the 4 most recent of 4 posts we hold for @PAIDX88866. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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 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.

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

“派大星新全球数据库” (@PAIDX88866), 5 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/PAIDX88866.

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.