Telegram RegisterThe public register of Telegram
Telegram profile photo for Apps推荐&抽奖&活动

Channel

Apps推荐&抽奖&活动

@AppsSweepstakesNews

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

8,509subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001413646788
TypeChannel
Username@AppsSweepstakesNews
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/AppsSweepstakesNews

Growth

8,5038,5188,510.56 August 2026 — 8,512 subscribers6 August 2026 — 8,514 subscribers10 August 2026 — 8,509 subscribers13 August 2026 — 8,518 subscribers16 August 2026 — 8,503 subscribers19 August 2026 — 8,509 subscribers8,5096 August 202619 August 2026
6 measurements spanning 14 days, net -3. 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 8,501–8,520 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 23:038,509+6
16 Aug 2026, 20:388,503-15
13 Aug 2026, 01:268,518+9
10 Aug 2026, 03:118,509-5
6 Aug 2026, 17:008,514+2
6 Aug 2026, 04:078,512first reading

Engagement

28 posts held, back to 6 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.9%
avg views ÷ 8,509 subscribers
Avg views / post
1,180
16 posts measured
Reaction rate
0.186%
reactions ÷ views · ER floor
Posts in window
17
of 28 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 13 of 16 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 18 August 2026
Posts held28 (6 June 202618 August 2026)
Views total18,874
Reactions total25
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Aug 2026, 18:49 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

51 reactions across 22 posts, in 4 distinct kinds. The most used accounts for 64.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3364.7%
🥰1223.5%
👍59.80%
👎11.96%

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 22 of the 28 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 51reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 28 most recent posts we hold, published 6 June 2026 to 18 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

18 Aug 2026, 14:21 UTC690 views3 reactionsread 19 August 2026
Photo

Photo, posted without a caption

🥰3

Signed 青木蚂蚁 🐜🐜🐜

15 Aug 2026, 13:26 UTC≈1,080 views2 reactionsread 19 August 2026

https://mp.weixin.qq.com/s/nZ86tAnNbTcl3M7pkda0cg?token=1385858978&clicktag=bar_comment&scene=294&clickpos=0&from_safari=1

2

Signed 青木蚂蚁 🐜🐜🐜

15 Aug 2026, 05:48 UTC881 views2 reactionsread 19 August 2026
Photo

https://mp.weixin.qq.com/s/awm8mfLIINtsjHY9Fhve0Q?token=1379177235&clicktag=bar_comment&scene=294&clickpos=0&from_safari=1 数独游戏欢迎来锤

👍2

Signed 青木蚂蚁 🐜🐜🐜

15 Aug 2026, 05:48 UTC≈1,020 viewsread 19 August 2026
Photo

Photo, posted without a caption

Signed 青木蚂蚁 🐜🐜🐜

15 Aug 2026, 04:51 UTC699 views1 reactionsread 19 August 2026
Forwarded from @InfuseEnterprise

Posted without readable text

1

Signed 青木蚂蚁 🐜🐜🐜

12 Aug 2026, 04:33 UTC796 views1 reactionsread 19 August 2026
Forwarded from @MakerNeo

https://apps.apple.com/tr/app/https-capture-traffic-decrypt/id6791491909 最近新发布了一个抓包的 APP,欢迎大家来试用。大约在一两个月以后会加入内购。到时候会给大家限免一下。 这个 APP 大约在 10 年前就写了一个版本,受限于当时的能力和时间限制没有完成。现在在 AI 的帮助下,给完善上架了。 目前App的功能还算比较完善,大部分抓包常用的功能都加入进来了,因为我自己也经常用,所以未来会不断地去迭代的。 最近打算把频道给启用起来,未来有很多活动信息什么之类的都统一往这里发,因为最近又做了好几个 App,未来群太多,不想加太多群的可以只看频道消息就行。

1

Signed 青木蚂蚁 🐜🐜🐜

