Telegram RegisterThe public register of Telegram
Telegram profile photo for 钻石爆奖投稿区

Channel

钻石爆奖投稿区

@ZSBJTG

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

7,209subscribers

-527 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003438981949
TypeChannel
Username@ZSBJTG
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/ZSBJTG

Growth

7,2097,7837,4969 August 2026 — 7,736 subscribers9 August 2026 — 7,735 subscribers12 August 2026 — 7,783 subscribers16 August 2026 — 7,645 subscribers19 August 2026 — 7,551 subscribers22 August 2026 — 7,514 subscribers25 August 2026 — 7,462 subscribers28 August 2026 — 7,451 subscribers31 August 2026 — 7,385 subscribers3 September 2026 — 7,278 subscribers8 September 2026 — 7,209 subscribers9 August 20268 September 2026
11 measurements spanning 31 days, net -527. 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 7,123–7,869 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 23:407,209-69
3 Sept 2026, 18:187,278-107
31 Aug 2026, 04:137,385-66
28 Aug 2026, 06:247,451-11
25 Aug 2026, 09:227,462-52
22 Aug 2026, 15:137,514-37
19 Aug 2026, 09:257,551-94
16 Aug 2026, 08:067,645-138
12 Aug 2026, 11:457,783+48
9 Aug 2026, 08:317,735-1
9 Aug 2026, 06:167,736first reading

Engagement

87 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 10 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.94%
avg views ÷ 7,209 subscribers
Avg views / post
140
62 posts measured
Reaction rate
0.58%
reactions ÷ views · ER floor
Posts in window
62
of 87 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 17 of 62 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held87 (5 August 202628 August 2026)
Views total8,680
Reactions total17
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 22:49 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
3m 52s
Average length
1m 17s

Measured directly from 3 videos 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.

Reaction mix

17 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 88.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1588.2%
💩211.8%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 17 of the 87 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 87 most recent posts we hold, published 5 August 2026 to 28 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Aug 2026, 16:03 UTC25 viewsread 28 August 2026
Forwarded from @zsjtvipPhoto

💎 钻石娱乐 8月29号福利红包如下💎 🧧 福利红包①:日累计充值20U可领取 🧧 福利红包②:电子流水52U幸运抽奖 🧧 福利红包③:电子流水128U 可领取 🧧 福利红包④:电子流水388U 可领取 📊 当日电子流水查询说明 ① 点击【投注记录】 ② 点击【游戏类型报表】 ③ 即可查看当日电子流水 ━━━━━━━━━━━━━━ 💡 K = 000 📌 例如:1367K ➡️ 1367 后面加 000 ➡️ 1367K = 1,367,000 ➡️ 等于 136.7万流水

28 Aug 2026, 03:22 UTC197 views0 reactionsread 28 August 2026
Photo

💎 钻石娱乐 di88.vip 🩸🩸恭喜钻石玩家10****9 本金200U 进场游戏PG麻将胡了 投注5万 爆奖1003万 奖励18万😊 投注返利高达1.9% (全网最高返利) 爆奖投稿规则登录平台查看活动规则 ➖➖➖➖➖➖➖➖➖➖➖ 😄钻石爆奖投稿(投注2万起) 😄爆奖200倍以上 奖励18万 😄爆奖500倍以上 奖励38万 😄爆奖1000 倍以上 奖励88万 😄爆奖5000倍以上 奖励188万 😄爆奖10000倍以上 奖励288万

27 Aug 2026, 16:03 UTC30 viewsread 28 August 2026
Forwarded from @zsjtvipPhoto

💎 钻石娱乐 8.28号福利红包如下 💎 🔥 电子52U流水幸运豹千万彩金抽奖 🧧 福利红包①: 当日充值2U可领取 🧧 福利红包②:当日充值50U可领取 🧧 福利红包③:当日流水188u可领取

27 Aug 2026, 13:31 UTC20 viewsread 28 August 2026
Forwarded from @zsjtvip

钻石娱乐🧧|爆率最高 🔥 2U起充|低门槛更方便 💰 支持钱包 OKPay|MPay|福利来|冷钱包 💱 固定汇率 1U = 2.5万越南盾 🌍 12种语言自由切换 ⚡ 充值便捷|提款快速 🕐 24小时提款服务 🚀 极速处理|快速到账 🎁 每日福利|精彩不断 🐆 每日电子流水52U 🏆 即可参与千万彩金抽奖 📢 关注钻石中文社区 👉 @zsjtvip 🧧 红包福利抢先领取 💎 钻石娱乐 2U起充 · 福利不断 🧧随机金额(0-12345678): 12345678 VND ✅ 剩余: 288/288 📝 备注: 本免费红包不可以购买免费游戏最高提款100万多余清零。

