Channel
@jding001
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002658301916 |
|---|---|
| Type | Channel |
| Username | @jding001 |
| Created | 2 April 2025 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jding001 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 03:03 | 5 | no change |
| 7 Aug 2026, 08:54 | 5 | first reading |
6 posts held, back to 2 April 2025 — 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 pageof 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 6 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
您好!请直接说明您的来意和需求,以便我快速且准确的回复您！谢谢！ 商品介绍 👇👇点击蓝色字体即可查看商品详情 ✅飞机账号 【2014-2026】 ✅实名飞机号 【广告户 】 ✅Telegram开发者API_ID ✅电报会员代开 ✅频道/群组僵尸粉 ✅苹果ID ✅谷歌邮箱 ✅老频道老群组 👇👇 引流类工具业务👇👇 ✅指定群强拉活人 ✅群发业务 ✅群发器 ✅关键词监听机器人 购买或业务联系白鸽： @ooox68 白鸽交流群 ： @hsl128a 白鸽分享频道： @hsl128 白鸽免费节点分享 ：@baigemf
1564564 pinned «导航首页 购买联系： @HSLgg6 交流群： @hsl128 苹果ID ☑️电报实名号♥️ ✈️精养飞机号✈️ 谷歌邮箱 ✅频道僵尸粉💹 😂Telegram开发者API_ID😗 搜索机器人 🎖 电报会员代开🎖 新手教程 老频道老群组»
导航首页 购买联系： @HSLgg6 交流群： @hsl128 苹果ID ☑️电报实名号♥️ ✈️精养飞机号✈️ 谷歌邮箱 ✅频道僵尸粉💹 😂Telegram开发者API_ID😗 搜索机器人 🎖 电报会员代开🎖 新手教程 老频道老群组
✈️频道帖子阅读 1000=10元 频道群组拉僵尸粉 🍔不掉🍔 😶🌫️50元/1000人 😶🌫️ 🍔不掉🍔 😶🌫️300元/6000人 😶🌫️ 🍔不掉🍔 -😶🌫️500元/1万 😶🌫️
此频道出售
Channel created
Showing the 6 most recent of 6 posts we hold for @jding001. 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.
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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“1564564” (@jding001), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/jding001.
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.