Channel

@ShouFa

@jddbc

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

4,125subscribers

-2,091 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID	-1001855558165
Type	Channel
Username	@jddbc
Created	Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	7 September 2026
Measurements held	12
Confirmed unchanged	1 time, most recently 7 September 2026
On Telegram	t.me/jddbc

Growth

12 measurements spanning 31 days, net -2,091. 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 3,811–6,530 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
7 Sept 2026, 08:56	4,125	-280
2 Sept 2026, 05:38	4,405	-163
30 Aug 2026, 10:35	4,568	-150
27 Aug 2026, 14:42	4,718	-255
24 Aug 2026, 12:13	4,973	-392
20 Aug 2026, 22:33	5,365	-333
17 Aug 2026, 19:24	5,698	-315
14 Aug 2026, 20:13	6,013	-187
11 Aug 2026, 02:08	6,200	-12
7 Aug 2026, 21:05	6,212	-4
7 Aug 2026, 11:46	6,216	no change
7 Aug 2026, 11:33	6,216	first reading

Engagement

20 posts held, back to 7 May 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 9 pages 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 27 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

27 Jul 2026, 16:14 UTCviews —

@ShouFa pinned a photo

27 Jul 2026, 16:14 UTC42 viewsread 12 August 2026

Photo

⚡️ 24 小时机器人自助服务 🎯 租赁 / 兑换入口： 🟢 点击机器人 👉【@ShouFa】即可自助完成操作 ━━━━━━━━━━━━ ℹ️ 如有任何疑问： 🟢 联系客服【@fanxiaoqin】 🟢 公告频道【首发工具箱·公告频道】 🟢 订单通知群【首发工具箱·订单通知群】 ━━━━━━━━━━━━ 💡 温馨提示 🟡 建议优先使用首发工具箱机器人自助操作，流程更快更稳定！

9 May 2025, 16:08 UTCviews —

@ShouFa pinned «南宫旗下🏆非凡娱乐🎖送288😎😎😎😎😎😎😎😎 🔥南宫旗下🏆《非凡娱乐》🏆冲600送288口令红包 1000反488口令红包南宫——非凡娱乐🏆 8zd.me 问鼎——巅峰国际⚡️ eg9.cc 送分群链接：@dianfeng6699（进频道看置顶）官方客服： @dianfenglb 🔥新台大放水pg 捕鱼电子加拿大快三百家乐六合彩等等新用户一个月可以保证不输钱 🔥不想玩的也可以自己推广玩家首充福利周福利 …最高一个人头1500人民币不用流水直接提。提款支持：🔥usdt…»

9 May 2025, 16:08 UTC≈1,530 viewsread 12 August 2026

南宫旗下🏆非凡娱乐🎖送288😎😎😎😎😎😎😎😎 🔥南宫旗下🏆《非凡娱乐》🏆冲600送288口令红包 1000反488口令红包南宫——非凡娱乐🏆 8zd.me 问鼎——巅峰国际⚡️ eg9.cc 送分群链接：@dianfeng6699（进频道看置顶）官方客服： @dianfenglb 🔥新台大放水pg 捕鱼电子加拿大快三百家乐六合彩等等新用户一个月可以保证不输钱 🔥不想玩的也可以自己推广玩家首充福利周福利 …最高一个人头1500人民币不用流水直接提。提款支持：🔥usdt 支付宝银行卡数字人民币…… 非凡娱乐官方链接： eg9.cc ⚡️ 巅峰国际官方链接： 8zd.me 🏆 你不干不要叫我不要干你不干你怎么抽中华住酒店 ⚡️巅峰链接： eg9.cc EG9.CC 🏆非凡链接： 8zd.me 8ZD.ME 《问鼎一号多多……模拟器黄片加速器…等众多信誉台实用工具导航》…

9 May 2025, 15:55 UTCviews —

@ShouFa pinned «🦇大陆最强军火商公群在压5️⃣🔠🔠🔠🔠 😃😄😃😄 气枪顶尖玩火顶尖 2️⃣🅾️2️⃣5️⃣ 国内一手货源没有中间商一手的价格买到放心 🐣支持双压 🐣支持量大面交 5月9日—5月19日下单即抽iphone16📱 老板： @jesusnpc 公群：https://t.me/+wWIF0Hop9aU1M2U1»

9 May 2025, 15:55 UTC876 viewsread 12 August 2026

