Telegram RegisterThe public register of Telegram
Telegram profile photo for 钻石福利群预告

Channel

钻石福利群预告

@zscjq

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

21subscribers

-2,173 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1004403576141
TypeChannel
Username@zscjq
Created12 August 2026 — measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live4 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/zscjq

Topic

Gambling & betting — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Growth

12,1941,097.512 August 2026 — 2,194 subscribers13 August 2026 — 1 subscribers15 August 2026 — 1 subscribers19 August 2026 — 9 subscribers25 August 2026 — 6 subscribers1 September 2026 — 11 subscribers10 September 2026 — 12 subscribers4 October 2026 — 21 subscribers2112 August 20264 October 2026
8 measurements spanning 53 days, net -2,173. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 05:5521+9
10 Sept 2026, 14:3612+1
1 Sept 2026, 20:3511+5
25 Aug 2026, 11:026-3
19 Aug 2026, 09:479+8
15 Aug 2026, 08:461no change
13 Aug 2026, 02:461-2,193
12 Aug 2026, 17:152,194first reading

Engagement

5 posts held, back to 12 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 5 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Aug 2026, 18:19 UTC7 viewsread 15 August 2026
Forwarded from @zsjtvip

通知: VIP2用户及以上登录就可以领取红包雨。

14 Aug 2026, 16:03 UTC7 viewsread 15 August 2026
Forwarded from @zsjtvipPhoto

🔥 每日排名幸运豹千万彩金幸运抽奖 🧧 福利红包①: 当日充值2U可领取 🧧 福利红包②:当日充值50U可领取 🧧 福利红包③:当日流水188u可领取

14 Aug 2026, 09:02 UTC12 viewsread 15 August 2026
Forwarded from @zsjtvip

🎁🔥 钻石娱乐|15亿红包雨回馈 🔥🎁 ━━━━━━━━━━━━━━━━━━ 📅 活动时间:8月14日-8月16日 🧧 每日红包雨:5亿彩金 💰 三天累计:15亿彩金 🎮 登录平台领取 🎯 红包随机掉落|先到先得 ━━━━━━━━━━━━━━━━━━ 💎 彩金仅限电子游戏使用 💎 需完成 5倍电子游戏有效流水 方可提款 ⚠️ 多账号重复领取,平台有权冻结相关账号,并取消彩金及收益。 ━━━━━━━━━━━━━━━━━━ 🔥 连续3天|每日5亿红包雨 🎁 15亿彩金豪爽回馈! 💎 钻石娱乐|登录即抢

13 Aug 2026, 16:06 UTC10 viewsread 15 August 2026
Forwarded from @zsjtvipPhoto

💎 钻石娱乐 8.14号福利红包如下 💎 🔥每日排名幸运豹千万彩金幸运抽奖 🧧 福利红包①: 当日充值2U可领取 🧧 福利红包②:立即领取 8888彩金 🧧 福利红包③:再次领取 38888彩金 🧧 福利红包④:继续领取 88888彩金 🧧 福利红包⑤:额外领取 222222彩金 💎 最后一舞,就在钻石娱乐(爆爆爆) 💎 今日精彩开启,等待你的高光时刻!

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

Forward network

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.

Mentions

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.

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

“钻石福利群预告” (@zscjq), 21 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/zscjq.

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.