Telegram RegisterThe public register of Telegram
Telegram profile photo for 深蓝网络数据

Channel

深蓝网络数据

@bsdwe1

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

1subscribers

+0 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-1003876417105
TypeChannel
Username@bsdwe1
Descriptionhttps://www.gomy-cloud.com/DC集团在逃名单
Created30 January 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live19 September 2026
Measurements held2
On Telegramt.me/bsdwe1

Growth

17 August 2026 — 1 subscribers15 August 2026 — 1 subscribers7 August 202615 August 2026
2 measurements spanning 8 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, 07:321no change
7 Aug 2026, 18:251first reading

Engagement

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

What this channel posts

Links
2

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

5 Aug 2026, 12:04 UTC1 viewsread 15 August 2026

小鸡视频资源采集站,秒拖秒播,精美封面,无弹窗,任意播放器播放,每日更新100+,数万资源一键入库,分类全面,国产日本欧美应有尽有,全网最快最全 技术24小时在线支持,可送模板+服务器端一整套、手机端+pc端 群:@xiaojizy 网站https://xjzy1.xyz

1 Aug 2026, 09:15 UTC2 viewsread 15 August 2026

https://t.me/msykk360 https://t.me/XBDB021 https://t.me/ytkj11 https://t.me/a897158 https://t.me/yufu369 https://t.me/kong8885 https://t.me/jb880cm https://t.me/huzhan1024 https://t.me/+oL1SZBgcpGE0ZWI1 https://t.me/rouji8888 https://t.me/roujiqunzu https://t.me/huichanyj

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

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.

“深蓝网络数据” (@bsdwe1), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/bsdwe1.

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.