Telegram RegisterThe public register of Telegram
Telegram profile photo for 赌场圈曝光

Channel

赌场圈曝光

@duchangquanBG

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

16subscribers

-1 since we began measuring on 11 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001509554231
TypeChannel
Username@duchangquanBG
Description赌场信息交流圈 出码换汇,美女房间,抵押典当 打击一切搞事行为,多多曝光以及悬赏,打造绿色行情 交流群组: https://t.me/duchangquan 发布内容/担保交易/上午洽谈: @sabo16888
Created19 December 2022measured — dated from the channel’s first post
First recorded13 September 2026
Last confirmed live13 September 2026
Measurements held3
On Telegramt.me/duchangquanBG

Growth

161716.511 September 2026 — 17 subscribers13 September 2026 — 16 subscribers13 September 2026 — 16 subscribers11 September 202613 September 2026
3 measurements spanning 2 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 16–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 17:2316no change
13 Sept 2026, 14:0216-1
11 Sept 2026, 23:1717first reading

Engagement

4 posts held, back to 19 December 2022the 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 4 posts for this entry, the most recent from 19 December 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1

Lifetime counters from Telegram’s own channel header, read 13 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.

Recent posts

19 Dec 2022, 13:46 UTC314 viewsread 13 September 2026
Photo

此人人品极差,欠钱跑路,赌场接回来,因为信任,借钱给他,背着同事的名号借钱周转,欠几十万跑路,如果有人知道详细地址,请告诉我,有重金感谢, @ciyu118

Showing the 4 most recent of 4 posts we hold for @duchangquanBG. 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.

Mentions

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.

Cite this entry

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 13 September 2026 — this entry's latest reading, not the date you are reading this.

“赌场圈曝光” (@duchangquanBG), 16 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/duchangquanBG.

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.