Channel
@yndb_gz
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
89,792subscribers
+4,963 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002481776660 |
|---|---|
| Type | Channel |
| Usernames | @YNDB_DBGZ @yndb_gz |
| Description | 一诺通知 @xiaohaigeSGK 一诺供需 @yndb_gongxu 交流大群 @XiaoHaiGe_SGK 交流二群 @yndb_xq 广告群组 @ynguanggao 供需商家 @YNDB_DBGZ 公群导航 @YNDB_GQGZ |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/yndb_gz |
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 38% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 21:59 | 89,792 | +162 |
| 16 Sept 2026, 12:00 | 89,630 | +119 |
| 14 Sept 2026, 18:56 | 89,511 | +66 |
| 13 Sept 2026, 07:55 | 89,445 | +94 |
| 11 Sept 2026, 13:21 | 89,351 | +389 |
| 8 Sept 2026, 18:20 | 88,962 | +449 |
| 5 Sept 2026, 09:56 | 88,513 | +247 |
| 3 Sept 2026, 10:05 | 88,266 | +121 |
| 2 Sept 2026, 07:07 | 88,145 | +120 |
| 1 Sept 2026, 05:53 | 88,025 | +94 |
| 31 Aug 2026, 04:43 | 87,931 | +120 |
| 30 Aug 2026, 05:43 | 87,811 | +92 |
| 29 Aug 2026, 07:15 | 87,719 | +139 |
| 28 Aug 2026, 10:23 | 87,580 | +84 |
| 27 Aug 2026, 11:36 | 87,496 | +163 |
| 26 Aug 2026, 11:24 | 87,333 | +124 |
| 25 Aug 2026, 08:48 | 87,209 | +64 |
| 24 Aug 2026, 12:13 | 87,145 | +289 |
| 22 Aug 2026, 20:23 | 86,856 | +236 |
| 21 Aug 2026, 08:02 | 86,620 | first reading |
6 posts held, back to 15 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 97 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 6 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 22 September 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.
一诺担保-供需商家 @YNDB pinned «供需商家为推荐制 新商家必须有老商家推荐 任何商家出事牵连推荐人 初始商家👇 佩奇查档 @peiqi_tyc 公群586 小怡查档 @xiaoyi9111 魔盒查档 @mohe008 公群333 美团查档 @mtina 猫猫查档 @maomao_kefu 公群111 大帅查档 @dscd5 极速查档 @jscd8888 公群078 小念查档 @xiaoxiao00 公群678 荒查档 @xnn_888 公群008 老班长查档 @lbztyc 仲谋查档 @zhongmou0 少妇查档 @shaofuu…»
大帅自首并做好徒弟天天通单子所有善后工作 从轻罚款 444u 发内部商家群 天天通一诺善后联系大帅 @dscd5
@ttcd11 天天通跑路 担保人 @dscd5 大帅 一诺供需被天天通跑路的联系大帅接替出单 @dscd5 根据商家推荐规则 1.大帅最好善后 2.大帅群发888u红包 联系大帅 @dscd5
供需查档广告只有以上人员👆 https://t.me/yndb_gongxu 无公群商家可使用一诺钱包担保交易 @yndb_wallet_bot
人脉关系👇 杨意查档 @wiwnn 介绍人：大帅 鸿蒙查档 @hmcd001 介绍人：美团 真家查档 @A000699 介绍人：小念 大B查档 @dabi5555 介绍人：大帅 止水查档 @zscd001 介绍人：范冰冰 泡泡查档 @ppcdfj 介绍人： 荒
供需商家为推荐制 新商家必须有老商家推荐 任何商家出事牵连推荐人 初始商家👇 佩奇查档 @peiqi_tyc 公群586 小怡查档 @xiaoyi9111 魔盒查档 @mohe008 公群333 美团查档 @mtina 猫猫查档 @maomao_kefu 公群111 大帅查档 @dscd5 极速查档 @jscd8888 公群078 小念查档 @xiaoxiao00 公群678 荒查档 @xnn_888 公群008 老班长查档 @lbztyc 仲谋查档 @zhongmou0 少妇查档 @shaofuu 范冰冰查档 @B5200B
Showing the 6 most recent of 6 posts we hold for @yndb_gz. 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.
@yndb_gz 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 registered channels — 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“一诺担保-供需商家 @YNDB” (@yndb_gz), 89,792 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yndb_gz.
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.