Telegram RegisterThe public register of Telegram
Telegram profile photo for 昱鼎支付

Channel

昱鼎支付

@ydzf889

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

502subscribers

+3 since we began measuring on 16 August 2026

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

Register entry

Telegram ID-1003350188661
TypeChannel
Username@ydzf889
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/ydzf889

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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

495506500.516 August 2026 — 499 subscribers16 August 2026 — 499 subscribers17 August 2026 — 495 subscribers25 August 2026 — 498 subscribers2 September 2026 — 506 subscribers11 September 2026 — 502 subscribers50216 August 202611 September 2026
6 measurements spanning 26 days, net +3. 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 493–508 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 20:42502-4
2 Sept 2026, 19:13506+8
25 Aug 2026, 20:34498+3
17 Aug 2026, 20:17495-4
16 Aug 2026, 19:15499no change
16 Aug 2026, 19:00499first reading

Engagement

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

Recent posts

16 Aug 2026, 08:50 UTC20 viewsread 16 August 2026
Photo

新产品!!! 名称:云闪付双端H5 金额:1-500(任意) 编码:8062 费率:12.8 "【通道规则】: 抗诉 全层 可抗并发 禁止超时支付(超时支付追不回) 支付时长3分钟 掉单必须24小时内(超过无法查单)禁止会员修改金额!!!会员修改金额支付会员自行承担!!! 🈲三黑料、色敲 🈲诈骗料 🈲资金盘 🈲盲盒话费劵一律不下发" 非bc投诉导致的司法冻结,罚款10万! 查单24小时内!混料一经发现罚款3w 双端!!全天24小时稳定开启!!!!

14 Aug 2026, 19:54 UTC38 viewsread 16 August 2026
Photo

8012 支转卡 码子充足 8012 支转卡 码子充足 8012 支转卡 码子充足 8012 支转卡 码子充足 加加量

14 Aug 2026, 17:01 UTC40 viewsread 16 August 2026
Photo

加量 加量 数字小额 成率依旧稳定 费率1.7 1.7!!!! 加加量冲冲冲!!!!

13 Aug 2026, 23:52 UTC57 viewsread 16 August 2026
Photo

8012 支转卡 8012 支转卡,码子充足,冲冲冲 8012 支转卡,码子充足,冲冲冲 8012 支转卡,码子充足,冲冲冲

13 Aug 2026, 12:19 UTC59 viewsread 16 August 2026
Photo

加量加量!!! 支转卡 码子充足!!! 随便来并发!!! 冲冲冲!

13 Aug 2026, 04:49 UTC60 viewsread 16 August 2026
Photo

加量加量!!!! 支转卡成率拉满了 宝子们上上量 冲冲冲!!!

12 Aug 2026, 12:49 UTC66 viewsread 16 August 2026
Photo

联通联通🛫了 宝子们加加量 码子充足!!! 几乎满绿 冲冲冲!!!!

10 Aug 2026, 03:38 UTC99 viewsread 16 August 2026
Photo

联通加量 联通商城码子超足 全面值都足 宝子们上量!!!!冲冲冲

10 Aug 2026, 02:11 UTC89 viewsread 16 August 2026
Photo

加量加量!!! 移动实时成率图 宝子们冲冲冲 加量开启!!!

9 Aug 2026, 04:08 UTC92 viewsread 16 August 2026
Photo

请看VCR 联通商城起飞了 成率拉满 码子充足!!!

8 Aug 2026, 17:08 UTC93 viewsread 16 August 2026
Photo

昱鼎支付 8026数字小额 码子充足。成率置顶 冲冲冲

6 Aug 2026, 02:32 UTC129 viewsread 16 August 2026
Photo

加量加量 !!! 大哥大姐们 移动网厅恢复!!! 加量冲 加量冲!!!!!

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

“昱鼎支付” (@ydzf889), 502 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/ydzf889.

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.