😊😊😊😊😊😊😊☺️😊☺️😊😊 公群编号[1111][公群导航] 全球🌍二手🔤🔤🔤 US高质量一手 ✅邮编,地址,资料正确率高✅ 🉑随机| 🉑挑头 | 🉑毛料 | 🉑一切去重复 大白⚡️⚡️ ⚡️😀😀😀 🤖😺 😳一卖一删,售后无忧!买料联系: @naike5566 😊😊 😊😊😊😊 https://t.me/dbtm1111 24小时客服机器人 @dabai 公群频道 @dabai_a 供需频道 @dabaiyajing
❤1👍1
Signed 大白担保公群交易员2

Channel
@dabaiyajing
On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
15,166subscribers
+276 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002073452965 |
|---|---|
| Type | Channel |
| Username | @dabaiyajing |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/dabaiyajing |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 04:39 | 15,166 | -13 |
| 3 Sept 2026, 21:59 | 15,179 | +42 |
| 2 Sept 2026, 15:48 | 15,137 | +18 |
| 1 Sept 2026, 17:53 | 15,119 | +14 |
| 31 Aug 2026, 21:25 | 15,105 | +76 |
| 30 Aug 2026, 23:54 | 15,029 | +34 |
| 29 Aug 2026, 21:04 | 14,995 | +7 |
| 28 Aug 2026, 19:24 | 14,988 | +7 |
| 27 Aug 2026, 19:42 | 14,981 | +15 |
| 26 Aug 2026, 18:18 | 14,966 | +13 |
| 25 Aug 2026, 16:45 | 14,953 | -30 |
| 24 Aug 2026, 14:52 | 14,983 | +31 |
| 23 Aug 2026, 00:24 | 14,952 | +74 |
| 21 Aug 2026, 13:57 | 14,878 | -4 |
| 20 Aug 2026, 15:43 | 14,882 | +7 |
| 19 Aug 2026, 19:03 | 14,875 | +8 |
| 18 Aug 2026, 19:48 | 14,867 | -2 |
| 17 Aug 2026, 20:06 | 14,869 | -1 |
| 16 Aug 2026, 21:55 | 14,870 | -10 |
| 15 Aug 2026, 15:18 | 14,880 | first reading |
53 posts held, back to 30 June 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 51 pages of 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 14 of 33 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 53 (30 June 2026 – 2 September 2026) |
| Views total | 43,387 |
| Reactions total | 16 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:56 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.
31 reactions across 21 posts, in 4 distinct kinds. The most used accounts for 90.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 28 | 90.3% | |
| 👍 | 1 | 3.23% | |
| 👎 | 1 | 3.23% | |
| 🔥 | 1 | 3.23% |
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 28 of the 53 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 31 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 53 most recent posts we hold, published 30 June 2026 to 2 September 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.
😊😊😊😊😊😊😊☺️😊☺️😊😊 公群编号[1111][公群导航] 全球🌍二手🔤🔤🔤 US高质量一手 ✅邮编,地址,资料正确率高✅ 🉑随机| 🉑挑头 | 🉑毛料 | 🉑一切去重复 大白⚡️⚡️ ⚡️😀😀😀 🤖😺 😳一卖一删,售后无忧!买料联系: @naike5566 😊😊 😊😊😊😊 https://t.me/dbtm1111 24小时客服机器人 @dabai 公群频道 @dabai_a 供需频道 @dabaiyajing
❤1👍1
Signed 大白担保公群交易员2
😊😊😊😊😊😊😊☺️😊☺️😊😊 公群编号[6666][公群导航] 日本🇯🇵核销大王专业收狗鹿瓜 🌟核销🇯🇵日本交通🚄 西瓜卡🍉suica、粉卡🌸pasmo 、蓝卡🌊icoca toica 🌟核销日本狗鹿卡 🌟Waon🐶nanaco🦌 🌟Family pay礼品码 🌟收🇭🇰香港八达通🚊 专业核销3年 老字号有保障 诚信交易🤝先销后结 😊😊 😊😊😊😊😊 https://t.me/dbtm6666 24小时客服机器人 @dabai 公群频道 @dabai_a 供需频道 @dabaiyajing
Signed 大白担保公群交易员2
一键即可添加所有群和频道,关注最新的资讯卖家买家信息 https://t.me/addlist/GKUxmfXpsskzNTlk
Signed 大白
😊😊😊😊😊😊😊☺️😊☺️😊😊 公群编号[695][公群导航] 泡泡寻韩免 2D3D 打手 长期寻韩免 2d3d 打手工作室 各类奢侈品核销 日吃百万 小白勿扰 取货回 u 押金不够可追加 😊😊 😊😊😊😊 https://t.me/dbtm695 24小时客服机器人 @dabai 公群频道 @dabai_a 供需频道 @dabaiyajing
Signed 大白担保公群交易员2
供需广告: 主营:US 亚洲 中东 北美 南美 欧洲 大洋州 非洲 南极洲 全球国家! 可随机 挑头 银行 等级 CD卡 我们拥有一支专业的黑客团队, 每天更新超过20,000张CC。品质始终如一,并非偶然,而是我们的标准。 我们提供真实、可靠、新鲜的数据——直接来自我们自己的渠道。绝不转售! 购买联系人:@ccnb1888
Signed 大白担保公群交易员2
👊⚡️⚡️⚡️⚡️ 品质【一手】🔤🔤🔤 可随机| 可挑头 | 可CD ⚡️⚡️💖❤️🩹❤️🩹⚡️🤖😺 💌💘💝💖😜 联系🆔: @Bdrcvv 双向联系: @Bdrcvvbot 😳"一卖一删,售后无忧! 😀😊 https://t.me/dbtm110
Signed 大白担保公群交易员2
BAT1688海外远控搭建(超强AI版) 1️ 一键AI自动获取支付密码 2️ AI自动生成注入页面· Y行钱包交易所等 3️ 可按需自己构建任意apk前端 4️ ADB 关闭无障碍操作 降低风控,更丝滑 5️ 一键解锁手机 6 软件长期持续更新升级,支付任意定制 7 7*24小时售后响应,让您在鲨鱼的过程中无任何技术烦恼 重大消息: AI自动转账训练已完成,对小白新手十分友好,频道里有示范。 大白公群: https://t.me/dbtm828 @z8657 @BAT1688Bear
❤2
Signed 大白担保公群交易员2
已押1000U长期收德铁 DB 代金券 - 礼品卡 长期收德铁 DB 代金券 - 礼品卡 2D 3D pay paypal 进算 (来长期有实力的 工作室 打手)以上压支持担保 客服:@Da_Zhuang
Signed 大白担保公群交易员2
🏆财神高质量谷歌电商鱼(8年电商鱼经验 只钓优质鱼) 📲IM短信鱼: 🇨🇦加拿大 包裹鱼 按IP计算(水手台) 日量2000+ 🇬🇧英国 停车费 按IP计算 (水手台) 日量1000+ 🇦🇺澳大利亚 航空积分 按IP计算(水手台) 日量500+ 🚀电商鱼: 🇱🇷美国电商鱼 超高质量(无视市场封控) 日量2000+ 🇬🇧英国电商鱼 客单价45英镑起 可禁4头 日量1000+ 🚀价格实惠,绝对一手 ❌注:只和长期客户合作,散户免打扰 🍎客服:@cs268
Signed 大白担保公群交易员2
供需广告: 主营:US 亚洲 中东 北美 南美 欧洲 大洋州 非洲 南极洲 全球国家! 可随机 挑头 银行 等级 CD卡 我们拥有一支专业的黑客团队, 每天更新超过20,000张CC。品质始终如一,并非偶然,而是我们的标准。 我们提供真实、可靠、新鲜的数据——直接来自我们自己的渠道。绝不转售! 购买联系人:@ccnb1888
Signed 大白担保公群交易员2
BAT1688海外远控搭建(超强AI版) 1️ 一键AI自动获取支付密码 2️ AI自动生成注入页面· Y行钱包交易所等 3️ 可按需自己构建任意apk前端 4️ ADB 关闭无障碍操作 降低风控,更丝滑 5️ 一键解锁手机 6 软件长期持续更新升级,支付任意定制 7 7*24小时售后响应,让您在鲨鱼的过程中无任何技术烦恼 重大消息: AI自动转账训练已完成,对小白新手十分友好,频道里有示范。 大白公群:https://t.me/dbtm828 @z8657 @BAT1688Bear
❤1
Signed 大白担保公群交易员2
供需广告: 源头真机im机房 可打条可包鱼 日发百万 免费测试文案落地 可包数据 以下国家可包鱼,按ip算 美国🇺🇸 英国🇬🇧 加拿大🇨🇦 欢迎各大工作室合作 联系客服:https://t.me/liuhuaqiang11dwe
Signed 大白担保公群交易员2
Showing the 12 most recent of 53 posts we hold for @dabaiyajing. 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.
@dabaiyajing edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“大白供需频道” (@dabaiyajing), 15,166 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/dabaiyajing.
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.