Channel
@YYDL01
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002239620277 |
|---|---|
| Type | Channel |
| Username | @YYDL01 |
| Created | 25 August 2024 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/YYDL01 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 04:17 | 3 | -1 |
| 13 Aug 2026, 08:47 | 4 | no change |
| 7 Aug 2026, 13:41 | 4 | first reading |
5 posts held, back to 25 August 2024 — 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 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 5 posts for this entry, the most recent from 11 March 2026. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
【YY易游】代理部 pinned a photo
🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥 ⚽️【YY易游】代理扶持专享🏀 💰 免费扶持做代理拿分红达55%！ 💰 客户输100万，你拿佣金55万！ 💰 双倍加码人头奖，100万扶持奖励！ 💰赠送5连专属扶持活动，助力开户！ 【首存送35%复存送15%彩金】 【送888彩金流水活动】 【累计充值送18%彩金】 【送888包赔彩金活动】 【送5%负盈利彩金活动】 💰 所有场馆皆有流水奖励！ 💻开通代理获取【专属域名 & 独立代理后台】 ☎️代理资讯☎️ ✈️官方唯一小助手：@YY8984、@YY8984_bot
Photo, posted without a caption
Channel created
Showing the 5 most recent of 5 posts we hold for @YYDL01. 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.
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.
@YYDL01 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“【YY易游】代理部” (@YYDL01), 3 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/YYDL01.
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.