Telegram RegisterThe public register of Telegram

Channel

Audi · 两元之神

@AudiABC

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

3,836subscribers

+300 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002060596770
TypeChannel
Username@AudiABC
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/AudiABC

Growth

3,5363,8363,6867 August 2026 — 3,536 subscribers7 August 2026 — 3,536 subscribers8 August 2026 — 3,685 subscribers11 August 2026 — 3,836 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net +300. 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 3,491–3,881 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 01:053,836+151
8 Aug 2026, 08:353,685+149
7 Aug 2026, 12:483,536no change
7 Aug 2026, 12:263,536first reading

Engagement

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

ERR · 30 days
19.7%
avg views ÷ 3,836 subscribers
Avg views / post
754
14 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
14
of 14 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held14 (5 August 20267 August 2026)
Views total10,561
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:09 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.

Recent posts

7 Aug 2026, 20:02 UTC102 viewsread 7 August 2026
Photo

🍭 新项目上线⑧日,感谢大家的关注与支持,目前已有 800+ 用户参与体验。 公益单透卡密:AudiWEHDJXBDKXJXAKBS 至臻版追锁赞助版提卡地址: https://shop.zmfaka.cn/shop/Audi 🍭 官方客服:@CNAZHO

7 Aug 2026, 20:02 UTC103 viewsread 7 August 2026
Photo

🍭 新项目上线⑧日,感谢大家的关注与支持,目前已有 800+ 用户参与体验。 公益单透卡密:AudiWEHDJXBDKXJXAKBS 至臻版追锁赞助版提卡地址: https://shop.zmfaka.cn/shop/Audi 🍭 官方客服:@CNAZHO 

7 Aug 2026, 07:38 UTC554 viewsread 7 August 2026

如当前卡网无法正常打开,请切换至全新卡网进行使用。 老卡网:https://shop.zmfaka.cn/shop/Audi 新卡网:https://shop.368fk.cn/shop/Audi 如遇其他问题,请及时联系在线客服处理。

7 Aug 2026, 04:01 UTC700 viewsread 7 August 2026
Photo

🍭 新项目上线⑦日,感谢大家的关注与支持,目前已有 800+ 用户参与体验。 公益单透卡密:AudiWEHDJXBDKXJXAKBS 至臻版追锁赞助版提卡地址: https://shop.zmfaka.cn/shop/Audi 🍭 官方客服:@CNAZHO

7 Aug 2026, 03:50 UTC412 viewsread 7 August 2026

如需使用至臻版 请先使用单透版本尝试是否适配该机型

7 Aug 2026, 03:45 UTC423 viewsread 7 August 2026
Photo

Audi云端更新V1.5🍭 1.更新断点无后 2.更新存号功能 3.修复古墓无效果问题 4.更新巡查预警功能 5.修复首局初始化次局无效果问题 7.修复部分用户卡死问题 🍭请前往APP直接安装或置顶安装 🍭使用时请勿挂载VPN 🍭点我跳转安装包 官方频道 https://t.me/AudiABC/15020 公益单透卡密:AudiWEHDJXBDKXJXAKBS 至臻版追锁赞助版提卡地址: https://shop.zmfaka.cn/shop/Audi 🍭 官方客服:@CNAZHO

7 Aug 2026, 01:39 UTC489 viewsread 7 August 2026

初始化加载异常说明 临时解决方法: 退出程序后重新执行一次程序; 进入特训岛后点击初始化绘制; 如需进入实战,请先进入实战,再点击初始化绘制。 该问题已定位,将在下个版本彻底修复,请大家耐心等待。 下个版本更新内容 🍭 修复初始化加载异常 🍭 新增断点无后 🍭 新增巡查预警功能 🍭 新增存号功能 🍭 修复目前已知问题,进一步提升整体稳定性与流畅性

6 Aug 2026, 03:08 UTC≈1,010 viewsread 7 August 2026

感谢大家这段时间的信任与支持,Audi内核 自费拿出 99 组数据号,全部免费送给大家练手、测试或备用。 官方频道: https://t.me/AudiABC

6 Aug 2026, 03:07 UTC892 viewsread 7 August 2026
File

🍭Audi 自费提供 99 个免费数据账号 所有账号均已通过正规渠道获取,支持后续授权绑定。如遇个别账号无法正常使用,可更换其他账号,均为一手货源,品质保障。 为提升整体可用性,账号等级已做随机分配处理,不设筛选门槛,确保公平获取。 上号工具:https://t-bu.cn/b009hk1dbi 访问码:yyds 授权平台:http://kssq1.com/ 官方频道: https://t.me/AudiABC

5 Aug 2026, 23:03 UTC883 viewsread 7 August 2026

这个安装包直接点点我跳转安装包去安装 云端上传的包名未上传正确 换了一个包名 下个版本会恢复!这只是一个小插错!先生

5 Aug 2026, 22:43 UTC≈2,930 viewsread 7 August 2026
Photo

Audi云端更新V1.4🍭 1.更换悬浮窗UI 2.更换控件样式 3.优化流畅性 4.更换APK颜色 5.修复执行时出现卡死问题 6.修复启动内核超时问题 🍭请前往APP直接安装或置顶安装 🍭使用时请勿挂载VPN 🍭点我跳转安装包 公益单透卡密:AudiWEHDJXBDKXJXAKBS 至臻版追锁赞助版提卡地址: https://shop.zmfaka.cn/shop/Audi 【购买后获取下载链接】 🍭 官方客服:@CNAZHO

5 Aug 2026, 20:57 UTC743 viewsread 7 August 2026
Photo

🍭全新悬浮窗即将上线: 本次版本带来重大架构升级,全面重构悬浮窗底层逻辑,大幅提升启动与加载速度,同时对整体流畅性进行了深度优化。经过多轮性能调校,无论在什么复杂场景中战斗,都能保持稳定流畅的运行表现,真正做到更快、更稳、更丝滑。 本次更新依旧两元 永不涨价! 官方频道: https://t.me/AudiABC

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

5 Aug 2026, 17:39 UTCAnonymous Poll158 voters

要不要断点无后

  1. 71%
  2. 不要29%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 14 most recent posts we hold, published 5 August 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 469,010 of 1,151,006entries 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 5 registered channels — 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Audi · 两元之神” (@AudiABC), 3,836 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/AudiABC.

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.