12 Aug 2026, 02:11 UTC858 views3 reactionsread 19 August 2026
Forwarded from @InfuseEnterprise

Posted without readable text

👍21

Signed 青木蚂蚁 🐜🐜🐜

11 Aug 2026, 02:24 UTC≈1,020 views2 reactionsread 19 August 2026

https://mp.weixin.qq.com/s/f_YjXkD85AuT9equ3TfcfA?token=1622798525&clicktag=bar_comment&scene=294&clickpos=0&from_safari=1 Infuse:Enterprise更新Store版本

2

Signed 青木蚂蚁 🐜🐜🐜

1 Aug 2026, 11:15 UTC≈1,600 viewsread 19 August 2026
Forwarded from @conflux_news

Conflux 2.0 TF测试版 (加入测试 -> https://testflight.apple.com/join/6TM1SKUH) Build 10110 (iOS) * 原生杜比视界和杜比全景声(Beta, 需在设置开启对应选项) * 影片评分显示(TMDB、IMDb、烂番茄、META等等) * 全新的Onboard Flow * 媒体源增加手动测试可连接性入口 * 现在保存媒体源时会先测试可连接性 * 自定义快进快退间隔) * 影片评分显示(TMDB、IMDb、烂番茄、META等等) * 全新的Onboard Flow * 媒体源增加手动测试可连接性入口 * 现在保存媒体源时会先测试可连接性 * 自定义快进快退间隔 Build 10109 (iOS) * 适配iOS 27 * 首页banner增加电视剧推荐 * 优化首页和视频详情滑动性能 * 电视剧支持设置片头片尾时长,跳过片头片尾 * 字幕样式设置现在是真实

Signed 青木蚂蚁 🐜🐜🐜

1 Aug 2026, 05:05 UTC≈1,310 views1 reactionsread 19 August 2026

Beta 1 (5719) 更新内容 7/31/26 分享:光鸭云盘(GuangYaPan)云盘 播放:在网络不稳定的情况下优化了 HTTP 流媒体性能 播放:提升了与部分复杂或非标准 WebDAV 服务器配置的兼容性 播放:修复了带有外部 SMI 字幕的视频转码问题 播放:优化了在 Cloudflare 后端的 HTTP 服务器上的播放兼容性 预播放:重新添加了新版本选择按钮(Emby、Jellyfin、Plex) 通用:修复了双语言文件名的电视剧元数据解析问题 通用:新增对后台下载操作的原生支持(iOS 26+)

1

Signed 青木蚂蚁 🐜🐜🐜

30 Jul 2026, 14:49 UTC≈1,670 views2 reactionsread 18 August 2026
Photo

即将发布Infuse8.5 Store版本 新增 - 为 Emby、Jellyfin 和 Plex 新增转码选项 - 重新设计搜索页面,采用分类分组布局 - 新增跳转到上一部或下一部视频的选项 - 将最大音频偏移调整提升至 5 秒 改进 - 提升 Emby、Jellyfin 和 Plex“正在观看”列表的加载速度 - 改进 Emby、Jellyfin 和 Plex 的重定向处理 - 优化演员和制作人员列表的显示效果与排序 - 改进元数据和海报语言选择的处理方式 - 改进 Emby、Jellyfin 和 Plex 在直连模式下的搜索流程 - 提升与不支持范围请求的 WebDAV 服务器的兼容性 修复 - 修复因近期 API 变更导致的 Trakt 同步问题 - 修复在资料库模式下使用 Emby 或 Jellyfin 时演员和制作人员列表缺失的问题 - 修复跳过片头片尾功能相关问题 - 修复部分视频实时预览为空的问题 - 修复

2

Signed 青木蚂蚁 🐜🐜🐜

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

Citation-graph rank

Citation-graph rank — 731,925 of 1,563,849entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

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.

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

“Apps推荐&抽奖&活动” (@AppsSweepstakesNews), 8,509 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/AppsSweepstakesNews.

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.