Telegram RegisterThe public register of Telegram
Telegram profile photo for 李大帅的频道

Channel

李大帅的频道

@xiyangyangyuhuitailangchadang

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

11subscribers

-1 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-1001681317385
TypeChannel
Username@xiyangyangyuhuitailangchadang
Created19 March 2023 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live16 September 2026
Measurements held4
Confirmed unchanged4 times, most recently 16 September 2026
On Telegramt.me/xiyangyangyuhuitailangchadang

Growth

1113127 August 2026 — 12 subscribers12 August 2026 — 12 subscribers16 August 2026 — 13 subscribers23 August 2026 — 11 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net -1. 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 11:0411-2
16 Aug 2026, 04:2713+1
12 Aug 2026, 04:4512no change
7 Aug 2026, 09:3912first reading

Engagement

10 posts held, back to 19 March 2023 — 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 10 posts for this entry, the most recent from 10 December 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

10 Dec 2023, 02:47 UTCviews —

The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

6 Jun 2023, 04:16 UTC964 viewsread 12 August 2026

v反现 当天回 大量收,名下三网,淘宝多地址 对接源头🏐🏐🏐需要的来 @zfyazyzl

2 Jun 2023, 21:13 UTC≈1,320 viewsread 12 August 2026

v反 三网名下 淘宝多地址 对接源头🏐🏐🏐🏐🏐🏐🏐🏐🏐 @zfyazyzl

2 Jun 2023, 00:24 UTC717 viewsread 12 August 2026

v反 三网名下。对接源头🏐🏐🏐🏐🏐🏐🏐🏐🏐 快来 @zfyazyzl

28 May 2023, 14:37 UTC≈1,220 viewsread 12 August 2026

v反收单 对接源头 批量更便宜 @zfyazyzl 有需要个户机器人可以联系我

4 Apr 2023, 17:15 UTC≈1,400 viewsread 12 August 2026

♾个户全户✅婚姻记录 💻开房记录💠同住记录 📢名下号码📌名下房产 🔞犯罪在逃✅模糊找人 ♾冻结原因🔔社保地址 💬宽带地址☁️关联一切 🎙三网位置️▶️三网机主 🏐三网话单👁‍🗨定位找人 ⏰手机轨迹🎧快递地址 💛淘宝地址👌微信反查 🆘微信流水🎚支付流水 👑微好友提🙈新版人鬼 🍌护照正反💎名下车档 💤三页汽车🤴汽车违章 🔩支付码反☀️历史户籍 💟身份轨迹🏓小档汽车 🙅车辆轨迹🚛企业法人 💠身份正反♾飞火记录 👌银行反查💠支付宝机 🏐银行卡名🍎银行流水 需要联系: @zfyazyzl

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

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

“李大帅的频道” (@xiyangyangyuhuitailangchadang), 11 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/xiyangyangyuhuitailangchadang.

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.