Channel
@lwqzbg
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2,481subscribers
-51 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001174425667 |
|---|---|
| Type | Channel |
| Username | @lwqzbg |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/lwqzbg |
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 73% 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 |
|---|---|---|
| 15 Sept 2026, 08:56 | 2,481 | -12 |
| 11 Sept 2026, 13:36 | 2,493 | -12 |
| 7 Sept 2026, 07:35 | 2,505 | -21 |
| 2 Sept 2026, 12:44 | 2,526 | -6 |
| 30 Aug 2026, 03:15 | 2,532 | no change |
| 30 Aug 2026, 03:00 | 2,532 | first reading |
5 posts held, back to 30 March 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 5 posts for this entry, the most recent from 2 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
骗子用户名:奥斯卡 L 向日葵 骗子ID:@peng969 @ff9989988 骗子说明:曝光这个骗子公司 已经被多人曝光 大家避雷 群里还有一个向日葵没有id 看来做好跑路打算都没有ID 第一次结账 第二次说漏发账单压账单要财务上班再结账 第三次就是第二次的晚上给他打第二天说薅羊毛没产值就是假粉 被跑路🐶骗钱一万多元 大家避雷理智一点一定要这种跑路🐶预付担保再打粉不然吃亏的是我们手子 骗子U地址: TWkFnGbBNjiNzbLkwHZPt5XwtPCZWPNbe8 建议:建议走老王担保 原因:曝光这个骗子公司 已经被多人曝光 大家避雷 群里还有一个向日葵没有id 看来做好跑路打算都没有ID 第一次结账 第二次说漏发账单压账单要财务上班再结账 第三次就是第二次的晚上给他打第二天说薅羊毛没产值就是假粉 被跑路🐶骗钱一万多元 大家避雷理智一点一定要这种跑路🐶预付担保再打粉不然吃亏的是我们手子 成本奎不说还倒贴一万 举报人用户名:…
骗子用户名: @shuazi00000309@Kitty8888880 @cn2025 @mumarensheng 骗子ID: 骗子说明:傻逼小盘，两天跑了我1700多粉，头一天说出三单了，让我加量，后面两天直接跑路了，还做假图，跟我说的不扣包结，结果说的话和放屁没什么区别，望各大粉商工作室避坑，这种垃圾盘谁都不要合作 骗子U地址: 建议:建议走老王担保 原因: 举报人用户名:@xiaobai8883
骗子用户名:@Wj168168168 骗子ID: 骗子说明:验号要十几二十分钟 还准时说不行，什么没流量，没流量第一时间就可以说吧 就是单纯白嫖号用 骗子U地址: 建议:建议走老王担保 原因:TT语音35级私人老号 举报人用户名:@jinghong86
骗子用户名:田田 骗子ID:@nidtian 骗子说明:骗我800u预付 骗子U地址:TDY5acvp5p6xrAS1A5EZqYuwMejuYHhwM1 建议:建议走老王担保 原因: 举报人用户名:@Gdc_118
骗子用户名:大圣查粉 骗子ID:@laddiew @laddieH @laoyaoH 骗子说明:他妈的臭傻B查粉的，给钱就判假，草你妈刀我那么多粉 骗子U地址: 建议:建议走老王担保 原因: 举报人用户名:
Showing the 5 most recent of 5 posts we hold for @lwqzbg. 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 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“【老王担保】骗子曝光” (@lwqzbg), 2,481 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/lwqzbg.
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.