Channel
@dblc12324
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
52subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002228259137 |
|---|---|
| Type | Channel |
| Username | @dblc12324 |
| Created | 29 July 2024 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 1 |
| On Telegram | t.me/dblc12324 |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 00:04 | 52 | first reading |
20 posts held, back to 29 July 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 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 20 posts for this entry, the most recent from 29 July 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 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.
19 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 42.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 42.1% | |
| 👍 | 6 | 31.6% | |
| 🎄 | 1 | 5.26% | |
| 🔥 | 1 | 5.26% | |
| 😁 | 1 | 5.26% | |
| 🤔 | 1 | 5.26% | |
| 🥰 | 1 | 5.26% |
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 8 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 19reactions 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 29 July 2024 to 29 July 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.
快速查找 1️⃣公群频道和自助验群教程【新手必看】 2️⃣代收代付群交易流程【新手必看】 3️⃣报备类公群交易流程【新手必看】 4️⃣公群不交易类交易流程 【新手必看】 5️⃣公群违规举报要求【新手必看】 6️⃣公群交易注意事项【新手必看】 7️⃣重 要 说 明【新手必知】 8️⃣公群各业务常见纠纷点【新手必看】 ①卡商类 ②代收类 ③承兑类 ④收u代付类 ⑤合作类 ⑥服务类 ⑦搭建类 ⑧引流类 ⑨买卖类 ⑩其它类
👍4🔥1🥰1😁1
⑩其他类 交易所解封业务： 1、解封时间问题 2、解封不成功 3、解封交易所盗U问题 危机公关业务： 1、协商时间内未处理 2、案件升级未协商好 3、案件处理结束，需方质疑供方推进效果 解卡业务： 1、解封不成功
❤1
⑨买卖类 卖各种号业务： 1、账号使用时间 2、账号掉实名需要二次辅助验证 3、账号找回 4、账号风控需要解除风控 手机卡业务： 1、发货时间，长时间未发货 2、收到的卡功能或者归属地与公群描述不符 3、卡收到后短时间内死卡 4、收到是空包或者丢包 5、测卡视频未录制完整一个视频 6、发货和退回寄卡发货视频录制拍完整一个视频 7、结算方式和结算时间未说明 8、未按测卡结算时间结算 卖数据业务： 1、数据不符合预期 2、数据真实性不够 3、数据未在协商时间内给客户 4、数据测试结算问题 能量TRX业务： 1、客户多转或者误转 2、转账长时间未自动兑换 烟酒奢侈品业务： 1、货物质量 2、发货问题 3、退换货问题 保健品业务： 1、货物质量 2、发货问题 3、退换货问题
👍2❤1
⑧引流类 贴卡片业务： 1、数据不达标，怀疑数据造假，刷数据 2、做单视频不合格 3、测码、打印等必报视频没报 4、动动或者水印相机不合格 5、下雨做单，贴纸材质不符合做单要求 6、科技做单、魔术手、一车多贴、多人同行 7、暗扣 收粉收量业务： 1、测试结算问题 引流出粉业务： 1、客户对效果不满意 2、协商时间内未完成交易 短信代发业务： 1、客户质疑短信数量 2、客户对效果不满意 抖音代发业务： 1、公群方怀疑客户刷点赞数量。 2、客户质疑公群方是否真的无法加热 3、客户质疑公群方的原因导致死号 话术单/Q推业务： 1、结算时间 2、扣单问题 电销业务： 1、结算问题
⑦搭建类 网站平台业务： 1、搭建完成有bug 2、后期维护问题 3、源码和服务器问题 4、后期维护和二次开发区分不开 5、退款问题 机器人业务： 1、实际交付成品与需求文档有差异 2、机器人功能问题 3、后期维护问题 签名上架业务： 1、掉签 远控/报du业务： 1、实际交付版本与测试使用版本有差异 2、后期维护问题 域名/服务器业务： 1、搭建完成有bug 2、后期维护问题 3、源码和服务器问题 4、后期维护和二次开发区分不开 5、退款问题 AL换脸业务： 1、所出售的声音建模人物建模，与客户实际需求有出入
❤1
⑥服务类 查档业务： 1、限制的敏感地区、地址、人员、群规则未写明 2、手机定位不准确 3、出现查档限制情况双方未沟通清楚 4、超过双方规定查档时间未出结果 5、查档结果客户不认 外围业务： 1、定金不退的问题 开飞机会员业务： 1、客户多转或者误转 2、转账长时间未自动开通 3、卡密开通 票务口令业务： 1、订票退票问题 2、口令代付问题，只能代付人tou报销费用 设计美工业务： 1、办证和实物差距过大 2、规定时间内未完成交易 接码带实名业务： 1、接码后掉实名 2、账号风控需要人tou配合 3、二次辅助验证
⑤合作类 手机口业务： 1、扣时间纠纷 2、单卡上口结算问题 3、测试口不通过不结算的问题。 4、不结算纠纷（一般为炸鱼、时长不够、不满1小时的无法结算等原因） APP跑分业务： 1、账号关联风控 快递代发业务： 1、结算问题 租苹果ID/租号类业务： 1、上号死号问题 2、账号顶号问题 3、账号风控问题 苹果ID贷业务： 1、还完贷款后苹果的ID号黑了登录不上去了
④收U代付类 1、出款料性与群规不符 2、交易所提币 3、客户到账不查 4、保司法就必须保止付，资金盘规则保30天的问题 5、P图
③承兑类 1、余额和余额宝/零钱和零钱通入款问题 设置码业务： 1、入款料性 2、入账时间或者入账截图问题 3、不按照入款金额修改金额入款 4、拉停时间 平台币核销业务： 1、不按规则入金 2、料性错误 3、死号后无法确认是否拖出 实物回U业务： 1、客户反馈到货公群反馈空包问题 2、核销时间问题
②代收类 1、入金料性和群规不符 2、公群方拉停后入金 3、入金和群内所报金额不符，超额或者少于报金金额 4、入金附言 5、敏感地区入金 6、分笔入款 7、P图 海外直通车业务： 1、到账时间问题 2、飘账问题 3、退回问题 限额划扣业务： 1、卡扣最终扣出的金额 2、卡扣的费率以及回款时间 3、代缴电费以及话费的入款回单以及入款时间。
①卡商类 1、报销问题，按照置顶和报备中的报销规则 2、没有破买断金额，群规体现出来按多少点位结算 3、车队接人问题导致卡主醒了不做 4、翘人头问题，怀疑方需提供流水证明 5、人头抢劫车队、或者车队私下联系人头做 6、盗刷问题
⚠️⚠️⚠️重 要 说 明⚠️⚠️⚠️ 1⃣️好旺担保是一家有底线的担保，涉及人口买卖类、毒品类、军火类业务不接，请免开尊口。凡是涉及这些业务的都是拉假群的骗子。 2⃣️公群内所有服务由商户提供，请联系带“群老板”、“业务员”字样的商户方管理员进行交易，好旺担保只提供担保服务。 3⃣️好旺担保工作人员启用永久用户名，号段hwtb1 到 hwtb999 ,”好旺淘宝”首字母“hwtb”简单好记！ 新手必看：真假群验证技巧 好旺安全防范 @hwtb22 每天发布当天新开的公群: @xinqun 不用到处找,一键收藏好旺担保 (点不开的需要把tg升级到最新版本)
Showing the 12 most recent of 20 posts we hold for @dblc12324. 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.
Citation-graph rank — 1,144,536 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“公群交易注意事项” (@dblc12324), 52 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dblc12324.
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.