Telegram RegisterThe public register of Telegram
Telegram profile photo for 阿丹V代挂通知频道

Channel

阿丹V代挂通知频道

@ad5269

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

208subscribers

+26 since we began measuring on 4 November 2026

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

Register entry

Telegram ID-1003984521163
TypeChannel
Username@ad5269
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 November 2026
Last confirmed live13 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/ad5269

Growth

1822081954 November 2026 — 182 subscribers4 November 2026 — 185 subscribers13 November 2026 — 208 subscribers4 November 202613 November 2026
3 measurements spanning 9 days, net +26. 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 178–212 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 02:27208+23
4 Nov 2026, 17:19185+3
4 Nov 2026, 02:22182first reading

Engagement

20 posts held, back to 29 October 2026 — 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.

ERR · 30 days
55.2%
avg views ÷ 208 subscribers
Avg views / post
115
20 posts measured
Reaction rate
1.34%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held20 (29 October 2026 – 3 November 2026)
Views total2,295
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 02:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 29 October 2026 to 3 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 13:53 UTC48 viewsread 4 November 2026

晚上位置充足 晚上位置充足 直上活码不需要中转,6位,7位 小程序 都有位置 💎💎💎💎💎✈️ @ad52699

3 Nov 2026, 06:25 UTC70 viewsread 4 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 有量都可以来聊聊 价格包你满意 可以预付 可以担保 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

3 Nov 2026, 04:02 UTC69 viewsread 4 November 2026

🦈陌陌聊天室 🦈陌陌拉群 🦈陌陌动态 🦈快手自热 🦈快手语音厅 🦈抖音协议采集 🦈抖音点赞 🦈抖音自热 🦈快手采集 🦈小红书自热 🦈王者 🦈地推浏览器 🦈V站街 🦈小红书动态 🦈小平台 🦈抖音截流粉丝群 🦈抖音热评 🦈抖音直播 🦈探探 🚨🚨 以上渠道 天马 / Q群/cpa 都有 全都有 📱📱📱📱📱📱📱📱⬇️ 🦈 @baisha9999

2 Nov 2026, 14:35 UTC90 viewsread 4 November 2026

晚上位置充足 晚上位置充足 直上活码不需要中转,6位,7位 小程序 都有位置 💎💎💎💎💎✈️ @ad52699

2 Nov 2026, 06:25 UTC107 viewsread 4 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 有量都可以来聊聊 价格包你满意 可以预付 可以担保 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

2 Nov 2026, 04:02 UTC96 viewsread 4 November 2026

🦈陌陌聊天室 🦈陌陌拉群 🦈陌陌动态 🦈快手自热 🦈快手语音厅 🦈抖音协议采集 🦈抖音点赞 🦈抖音自热 🦈快手采集 🦈小红书自热 🦈王者 🦈地推浏览器 🦈V站街 🦈小红书动态 🦈小平台 🦈抖音截流粉丝群 🦈抖音热评 🦈抖音直播 🦈探探 🚨🚨 以上渠道 天马 / Q群/cpa 都有 全都有 📱📱📱📱📱📱📱📱⬇️ 🦈 @baisha9999

1 Nov 2026, 13:27 UTC117 viewsread 4 November 2026
Photo

号扛不抗 自己看 全部是国内私人老号 嘎嘎稳定 代挂认准阿丹

1 Nov 2026, 12:44 UTC113 viewsread 4 November 2026

25u一天 6字母 1字母5数字 3字母3数字 6,7位纯数字绑定q的 (包号包头像,死了包补) 头像直上活码(35u一天) 💎💎💎💎💎✈️ @ad52699

1 Nov 2026, 08:48 UTC125 viewsread 4 November 2026

🦈陌陌聊天室 🦈陌陌拉群 🦈陌陌动态 🦈快手自热 🦈快手语音厅 🦈抖音协议采集 🦈抖音点赞 🦈抖音自热 🦈快手采集 🦈小红书自热 🦈王者 🦈地推浏览器 🦈V站街 🦈小红书动态 🦈小平台 🦈抖音截流粉丝群 🦈抖音热评 🦈抖音直播 🦈探探 🚨🚨 以上渠道 天马 / Q群/cpa 都有 全都有 📱📱📱📱📱📱📱📱⬇️ 🦈 @baisha9999

1 Nov 2026, 06:25 UTC113 viewsread 4 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 有量都可以来聊聊 价格包你满意 可以预付 可以担保 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

31 Oct 2026, 11:26 UTC137 viewsread 4 November 2026

💎💎💎💎微信代挂业务 📱📱📱📱 稳定耐造-包头像-死号包补-可定制 头像直上活码(35u一天) 可以挂小程序,浏览器,q群,都可以挂,(25u一天) 6字母 1字母5数字 3字母3数字 📱 📱 📱 6位纯数字绑定q的 7位纯数字绑定q的 以上全部货充足 白班客服,夜班客服 ⚡️为您全程保驾护航 💎💎💎💎💎✈️ @ad52699

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

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.

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

“阿丹V代挂通知频道” (@ad5269), 208 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/ad5269.

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.