一天24小时都在线💎 正在上班中~ 欢迎各位老板下单 TG引流/代发/上粉/开会员/什么业务都有 便宜实惠不坑蒙拐骗任何一位用户长期合作的可以优惠、活动福利多多每日都有活动和福利6月22日晚上9点准时发红包🧧、TG上粉认准娜美不吃亏 💎客服:@tgwu1 💎双向机器人:@IIdzdzBot https://t.me/tgwu0

Channel
大众👑供需7u或50口发布
@dzdb3
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,931subscribers
-29 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001753122090 |
|---|---|
| Type | Channel |
| Username | @dzdb3 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/dzdb3 |
Topic
Gambling & betting — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 14:41 | 1,931 | -5 |
| 14 Sept 2026, 20:38 | 1,936 | -5 |
| 10 Sept 2026, 23:18 | 1,941 | -2 |
| 5 Sept 2026, 15:00 | 1,943 | -1 |
| 1 Sept 2026, 19:16 | 1,944 | -3 |
| 26 Aug 2026, 10:34 | 1,947 | -1 |
| 23 Aug 2026, 08:16 | 1,948 | -2 |
| 19 Aug 2026, 23:36 | 1,950 | -3 |
| 16 Aug 2026, 16:54 | 1,953 | -2 |
| 13 Aug 2026, 02:54 | 1,955 | -4 |
| 10 Aug 2026, 13:22 | 1,959 | -1 |
| 7 Aug 2026, 18:58 | 1,960 | no change |
| 7 Aug 2026, 11:17 | 1,960 | first reading |
Engagement
20 posts held, back to 3 February 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 21 June 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
4 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 75.0% | |
| 👍 | 1 | 25.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 3 February 2024 to 21 June 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
28圈合营代理见面礼大放送!🎉 🌟限时新代理推荐,奖励高达18888元! 🎁推荐即享丰厚扶持奖励,机会难得,不容错过! 💸直属下级投注欧洲杯赛事,最高奖金可领3888888元! 📈更有欧洲杯赛事投注流水提成,限时返利5%! 🛫 纸飞机联系: @GQ_9901 28圈最新下载链接:https://ljlycd.top/#/link?allwin=3564579 28圈诚挚祝愿你在此次活动中财源滚滚、大发利市!
❤1
漫威招车队/盘口/中介 优势1:点位美丽,全网高价 优势2:从不排队,从不罚站 优势3:公户 私户都可以 诚聘有实力的合作伙伴 长期合作 联系人:@lilelele568 https://t.me/+OoAx0AyvLcExZmUy 乐乐老板重金买断广告一天
白资代付 欢迎盘总对接(中介可聊) Bc会员下发,代付 下发区间:100-49999 下发方式:贴群 或api 充值模式:充u代付 是否包司法:包司法,查档为准 骗子查波场P图的别来浪费时间 联系人:@Sss9098 ——————-—————————————-请注意:此供应/需求为免费广告,本群不做任何担保,真伪自己辨别,最终解释权归本群所有!
大众👑供需7u或50口发布 pinned Deleted message
♻️纯绿色项目,操作简单 项目名称:注册 QQ一单一结 项目要求:能注册 QQ手机号接验证码即可一个手机号可以接两个码 三十秒任务,秒结口令或u 价格:四码320 结算方式:u口令 联系人:@Truuo6 对接群:https://t.me/iiss66888 一单一结无套路,秒口令320 (事优先推荐此广告)靠谱
❤1
专业做银行卡非柜解冻资料,支付宝止付解封资料,擅长各类证件合同印章PS,工作证明,虚拟银行APP,视频编辑,全能美工。 联系: @zhongli888888
👍1
650官方 信誉平台 安全可靠 不黑不卡 资金安全 650cc 实力抗大户 为您保驾护航 IM体育 沙巴体育 玩法齐全 168极速系列 澳洲系列 幸运飞艇 AG百家乐 双赢棋牌 游戏齐全 优势🔥1️⃣: 不限IP,菲律宾、迪拜、柬埔寨随便玩! 优势🔥2️⃣:虚拟币存提款无需实名绑卡,无须认证大陆手机,保障会员信息安全! 优势🔥3️⃣:充值渠道齐全,24小时在线客服为会员提供安全充值通道! 优势🔥4️⃣:充值提款到账速度快,秒杀其他平台! 【650cc】信誉盘 官网注册 👉 650-76.com 邀请码 👉 18815
a17集团租🔠🔠id续租慢杀 一个id一天能挂1️⃣🔠➖1️⃣2️⃣小时 超强续租!!! 散户:👍👍起 团队、机房:👍👍👍👍👍 吃饭不扣时长,不会一天包三顿!!! 正常id 能连续挂好几天 不满一小时按半小时结算 不满半小时不结算 没有时间限制 不掉号!不掉号!很多市场上高价,但是没一会就掉号了。我这挂号 稳定奔放😎🤥🤓😞 散户一天千元以上收入 位置5️⃣🔠🔠➕不堵车 发资料秒安排 号商、大团,一天万元利润 一号公群押金1500u:https://t.me/xiaojiu2024fff 二号公群押金500u:https://t.me/jbpxinum5 三号公群押金500u:https://t.me/a172024fff 负责人:@YO_YYDS 频道:https://t.me/a17yyds
❤1
🥰 [问鼎娱乐 ] wdt16.vip 60%佣金-诚招代理,新增人头费500/1人 上不封顶 携手共创财富🏆创造未来 加拿大丨比特丨分分丨体育 电竞丨六合丨棋牌丨百家乐丨 彩票丨电子 —————————————————— ✅新人100+100💸 实力大平台|佣金最稳,官方直招|待遇拉满 💸 存 取款快、大额无忧 支持 支付宝//USDT💰 💸加入问鼎代理直享60%负盈利佣金+高额人头费+新代理扶持+保底佣金+流水提成+介绍代理提成+周流水+双域名扶持+年终奖++(无需投资) 😎🤥🤓😞😍🤓🤓😎
项目名称 微信免验证数据是直接通过的不需要验证信息 单价6 需要换个头像 还有名字然后发两个图片就可以了 对接人 @xiaohao15 对接群 https://t.me/+tLinNlbO0ahhMzBl 频道 https://t.me/wwjdsj
项目名称:冠希手机口场地直招【课结】 二道白料!不易死卡!时长拉满! 🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹 ⬆️⬆️⬆️⬆️⬆️💸💸💸 🥰🥰🔠起!🔹🔹🔹🔹🔹🔹🔹🔹🔹 价格:无线手拨!单小时🥰🥰😵💫 口令🔠🥰🥰3小时🥰🥰🥰 每天早上前十名奖励🥰🥰rmb的早餐!!! 一天内多口可以叠加!累计! 🔺🔺🔺🔺🔺🔺🔺🔺🔺🔺🔺 甘肃,新疆,云南,宁夏地区都要!联通!广电!都要! (另招上口客服一名 傻子勿扰) 🔺🔺🔺🔺🔺🔺🔺🔺🔺🔺🔺 下课结账!下课结账! 结账可以走👍,👍,👍! 🔺🔺🔺🔺🔺🔺🔺🔺🔺🔺 你可以永久相信本公司!实力担当! 单口时长🥰小时 🥰小时 拉满 福利多多 欢迎各位老板咨询!!! 团队可以来找我谈价格!🥰🥰起! 已在新旺上押! 🔺🔺🔺🔺🔺🔺🔺🔺🔺🔺🔺 🔻🔻联系人: @esldb 🔻🔻对接群 : https://t.me/guanxiooo ------------------------- 👉查看发布者【累计发布940次】
Showing the 12 most recent of 20 posts we hold for @dzdb3. 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.
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.
Handles this channel named that no longer answer
- Dead references
- 16
- 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
- 16
- vacant every time we have ever looked
@dzdb3 named 16 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.
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“大众👑供需7u或50口发布” (@dzdb3), 1,931 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/dzdb3.
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.