Telegram RegisterThe public register of Telegram
Telegram profile photo for 币游娱乐-大奖连连爆

Channel

币游娱乐-大奖连连爆

@ByyLBDJ

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

144subscribers

-12 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002313614916
TypeChannel
Username@ByyLBDJ
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 13 September 2026
On Telegramt.me/ByyLBDJ

Growth

1441561507 August 2026 — 156 subscribers8 August 2026 — 156 subscribers15 August 2026 — 152 subscribers29 August 2026 — 146 subscribers5 September 2026 — 144 subscribers7 August 20265 September 2026
5 measurements spanning 29 days, net -12. 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 142–158 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 18:17144-2
29 Aug 2026, 13:13146-6
15 Aug 2026, 10:14152-4
8 Aug 2026, 18:30156no change
7 Aug 2026, 13:34156first reading

Engagement

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

Recent posts

7 Aug 2026, 17:27 UTC11 viewsread 8 August 2026
Photo

🥳🥳🥳恭喜用户***45557🥳🥳🥳 🎉🎉🎉成功提款2800USDT🎉🎉🎉

7 Aug 2026, 16:24 UTC11 viewsread 8 August 2026
Photo

🥳🥳🥳恭喜用户***45557🥳🥳🥳 🎉🎉🎉成功提款10700USDT🎉🎉🎉

16 Jul 2026, 14:15 UTC91 viewsread 8 August 2026
Photo

🥳🥳🥳恭喜用户***45557🥳🥳🥳 🎉🎉🎉成功提款8000USDT🎉🎉🎉

16 Jul 2026, 12:05 UTC85 viewsread 8 August 2026
Photo

🥳🥳🥳恭喜用户***45557🥳🥳🥳 🎉🎉🎉成功提款20000USDT🎉🎉🎉

28 Jun 2026, 15:44 UTC132 viewsread 8 August 2026
Photo

🥳🥳🥳恭喜用户***82196🥳🥳🥳 🎉🎉🎉成功提款8194USDT🎉🎉🎉

28 Jun 2026, 12:35 UTC122 viewsread 8 August 2026
Photo

发大大大大大大水 家人们 恭喜🎉老板😀😀爆奖😀😀😀😀倍 喜提😀😀😃😀😀 刺激 ‼️牛坏啦📈 真的是太欧气啦 财富通道 @bayl_bot 💫

22 Jun 2026, 18:27 UTC117 viewsread 8 August 2026
Photo

🥳🥳🥳恭喜用户***45557🥳🥳🥳 🎉🎉🎉成功提款4900USDT🎉🎉🎉

20 Jun 2026, 13:48 UTC109 viewsread 8 August 2026
Photo

💳 充值|投注|结算|提款 丝滑完成 😀USDT直接投注,高额反水😀 满足充值金额1倍有效额度丝滑出款 支持 @PPAY @OKPAY @FLLQB 等钱包红包/转账 唯一客服: @ZALO

18 Jun 2026, 10:35 UTC109 viewsread 8 August 2026
Photo

💳 充值|投注|结算|提款 丝滑完成 😀USDT直接投注,高额反水😀 满足充值金额1倍有效额度丝滑出款 支持 @PPAY @OKPAY @FLLQB 等钱包红包/转账 唯一客服: @ZALO

18 Jun 2026, 10:02 UTC94 viewsread 8 August 2026
Forwarded from @TDDBliucheng

担保圈风起云涌:群雄逐鹿,谁主沉浮? —— 唯有必安,稳如泰山。 各位老板、各位公群兄弟、各位必安家人: 近期担保圈消息不断,行业环境风起云涌,市场信心也在一次次波动中接受考验。 新小平台跑路不断:如超乖、永盛、太平洋等担保均已跑路。套路其实大同小异:均是打着免租金、低价、福利、扶持等资金盘模式,吸引公群入驻上押,最后圈钱、卷款、跑路。 行业巨头同样动荡不安:汇旺倒闭,土豆倒闭,新币暴雷,市场信心持续受挫。网络盛传:新币被国际制裁,股东被抓,地址冻结数千万,联合公群项目陷入资金盘及理赔纠纷,担保平台及股东负债,无数公群已纷纷退减。(真假自辨,但愿安好 ) 越是行业动荡,越能看出谁在长期经营。 越是市场洗牌,越能看出谁才值得托付。 越是人心浮动,越要选择真正稳定、可靠、有持续服务能力的平台。必安监察历史神作《浅谈担保平台的选择之道》含金量还在持续上升!🔝 必安担保一路走来,靠的不是一时噱头,不是

14 Jun 2026, 10:01 UTC108 viewsread 8 August 2026
Photo

🥳🥳🥳恭喜用户***60904🥳🥳🥳 🎉🎉🎉成功提款6888USDT🎉🎉🎉

Showing the 12 most recent of 15 posts we hold for @ByyLBDJ. 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 2 registered channels — 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.

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

“币游娱乐-大奖连连爆” (@ByyLBDJ), 144 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/ByyLBDJ.

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.