🦇大陆最强军火商公群在压5️⃣🔠🔠🔠🔠 😃😄😃😄 气枪顶尖玩火顶尖 2️⃣🅾️2️⃣5️⃣ 国内一手货源没有中间商一手的价格买到放心 🐣支持双压 🐣支持量大面交 5月9日—5月19日下单即抽iphone16📱 老板： @jesusnpc 公群：https://t.me/+wWIF0Hop9aU1M2U1

9 May 2025, 10:45 UTCviews —

9 May 2025, 10:45 UTC614 viewsread 12 August 2026

9 May 2025, 06:59 UTCviews —

@ShouFa pinned «想要低价飞机号？还在到处瞎找？源头直供！全网最全最稳最便宜的飞机号资源，3元起售，各国号码应有尽有，实时更新库存，绝无虚货！【傻逼担保公群002】官方担保，安全交易，信誉保障，买号无忧！支持发卡网自助下单，系统秒发，无需等待，效率拉满！适用范围：注册Telegram、二次验证、养号备用、各种业务搭建必备！一手源头，量大价优，稳定供货，支持批发！个人小量、大客户大量采购均可对接，专属折扣优惠等你来拿！立刻访问发卡网自助下单页面： https://baihu.pics/links/730B6382…»

9 May 2025, 06:59 UTC401 viewsread 12 August 2026

想要低价飞机号？还在到处瞎找？源头直供！全网最全最稳最便宜的飞机号资源，3元起售，各国号码应有尽有，实时更新库存，绝无虚货！【傻逼担保公群002】官方担保，安全交易，信誉保障，买号无忧！支持发卡网自助下单，系统秒发，无需等待，效率拉满！适用范围：注册Telegram、二次验证、养号备用、各种业务搭建必备！一手源头，量大价优，稳定供货，支持批发！个人小量、大客户大量采购均可对接，专属折扣优惠等你来拿！立刻访问发卡网自助下单页面： https://baihu.pics/links/730B6382 傻逼担保❤️ 靠谱没得跑!💪

9 May 2025, 05:47 UTCviews —

@ShouFa pinned «薇薇高价租异常号QQ （续租盘）傻逼担保在压300u 达利永盛上压2500u （总压3399u）异常Q加好友过滤Q全都要吵群盘口夜盘博彩盘三大盘口都有飞机盘口最全的公群星星15 月亮30 夜盘太阳55米皇冠80米 QQ老群50一个上号时间：全天要号结账方式：支付宝微信 u 公群链接 https://t.me/+U7hd0MJYdSBlYTc0 负责人 @weiwei696 信誉频道 https://t.me/+nbIl92OVsEA4MWRl 傻逼担保❤️ 靠谱没得跑!💪»

9 May 2025, 05:47 UTC339 viewsread 12 August 2026

薇薇高价租异常号QQ （续租盘）傻逼担保在压300u 达利永盛上压2500u （总压3399u）异常Q加好友过滤Q全都要吵群盘口夜盘博彩盘三大盘口都有飞机盘口最全的公群星星15 月亮30 夜盘太阳55米皇冠80米 QQ老群50一个上号时间：全天要号结账方式：支付宝微信 u 公群链接 https://t.me/+U7hd0MJYdSBlYTc0 负责人 @weiwei696 信誉频道 https://t.me/+nbIl92OVsEA4MWRl 傻逼担保❤️ 靠谱没得跑!💪

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

@jddb九鼎福利频道
@YYJD6 · 221 post

Names

Channels on the register whose handles appear in this channel's posts.

胜天国际爆奖反馈
@dianfeng6699 · 1,8178 posts @ShouFa·公告频道
@ShouFa33 · 6,1841 post

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.

Handles this channel named that no longer answer

Dead references: 3; handles named in this channel’s posts, vacant today
Evidenced gone: 0; we ourselves saw one of these resolve, at some point
Never seen alive: 3; vacant every time we have ever looked

@jddbc named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.

Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.

Never seen alive

References a handle that is not a live channel — we have no record it ever was one.

@weiwei696
named in 12 posts, 8 August 2026 – 11 August 2026

@jesusnpc
named in 6 posts, 8 August 2026 – 11 August 2026

@qweriii5210
named in 5 posts, 8 August 2026 – 11 August 2026

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

“@ShouFa” (@jddbc), 4,125 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/jddbc.

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.