能承包的靠谱大团来谈! 来兼职卡发 不押款 不扣款 每日数据10000+找大团承包【靠谱大团来谈】 桃子手工招聘短信 【诚招!全网最高价!】 团队/每条1.5元起!【团队福利】 团队/回复5-7元起!【团队福利】 团队每周可甩你3.5散户说到做到!!! 【散户待遇也拉满!】 散户/每条1.5起!【欢迎稳定散户】 散户/回复5起!【欢迎稳定散户】 各大担保均在压 业务员: @dshunde 在押公群: https://t.me/+71YVL04t_0s0MGVl
❤1😁1

Channel
@dyzdb
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,492subscribers
-15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001564178000 |
|---|---|
| Type | Channel |
| Username | @dyzdb |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/dyzdb |
Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 56% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @dyzdb/72610 · this entry14 Jul 2026, 05:44 UTC | @bb88/926026 Aug 2026, 06:21 UTC | 1.00 | 23 days |
| @dyzdb/72613 · this entry14 Jul 2026, 12:41 UTC | @bb88/926036 Aug 2026, 07:21 UTC | 1.00 | 23 days |
| @dyzdb/72609 · this entry14 Jul 2026, 04:45 UTC | @bb88/926066 Aug 2026, 11:31 UTC | 1.00 | 23 days |
| @dyzdb/72608 · this entry14 Jul 2026, 04:14 UTC | @bb88/926086 Aug 2026, 14:38 UTC | 1.00 | 23 days |
| @dyzdb/72606 · this entry14 Jul 2026, 02:21 UTC | @bb88/926157 Aug 2026, 02:00 UTC | 1.00 | 24 days |
| @dyzdb/72621 · this entry15 Jul 2026, 03:01 UTC | @bb88/926177 Aug 2026, 06:07 UTC | 1.00 | 23 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @bb88 | 12 (8/8 hand-verifiable sample passed) | 1.00 | 23 days | this entry (12–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 14 July 2026 to 15 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @dyzdb — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 01:47 | 3,492 | -14 |
| 7 Aug 2026, 15:30 | 3,506 | -1 |
| 7 Aug 2026, 13:18 | 3,507 | first reading |
20 posts held, back to 14 July 2026 — 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 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 July 2026 |
|---|---|
| Posts held | 20 (14 July 2026 – 15 July 2026) |
| Views total | 5,362 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:11 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
3 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 66.7% | |
| 😁 | 1 | 33.3% |
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 2 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 3reactions 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 14 July 2026 to 15 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
能承包的靠谱大团来谈! 来兼职卡发 不押款 不扣款 每日数据10000+找大团承包【靠谱大团来谈】 桃子手工招聘短信 【诚招!全网最高价!】 团队/每条1.5元起!【团队福利】 团队/回复5-7元起!【团队福利】 团队每周可甩你3.5散户说到做到!!! 【散户待遇也拉满!】 散户/每条1.5起!【欢迎稳定散户】 散户/回复5起!【欢迎稳定散户】 各大担保均在压 业务员: @dshunde 在押公群: https://t.me/+71YVL04t_0s0MGVl
❤1😁1
哪吒快手租号全网上押6000U 快手80起 快手3+85 快手5+90 快手10+100 快手要求:3小时全,以用号时间开始计算,要能配合激活,配合登录,1小时内配合不了不算钱,每天中午开始上号,下午5点用号开始计时。一切以盘口反馈为准。 1、挤号,捣乱,改密码的一律清零,,挤号直接清零,不续租提前一天说,不然挤号一律清零+开户。 2、晚12点结账之前一定要报帐不报帐不结账。12点结完帐就可以把设备踢了号挤了,第二天重新上,不踢设备被偷用跟我方无关,不扯皮。 上号客服: @XMT88888888 上号客服: @guotianyi1 公群老板:@nznb0 太平洋上押560u:https://t.me/+J92mvTYxHUJhMmJl
ZMPC超强月租 日在租150+ZM PC 主打长租 稳定日结 不需要每天报账 定时打款 可看续租表 诚心招 zmpc 微信号商散户 一个月打底4000+利润 很多人都只在乎单价高的 其实那种没有三四天就死号了 我们这里主打的就是续租 你一个月号在别人那里可能就一两天 在我这里一般都是一个月起步 上号上的多的直接来找我谈待遇不墨迹 我一定给你最稳定的价格和最稳定的续租 这个年头,续租强才是王道 价格:130-200 诚招号商:150-200 电商 精聊 六合彩 挂群主 目前可以打全网 不封号!不封号!基本一天没有太大的工作量 押金只压当天的50以防顶号 不续租结清 只扣一天的50!! 散户~量大可以私聊价格 我这边只做续租盘 而且价格也比别人高很多 我可以说我这个续租情况 再加上这个价格 基本没有人可以来比较 全网续租最强 公群老板:@argggg 太平洋公群:https://t.me/+aoUgKwZAFxg2NGNl
项目名称:地推盖单车 项目简介:杭州上城区 深圳南山区 价格:0.8-0.9 不用换地方 常年每天盖 上押公群链接: https://t.me/+IY3VHs-ZU5w0OThl
全网上压20000U 项目名称:代发评论、代发视频 主营:抖音、快手、小红书等等 价格:最高80米一单(不封号,好出单、不是杀猪料、不是色料、通过率高、) 结帐方式:USDT、支付宝口令 挑战全网最高价!!每天可循环做 迎接世界杯,长期包养团队和工作室 欢迎有实力的来谈,盘口直招,无中间商 公群:https://t.me/+Cb6ueWXePFM2ZWE1 公群:https://t.me/+bY5a3Nvcv9wwNTc1 公群:https://t.me/+Q2eeyRAortg3M2Vl 公群:https://t.me/+EHJXGjY7Aoc3YjM8 公群:https://t.me/+lMBPjELP9HxhMjll 公群:https://t.me/+_tWYfbOndjs4Mzkx 公群:https://t.me/+NyF3g90ABLUwMDI0 公群:https://t.me/+lL9tVmAZevhjY2Nl
2026国际平台王炸合集!@duge 戴高乐 领航 汇赢 星耀 壹号 问鼎 君临 胜天 豪门 新时代 东升 逐梦 凯旋等全系列!充值100送88 500送288现金! 点击查看玩家爆奖反馈,不干怎么操女人 捕鱼 电子 加拿大 快三 百家乐 六合彩等等 新用户一个月可以保证不输钱 提款支持:usdt 支付宝 银行卡 数字人民币 聚鑫汇官方链接: bjx17.top 戴高乐官方链接: 27dgq.top 领航国际: lhr66.top (强推) 汇赢国际: hu65w.top (推荐) 星耀国际: x13wy.top (新台) 君临链接: y6gx.top (新台) 胜天国际: sh81f.top (新台) TOP娱乐: t94ur.top 超凡国际: c81bf.top 壹号娱乐: ya10m.top 问鼎娱乐: ww41d.top 旺财28: wfc4.top 赏金国际: sw…
文赫📱手机口 手机📱口 全网押金15万u折合人民币100万元 运营时间三年多 最开始的初心一直以 (真诚)为主 不黑不扣 稳稳当当 有自己的运营方式 毕竟做这一行的大家都是顶着风险在做 没必要为了一点利益 破坏了大家的合作关系 以长久为伴 以回头客为主 一直以来从未忘记 新的一年 祝贺大家多多赚钱 价格可能不是最高 但是绝对是最让你满意 就让我们相约 在山的顶峰相见 浪漫至死不渝 我们的梦就要实现 太平洋 手机口上押5000u https://t.me/+9Q370hleKC9jZThl https://t.me/+9Q370hleKC9jZThl https://t.me/+9Q370hleKC9jZThl
❤1
小🉑TRX能量笔数兑换代开飞机会员! 【能量闪租2.5TRX即可免费转账一笔能量,,, 能量时长超实惠1.5trx即可免费转账一笔】 ---能量租用--TRX兑换--能量笔数套餐--智能托管--代开TG会员--机器人可监听地址查询余额 真实笔数,放心使用 全网上押上万USDT 转错可退回,用得安心,全天24小时在线! 太平洋担保上押公群: t.me/hihinbnb258 全网最优、转账省百分之80手续费~省钱省事。转错包退~安全放使用!
全网上压20000U 项目名称:代发评论、代发视频 主营:抖音、快手、小红书等等 价格:最高80米一单(不封号,好出单、不是杀猪料、不是色料、通过率高、) 结帐方式:USDT、支付宝口令 挑战全网最高价!!每天可循环做 迎接世界杯,长期包养团队和工作室 欢迎有实力的来谈,盘口直招,无中间商 公群:https://t.me/+Cb6ueWXePFM2ZWE1 公群:https://t.me/+bY5a3Nvcv9wwNTc1 公群:https://t.me/+Q2eeyRAortg3M2Vl 公群:https://t.me/+EHJXGjY7Aoc3YjM8 公群:https://t.me/+lMBPjELP9HxhMjll 公群:https://t.me/+_tWYfbOndjs4Mzkx 公群:https://t.me/+NyF3g90ABLUwMDI0 公群:https://t.me/+lL9tVmAZevhjY2Nl
四方PC ZM博彩续租 zm:3个月以上账单30以上好友 pc:不看账单30以上好友 ZM价格140 Pc价格100 月租起步全网续租天花板 适合刚开始的号商或者稳量的号商,续租率高于90%以上 散客不能长租回复慢的别来(号商优先) 不打算长租的号商别来 欢迎号商试号对比 上押公群: https://t.me/+Is_Tt40XlgljYmQ1
哪吒快手租号全网上押6000U 快手80起 快手3+85 快手5+90 快手10+100 快手要求:3小时全,以用号时间开始计算,要能配合激活,配合登录,1小时内配合不了不算钱,每天中午开始上号,下午5点用号开始计时。一切以盘口反馈为准。 1、挤号,捣乱,改密码的一律清零,,挤号直接清零,不续租提前一天说,不然挤号一律清零+开户。 2、晚12点结账之前一定要报帐不报帐不结账。12点结完帐就可以把设备踢了号挤了,第二天重新上,不踢设备被偷用跟我方无关,不扯皮。 上号客服: @XMT88888888 上号客服: @guotianyi1 公群老板:@nznb0 太平洋上押560u:https://t.me/+J92mvTYxHUJhMmJl
太平洋C987 萬豪集团🏆金屿QQ接码注册全网最高价–秒结账 QQ注册接码一个7元只需要收一个验证码就可以纯捡钱项目秒结账 要求:只要可以收到验证码的号码统统发来! 大量位置结束秒结账 给得了你稳定 给得了你安心 公群链接:https://t.me/+2K5ow0yilJMxYzY1 公群老板:@JINYUHOA
Showing the 12 most recent of 20 posts we hold for @dyzdb. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“大洋洲供需 @dyzdb 免费代理分享” (@dyzdb), 3,492 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/dyzdb.
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.