27 Aug 2026, 07:36 UTC267 views1 reactionsread 28 August 2026
Video

💎 钻石娱乐 di88.vip 🩸🩸恭喜钻石玩家10****7 本金74U 进场游戏PG宝石矿工 投注2万 爆奖1032万 奖励18万😊 投注返利高达1.9% (全网最高返利) 爆奖投稿规则登录平台查看活动规则 ➖➖➖➖➖➖➖➖➖➖➖ 😄钻石爆奖投稿(投注2万起) 😄爆奖200倍以上 奖励18万 😄爆奖500倍以上 奖励38万 😄爆奖1000 倍以上 奖励88万 😄爆奖5000倍以上 奖励188万 😄爆奖10000倍以上 奖励288万

1

27 Aug 2026, 06:00 UTC225 views1 reactionsread 28 August 2026
Photo

💎 钻石娱乐 di88.vip 🩸🩸恭喜钻石玩家10****9 本金78U 进场游戏PG宝石矿工 投注6万 爆奖1422万 奖励18万😊 投注返利高达1.9% (全网最高返利) 爆奖投稿规则登录平台查看活动规则 ➖➖➖➖➖➖➖➖➖➖➖ 😄钻石爆奖投稿(投注2万起) 😄爆奖200倍以上 奖励18万 😄爆奖500倍以上 奖励38万 😄爆奖1000 倍以上 奖励88万 😄爆奖5000倍以上 奖励188万 😄爆奖10000倍以上 奖励288万

1

27 Aug 2026, 05:59 UTC203 views1 reactionsread 28 August 2026
Photo

💎 钻石娱乐 di88.vip 🩸🩸恭喜钻石玩家10****5 本金204U 进场游戏PG赏金大对决 投注3万 爆奖708万 奖励18万😊 投注返利高达1.9% (全网最高返利) 爆奖投稿规则登录平台查看活动规则 ➖➖➖➖➖➖➖➖➖➖➖ 😄钻石爆奖投稿(投注2万起) 😄爆奖200倍以上 奖励18万 😄爆奖500倍以上 奖励38万 😄爆奖1000 倍以上 奖励88万 😄爆奖5000倍以上 奖励188万 😄爆奖10000倍以上 奖励288万

1

27 Aug 2026, 05:58 UTC194 views1 reactionsread 28 August 2026
Photo

💎 钻石娱乐 di88.vip 🩸🩸恭喜钻石玩家10****0 本金105U 进场游戏PG赏金大对决 投注3万 爆奖2253万 奖励38万😊 投注返利高达1.9% (全网最高返利) 爆奖投稿规则登录平台查看活动规则 ➖➖➖➖➖➖➖➖➖➖➖ 😄钻石爆奖投稿(投注2万起) 😄爆奖200倍以上 奖励18万 😄爆奖500倍以上 奖励38万 😄爆奖1000 倍以上 奖励88万 😄爆奖5000倍以上 奖励188万 😄爆奖10000倍以上 奖励288万

1

27 Aug 2026, 05:57 UTC229 views1 reactionsread 28 August 2026
Photo

💎 钻石娱乐 di88.vip 🩸🩸恭喜钻石玩家10****2 本金400U 进场游戏PG宝石矿工 投注3万 爆奖872万 奖励18万😊 投注返利高达1.9% (全网最高返利) 爆奖投稿规则登录平台查看活动规则 ➖➖➖➖➖➖➖➖➖➖➖ 😄钻石爆奖投稿(投注2万起) 😄爆奖200倍以上 奖励18万 😄爆奖500倍以上 奖励38万 😄爆奖1000 倍以上 奖励88万 😄爆奖5000倍以上 奖励188万 😄爆奖10000倍以上 奖励288万

1

26 Aug 2026, 16:03 UTC32 viewsread 28 August 2026
Forwarded from @zsjtvipPhoto

💎 钻石娱乐 8.27号福利红包如下 💎 🔥 电子52U流水幸运豹千万彩金抽奖 🧧 福利红包①: 当日充值2U可领取 🧧 福利红包②:当日充值50U可领取 🧧 福利红包③:当日流水188u可领取

26 Aug 2026, 09:56 UTC37 viewsread 28 August 2026
Forwarded from @zsjtvipPhoto

千万彩金红包等你来抢 钻石回馈福利通知: 时间:27号晚上9点 地点:钻石俱乐部 金额:千万彩金红包 领取要求:VIP2 ⚠️: 20:59分截止进群

Showing the 12 most recent of 87 posts we hold for @ZSBJTG. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“钻石爆奖投稿区” (@ZSBJTG), 7,209 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/ZSBJTG.

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.