Telegram RegisterThe public register of Telegram
Telegram profile photo for TGBC博彩娱乐公告台

Channel

TGBC博彩娱乐公告台

@xwgx1

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

1subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003928828847
TypeChannel
Username@xwgx1
Description博彩娱乐|活动公告|代理合作|验证进群|奖励说明
Created10 April 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live28 August 2026
Measurements held2
On Telegramt.me/xwgx1

Growth

113 August 2026 — 1 subscribers15 August 2026 — 1 subscribers13 August 202615 August 2026
2 measurements spanning 2 days. 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
15 Aug 2026, 10:011no change
13 Aug 2026, 02:331first reading

Engagement

10 posts held, back to 10 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 10 posts for this entry, the most recent from 11 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

11 Apr 2026, 04:28 UTC1 viewsread 15 August 2026

📢 TGBC博彩娱乐公告台 本频道主要用于发布: 博彩娱乐活动公告|代理合作信息|验证进群说明|奖励规则通知 适合人群: 优质代理|项目方|广告主|资源方|真实玩家 如需交流合作,请进: 资源合作圈:@TGBC 如需办理相关业务,请联系: 官方助手:@TGBCzsBot 所有规则、活动、入口与通知, 均以本频道与官方助手公布内容为准。 🏆 势域生态 @SHIYU

11 Apr 2026, 04:21 UTCviews —

TGBC博彩娱乐公告台 pinned «博彩娱乐|活动公告|代理合作|验证进群|奖励说明 资源合作圈:@TGBC|官方助手:@TGBCzsBot 🏆 势域生态 @SHIYU»

11 Apr 2026, 04:21 UTC1 viewsread 15 August 2026

博彩娱乐|活动公告|代理合作|验证进群|奖励说明 资源合作圈:@TGBC|官方助手:@TGBCzsBot 🏆 势域生态 @SHIYU

10 Apr 2026, 17:41 UTC1 viewsread 15 August 2026

📢 博彩娱乐资源合作入口 这里主要发布: 博彩娱乐活动公告 代理合作信息 验证进群说明 奖励规则通知 如需进入 TGBC 资源合作圈交流: @TGBC 如需办理账号、奖励、审核相关业务: @TGBCzsBot 🏆 势域生态 @SHIYU

10 Apr 2026, 17:38 UTC1 viewsread 15 August 2026

📢 代理合作通道开放 TGBC资源合作圈现面向 优质代理 开放定向准入通道。 日销量不低于5000,可申请审核入群。 群内主要方向: 博彩娱乐资源合作|广告对接|渠道互通|项目交流 资源合作圈: @TGBC 官方办理入口: @TGBCzsBot 🏆 势域生态 @SHIYU

10 Apr 2026, 17:35 UTC1 viewsread 15 August 2026

📢 验证进群说明 TGBC资源合作圈现开放验证进群。 满足验证要求,审核通过后可获得 88奖励 并进群。 未达标也可按活动规则参与,部分活动为 充1000送88。 本群主要面向: 博彩娱乐相关代理、项目方、广告主、资源方、真实玩家 交流合作请进: @TGBC 办理与规则查看: @TGBCzsBot

10 Apr 2026, 17:32 UTCviews —

TGBC博彩娱乐公告台 pinned «📢 TGBC博彩娱乐公告台 本频道主要用于发布: 博彩娱乐活动公告|代理合作信息|验证进群说明|奖励规则通知 适合人群: 优质代理|项目方|广告主|资源方|真实玩家 如需交流合作,请进: 资源合作圈:@TGBC 如需办理相关业务,请联系: 官方助手:@TGBCzsBot 所有规则、活动、入口与通知, 均以本频道与官方助手公布内容为准。 🏆 势域生态 @SHIYU»

10 Apr 2026, 17:32 UTC1 viewsread 15 August 2026

📢 TGBC博彩娱乐公告台 本频道主要用于发布: 博彩娱乐活动公告|代理合作信息|验证进群说明|奖励规则通知 适合人群: 优质代理|项目方|广告主|资源方|真实玩家 如需交流合作,请进: 资源合作圈:@TGBC 如需办理相关业务,请联系: 官方助手:@TGBCzsBot 所有规则、活动、入口与通知, 均以本频道与官方助手公布内容为准。 🏆 势域生态 @SHIYU

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

Citation-graph rank

Citation-graph rank — 1,196,447 of 1,625,404entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“TGBC博彩娱乐公告台” (@xwgx1), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/xwgx1.

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.