Channel
@danbaoh
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,888subscribers
-597 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003757742602 |
|---|---|
| Type | Channel |
| Usernames | @danbaoh @fulilai4 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/danbaoh |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 |
|---|---|---|
| 16 Sept 2026, 05:59 | 2,888 | -13 |
| 12 Sept 2026, 09:39 | 2,901 | -335 |
| 8 Sept 2026, 00:58 | 3,236 | -123 |
| 2 Sept 2026, 13:44 | 3,359 | -62 |
| 30 Aug 2026, 12:58 | 3,421 | -23 |
| 27 Aug 2026, 17:04 | 3,444 | +27 |
| 24 Aug 2026, 18:45 | 3,417 | -4 |
| 24 Aug 2026, 15:08 | 3,421 | -39 |
| 20 Aug 2026, 19:17 | 3,460 | -1 |
| 20 Aug 2026, 13:52 | 3,461 | -17 |
| 17 Aug 2026, 17:26 | 3,478 | -4 |
| 17 Aug 2026, 12:26 | 3,482 | -3 |
| 16 Aug 2026, 19:31 | 3,485 | first reading |
8 posts held, back to 4 August 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 1 page 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 8 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
整理了一下 少爷这个人 劣迹斑斑 1：帮助南宫做APP 利用技术漏洞刷走几万U 导致关门 2：帮rich 做虎牙极速色子 也是买什么开什么 刷走13万u 导致关门 3：帮雨婷做极速，直接说介绍个客户，其实是自己小号 刷走3万 导致关门 他本人没有技术团队，全是外包，比如出现什么漏洞就请人10u 5u 修复 就这样忽悠了两三年。。。 群里部分新人很多找他做的产品，不是因为资金损失 就是因为产品缺陷得不到修复，导致关门 总结一句话：自己吃的亏不想在群里说，导致骗子可以无限重复的骗人
周润发 发哥 @fage 被 @shaoye 杀熟4000U 从送水认识到现在开上了E300，一起度过的风风雨雨算什么 少爷，你没有心。
皇冠担保宣布并购新币旗下万邦担保海外业务 相当于说 新币把欧美最棘手的大尾巴切割了 让出去了 目前全面让皇冠接手了，海外支付利润多大 ，是能算出来的 新币这一招 属于是断尾求生
在NFT圈子5年老人 在群里频繁发出售+888 获利8万U 目前已跑路 少爷 @shaoye
新币旗下海外担保 万邦担保 @wbgq 宣布结业 📢 关于万邦海外业务调整及退押的温馨提示 亲爱的用户： 感谢大家一直以来对万邦的信任与支持。因业务方向调整，万邦海外公群将于 8月8日前 正式关闭运营。公群担保关闭,不再提供海外业务担保。 为了保障您的切身利益，请于 8月15日前 联系官方客服 @wbkf 完成办理退押手续。 PS：自从胡小伟被劝反回美国，新币就一直在切割欧美那边的业务，果然洋人惹不起
我整理了一下 事情是真的 总损失在120万U 把手机里全部的U，还有NFT全部下走了，包括PC的也洗了一波 ID也确实在凌晨发生了两次转移，包括还有新币的交易专群 公群N小组222 @ttpg 天天PG 现在也暂停营业了 明天晚上凌晨1点应该会恢复，已经达成和解
云顶pc @yd28 股东叶门负责人叶明轩手机被小姐偷走，要求打50万u返还所有nft，否则解散此账号所有群组，据合伙人刚子透露损失了91万u，其中有49万u是云顶pc偷走
天天包网旗下 富贵娱乐 @fgyl 再次被入侵 被获取权限 可增加余额 富贵紧急维护，无任何损失，方阳无任何获利
Showing the 8 most recent of 8 posts we hold for @danbaoh. 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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“TG圈大事件” (@danbaoh), 2,888 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/danbaoh.
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.