支持国家: 美国、阿尔及利亚、阿拉伯联合酋长国、埃及、澳大利亚、巴西、德国、俄罗斯、法国、哥伦比亚、荷兰、马来西亚、秘鲁、摩洛哥、墨西哥、南非、尼日利亚、沙特阿拉伯、土耳其、西班牙、以色列、意大利、印度、英国、智利

Channel
星光数据sdk/dpi/百万/全行业数据
@svip276
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,529subscribers
-2,534 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003664026141 |
|---|---|
| Type | Channel |
| Usernames | @svip276 @svip464 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/svip276 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 06:54 | 6,529 | -162 |
| 6 Sept 2026, 02:58 | 6,691 | -144 |
| 3 Sept 2026, 16:40 | 6,835 | -235 |
| 1 Sept 2026, 20:03 | 7,070 | -146 |
| 31 Aug 2026, 11:34 | 7,216 | -88 |
| 30 Aug 2026, 00:56 | 7,304 | -216 |
| 28 Aug 2026, 18:14 | 7,520 | -96 |
| 27 Aug 2026, 02:34 | 7,616 | -42 |
| 25 Aug 2026, 16:26 | 7,658 | -39 |
| 23 Aug 2026, 18:26 | 7,697 | -5 |
| 23 Aug 2026, 00:36 | 7,702 | -23 |
| 20 Aug 2026, 12:35 | 7,725 | -27 |
| 20 Aug 2026, 00:32 | 7,752 | -324 |
| 17 Aug 2026, 10:57 | 8,076 | no change |
| 17 Aug 2026, 10:48 | 8,076 | -504 |
| 14 Aug 2026, 02:16 | 8,580 | -21 |
| 13 Aug 2026, 14:27 | 8,601 | -410 |
| 10 Aug 2026, 20:17 | 9,011 | -52 |
| 10 Aug 2026, 16:17 | 9,063 | no change |
| 10 Aug 2026, 13:46 | 9,063 | first reading |
Engagement
20 posts held, back to 5 June 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 10 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1374.8%
- avg views ÷ 6,529 subscribers
- Avg views / post
- 89,800
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- 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.
| Window | Rolling 30 days · latest post in window 21 August 2026 |
|---|---|
| Posts held | 20 (5 June 2026 – 21 August 2026) |
| Views total | 538,554 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 22:13 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.
What this channel posts
- Video runtime
- 19s
- Average length
- 19s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
3 reactions across 1 post, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 66.7% | |
| 👍 | 1 | 33.3% |
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 3 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 5 June 2026 to 21 August 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
短信通道的机房已经对接好,只发移动,白跑,落地率百 85。 上次问过的小伙伴们火速联系
IM 通道每天正常运行,需要 bc 机房的盘总和代理速速甩单过来
红薯 UID转手机号码 快手 UID转手机号码 抖音 UID转手机号码 小单不要催,大单插队出 口嗨勿扰,此类产品增加频道多元化数据元素,符合本数据工作室全行业提取的初心 小红书提供直播间,房间号,截流停留多少时间以上的,或者是要正在购买的,看要哪个直接出。
全新移动dpi内测对接完毕 承接 贷款 股票 POS 网贷 等全行业可以承接做到更高维度的出数,提单规则跟移动一样,周天到周四提单!! 特别是可以跑灰,可以跑灰,六合,百家乐,棋牌等全面复工
实时洗抖音:开通 ID 实时洗快手:开通 昵称 id
灰产dpi是专门的线路,任何时候都不会影响出数跟下单
股票稳定输出
股票 翡翠 全行业洗微信去水军,筛选高活跃人群,专业处理,实时微信,支付宝,实时非垃圾过库可比
寻求专业引粉团队 私我
不忘初心,方得始终 山高路远,全凭良心 让时间去检验那些质疑。 专为电话盘口服务 花呗 白条 信用卡 储蓄卡 疑难杂症 转账风控 限额,存单 理财 基金需隔天到账的都可丢来尝试!没有华丽的语言 用心对待每一条鱼! 回款从不隔夜 从未有过飞单 黑单历史 可拉专群 可上押 可走担保 欢迎咨询!业务对接,拉专群 投诉建议找 @eeaaa https://t.me/+N4o-ULS_Mqo4OTg1
+888 🇺🇿NFT用户名 礼物🎁 租.售.收.抵押.放款快.利息低🪙 源头能量 天价收888号码 @s888
Showing the 12 most recent of 20 posts we hold for @svip276. 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“星光数据sdk/dpi/百万/全行业数据” (@svip276), 6,529 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/svip276.
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.