Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳出击报告【奥迪俱乐部】

Channel

深圳出击报告【奥迪俱乐部】

@szAudiRS7

2 usernames

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

16,947subscribers

-7,644 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002395229909
TypeChannel
Usernames@szAudiRS7 @szxc04
Description报告投稿联系奥迪修车队长:https://t.me/szxc02
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held122
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/szAudiRS7

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 58% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@szxcaodi18/690219 Aug 2026, 11:41 UTC@szAudiRS7/2487 · this entry19 Aug 2026, 11:41 UTC1.00under a minute
@szxcaodi18/692520 Aug 2026, 17:38 UTC@szAudiRS7/2492 · this entry20 Aug 2026, 17:38 UTC1.00under a minute
@szxcaodi18/698927 Aug 2026, 17:38 UTC@szAudiRS7/2498 · this entry27 Aug 2026, 17:38 UTC1.00under a minute
@szxcaodi18/699129 Aug 2026, 19:02 UTC@szAudiRS7/2503 · this entry29 Aug 2026, 19:02 UTC1.00under a minute
@szxcaodi18/72125 Oct 2026, 16:17 UTC@szAudiRS7/2554 · this entry5 Oct 2026, 16:17 UTC1.00under a minute
@szxcaodi18/72206 Oct 2026, 14:49 UTC@szAudiRS7/2556 · this entry6 Oct 2026, 14:49 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@szxcaodi1812 (8/8 hand-verifiable sample passed)1.00under a minute@szxcaodi18 (7–5)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 7 of the 7 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 84 comparable posts for this entry, running 24 July 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_mutual, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

16,91524,59120,75316,9477 August 202616 November 2026
122 measurements spanning 101 days, net -7,644. 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 15,764–25,742 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 122
Measured (UTC)SubscribersChange
16 Nov 2026, 08:5016,947-2
15 Nov 2026, 21:5516,949+34
12 Nov 2026, 09:1716,915-3
10 Nov 2026, 15:3716,918+1
10 Nov 2026, 05:2116,917-12
9 Nov 2026, 02:4716,929+1
8 Nov 2026, 18:4916,928-22
7 Nov 2026, 16:1716,950-3
6 Nov 2026, 17:5116,953+3
6 Nov 2026, 13:2016,950-6
5 Nov 2026, 15:4816,956no change
5 Nov 2026, 14:3816,956-14
4 Nov 2026, 14:1716,970no change
4 Nov 2026, 12:2916,970-19
3 Nov 2026, 11:3516,989-3
3 Nov 2026, 10:0116,992-12
2 Nov 2026, 12:3017,004no change
2 Nov 2026, 11:5717,004-433
1 Nov 2026, 15:0717,437-343
1 Nov 2026, 09:3617,780first reading

Engagement

84 posts held, back to 24 July 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 87 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.87%
avg views ÷ 16,947 subscribers
Avg views / post
317
9 posts measured
Reaction rate
0.193%
reactions ÷ views · ER floor
Posts in window
9
of 84 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 4 of 9 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 16 November 2026
Posts held84 (24 July 2026 – 16 November 2026)
Views total2,850
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 17:59 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

Photos
≈1,160
Videos
≈117
Links
≈2,280

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

17 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 94.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1694.1%
👍15.88%

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

Measured over the 84 most recent posts we hold, published 24 July 2026 to 16 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: 1 of 9 posts held from the last 30 days (11.1%) 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).

16 Nov 2026, 14:24 UTC78 viewsread 17 November 2026
Photo

🎰 奥迪赞助宝安小欣【半价卷】 📮 参与条件: 🎫 加入-小欣的朋友圈 🎫 加入-深圳奥迪RS修车俱乐部【修车榜单】 🎫 加入-深圳修车交流群【奥迪RS修车俱乐部】 └ 🎟️ 发言数大于 38 条 🎫 加入-深圳出击报告【奥迪俱乐部】 🎁 奖品内容: 💰️ 宝安小欣【半价卷】 × 1 ⚠️ 抽奖说明: 1. 兑奖凭中奖截图请联系:@aa09124aa 2. 奖品自开奖时间起7天内可兑换。 3. 炸号者中奖作废。 4. 优惠劵禁止买卖,一经发现或被举报核实之后,永久拉黑。 5. 携半价劵/白嫖劵出击者需提交反馈报告。 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月20日 22时22分00秒

16 Nov 2026, 08:25 UTC89 viewsread 17 November 2026

深圳奥迪RS出击报告 学生留名:@dahuaiZx 验证时间:11.16 老师花名:小娘子@Xiaoniangziyydss 城市坐标:福田 上课花费:1200p 颜值身材:人照一致,甚至线下感觉更自然更好看 服务内容: 课表有的全部都有 出击体验:课表有的基本上都有,陪洗也有 上课过程:约的2点,我提前1.47到了,娘子没看见消息罚站了十分钟哭,遥控上楼,长租房很安全不用登记,一进门小娘子就微笑迎接,头上的发卡带着是真好看,颜值感觉都提升了1分,人照百分之百符合 而且感觉真人比照片好看,以前不知道哪儿看到的带发卡那个照片基本上就是那样了,一进门就摸摸小弟,很热情,然后交了水费带着我洗澡,洗澡也很贴心给我擦后背,然后领着到床上可以选择各种各样的丝袜,我是新手小司机,把我推到床上直接啵上来,很有女友感,我感觉手活比口活还顶,可惜我没怎么出击过还是比较紧张状态很差,好不容易起来了,一插入,娘子的妹妹又紧又热,包裹感巨强,太爽了,说实…

15 Nov 2026, 14:19 UTC134 viewsread 17 November 2026

🎉🎉🎉🎊🎊🎊 开奖通知 🎊🎊🎊🎉🎉🎉 📌 防伪编号:FZ5LSRPPVM 活动:奥迪赞助罗湖【婉婉】半价卷 开奖时间:2026-11-15 22:19(UTC+8) 🫡 联系领奖:奥迪RS修车大队长 【认准队长ID再付款】 🏆 中奖名单 1. jackfunny Joy 奖品:罗湖婉婉【半价卷】 × 1 🔍 公正性证据(可独立复算) 服务器种子:364b302d1689e9e5857a1bc316ff72beee4bf45678ab45e171688da3c3982646 公共随机信标:drand quicknet #33983000 信标随机数:d9958cdf466d9c5fb8d7cb50b7d0b1c0651f48d477cd75d62676ba6e370a15e8 最终种子:daea15ab66389f62d23aa331a9f44e613ac26b45ab44b92f8305a11260e84cf5…

15 Nov 2026, 01:02 UTC172 viewsread 17 November 2026
Photo

🎰 奥迪RS修车俱乐部恭喜BLG夺冠 📮 参与条件: 🎫 加入-深圳奥迪RS修车俱乐部【修车榜单】 🎫 加入-深圳修车交流群【奥迪RS修车俱乐部】 └ 🎟️ 发言数大于 66 条 🎫 加入-深圳出击报告【奥迪俱乐部】 🎁 奖品内容: 💰️ 口令【100】 × 3 ⚠️ 抽奖说明: 我们是冠军 恭喜BLG夺冠 这是兄弟们的青春 熬夜辛苦了 。 领奖联系队长 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月18日 09时01分00秒

12 Nov 2026, 13:45 UTC243 views1 reactionsread 17 November 2026

深圳奥迪RS出击报告 学生留名:狂徒 验证时间:11-12 老师花名:@xhl78 城市坐标:福田 上课花费:PP 颜值身材:人照如一 服务内容: xcz🐍 出击体验: 约了晚上做头发 下午闲来无事 就去圆梦了 在等了前面几位老哥也是终于到我了 为了圆梦 等几个小时也是值得 见到火狸那一刻确实也值得 谈吐未曾冷场给的反应也恰到好处 但绝对有反差 尤其是在床上 无论什么时候都含情脉脉看着你 眼神交流真的很到位 爱爱过程姿势随意操盘 叫的也很让人上头 骚话张嘴就是 奈何昨晚落枕状态不佳问过后面没人加多一课以示支持最后也是顺利出水 老师也没有任何不耐烦 恭恭敬敬温柔体贴 给到夯 综合评分:9.5/满分10分 【奥迪RS俱乐部】老师频道:https://t.me/szxcaodi18 【奥迪RS俱乐部】修车报告:https://t.me/szAudiRS7 【奥迪RS俱乐部】修车雷暴:https://t.me/adcjlb 【奥迪…

👍1

10 Nov 2026, 12:37 UTC302 viewsread 17 November 2026
Photo

🎊 奥迪赞助罗湖【婉婉】半价卷(已开奖) ⚠️ 抽奖说明: 1. 兑奖凭中奖截图请联系:https://t.me/szxc02 2. 奖品自开奖时间起7天内可兑换。 3. 炸号者中奖作废。 4. 优惠劵禁止买卖 ⏰ 开奖时间:2026年11月15日(周日)22时19分(UTC+8) 🎁 奖品:罗湖婉婉【半价卷】 × 1 📌 参与要求 👥 加入-深圳修车交流群【奥迪RS修车俱乐部】 └ 💬 活动期间发言至少 38 条 └ 📣 加入-深圳奥迪RS修车俱乐部【修车榜单】 └ 📣 加入-深圳出击报告【奥迪俱乐部】 └ 📣 加入-婉婉的朋友圈 🎫 活动编号:FZ5LSRPPVM 🔒 种子承诺:bce495ccef852cd4… 开奖将同时使用种子承诺与未来公共随机数,任何人都能独立复算中奖名单。

25 Oct 2026, 10:08 UTC674 views1 reactionsread 17 November 2026

深圳奥迪RS出击报告 学生留名:素质工兵 验证时间:4:10 老师花名:冉冉 城市坐标:深圳福田 上课花费:2200 颜值身材:皮肤白,完美身材无敌 服务内容:老师本人跟照片一样好看,身材好皮肤白,是我喜欢的类型,交完水费,就开始进行表演流程,老师外表风骚适合玩SM,气氛带动得很到位,上完课之后中途按摩一下,进行第二次,一般老师我都只出两次水,结果老师太疯骚了,下面的水多。两个人在床上缠绵很投入,我就被榨干了。破记录了很少出三次。 联系方式:@ranran948 深圳修车大队交流群【奥迪RS俱乐部】 😀😀😀😀😀😀😀😀😀😀😀😀😀 【奥迪RS俱乐部】老师频道:https://t.me/szxcaodi18 【奥迪RS俱乐部】修车报告:https://t.me/szAudiRS8 【奥迪RS俱乐部】修车雷暴:https://t.me/adcjlb 【奥迪RS俱乐部】交流群:https://t.me/SZaodi02 【奥迪RS俱乐部…

❤1

24 Oct 2026, 07:58 UTC574 views1 reactionsread 17 November 2026

深圳奥迪RS出击报告 学生留名:林大也也 验证时间:10月23日 老师花名:维维 城市坐标:#深圳宝安 上课花费:P 身材颜值:S身、颜值高 服务类容:课表内容 出击体验:开门眼前一亮,人照9成,本人去掉美颜的加持看起来好欲,绝无风尘味,声线很温柔。交费后把老师拥入怀里,一个对视,老师秒懂,温柔侍浴,洗得也很细心,我亦忙著把玩软糯的咪咪和屁屁。入正题,先给妹妹进攻我咪咪,舌头很软很暖,我也继续不停地搓著她咪咪,之后她一直吻下去,望著鳮巴在小嘴里进进出出,👅在环绕沟边滋滋作响。爽感爆棚。跟著我来操盘,先吻遍她全身,小鲍鱼粉嫩多汁,很敏感,没几下就湿漉漉的了。鳮巴已入状态了,传教,侧入,后入,女上再传教,叫声看著她青涩的表情和十分诱人的娇喘,终于蛇著出水...很久没那么爽了...休息一下,服务这么全面的老师属实难得,一定会返 联系方式:@abc28828 【奥迪RS俱乐部】工兵团:https://t.me/+F5bW5PS5B8Qx…

❤1

19 Oct 2026, 08:57 UTC584 views1 reactionsread 17 November 2026

深圳奥迪RS出击报告 学生留名:新奇士 验证时间:10.19 老师花名:小团团 城市坐标:#深圳福田 上课花费:45(三小时) 身材颜值:长腿 胸大 服务类容:见课表 出击体验:在频道潜伏了蛮久 一直想尝一下小团团姐姐的服务 下班后直接前往 人照一致,姐姐很健谈 给我的感觉不错于是包时 陪洗后姐姐为我服务 课表内容都有 大胸操盘很爽 由于小弟弟本身够硬 姐姐女上一直在喷水 小狼也特别爽 感觉是出击过最爽的女上了 后面的时光按下不表了 姐姐给我的感觉很享受过程 本小狼也干的特别爽 属于是双赢 联系方式:@abcxal 【奥迪RS俱乐部】工兵团:https://t.me/+F5bW5PS5B8QxZTJl 报告投稿联系奥迪修车队长:https://t.me/szxc02

❤1

17 Oct 2026, 08:20 UTC542 viewsread 17 November 2026

深圳奥迪RS出击报告 学生留名:醒悟 验证时间:10,16 老师花名:宝安维维 @abc28828 城市坐标:宝安西乡 上课花费:800P 颜值身材:9.9 服务内容:课表介绍 出击体验:昨晚做完准备出门的时候,维维在门口小声问了我一句,你能不能帮我写篇报告?看着她的眼睛二话没说我就答应下来了。说来惭愧,维维我找了几次了,竟然还没写过报告😂。回归正题。维维挑的地方安全系数可以说是很高,停车也方便,进门先是交水费脱衣服洗澡。值得一提的是全程不需要你动手,维维会非常仔细的把你全身洗干净,然后再拿毛巾帮你擦干净,最后坐在床边,她会把你的脚放到她腿上再擦一遍。这个我说实话,算是我找过的老师里服务最认真的。服务过程认真,不扭捏,姿势拉满,我认为维维最厉害的是哪怕她躺在你身下,你累了不动了,她自己会顶胯配合把动作继续下去,之前第一次遇到这个阵势把我看愣了😂。总结,你无论是想体验服务还是情绪价值,亦或者是喜欢69,找维维就对了 综合评分:9.…

13 Oct 2026, 15:38 UTC≈2,380 views1 reactionsread 17 November 2026
Photo

深圳奥迪RS出击报告 学生留名:J 验证时间:2026.10.13 老师花名:@YWWoioi #余晚晚 城市坐标:深圳南山 上课花费:1699 颜值身材:爱 服务内容: 女友般 出击体验:好久没见晚晚,今天摸鱼时闲聊,决定今天去找晚晚。就和晚晚约好时间。 熟悉的地方,晚晚刚好下来接我,就顺利上楼。坐下一顿唠嗑,好一会才开始脱衣洗澡开始激情运动。晚晚对我不断的舔弄,我反手把晚晚翻过来,开始挑逗晚晚的豆豆,看看晚晚的翘臀,感受晚晚在身上一抖一抖的触感。晚晚最终忍受不了直接给我带套坐了上去,疯狂桩我,只听床下咔嚓一声,床塌了,这就是爱的桩机力量吧。后续换了几个姿势,手是离不开胸的,嘴是离不开嘴的,最终结束。 中间休息,聊着天,晚晚还展示了一下,按摩小技巧,我还颇为受用。 第二次在晚晚咬我一口后开始,途中还浪费晚同学一个套套才结束,可惜可惜。 综合评分:10/满分10分 【奥迪RS俱乐部】老师频道:https://t.me/szxc…

❤1

12 Oct 2026, 08:04 UTC479 views3 reactionsread 17 November 2026

深圳奥迪RS出击报告 学生留名:鸟巢 验证时间:10-11 老师花名:维维 @abc28828 城市坐标:宝安 上课花费:800p 颜值身材:10 服务内容:课表 出击体验:按约定时间到了科室,推门时维维老师已经在等,还准备好了矿泉水,进门感觉挺舒服。坐下聊了几句,递上水费后来到浴室,准备好了一次性牙膏和水杯,两人一起刷牙漱口。 共浴的时候边聊边洗,前后都清理得比较仔细,擦干后让老师换上了我喜欢的半筒黑丝,光是看到穿在身上二弟就有了反应。 上完床她主动凑过来舌吻,嘴唇柔软,舌尖带着一点温热,力度和节奏都刚好,气氛很快就热起来。接着开始口,从胸口慢慢往下,舌尖绕着乳晕打转,能感觉到细微的湿润和温度变化,再滑到小腹和大腿,敏感的地方会多停留一会儿,随即对二弟发起进攻,含进去之后口腔温热紧致,节奏不急不躁,偶尔会口的比较快,舌头灵活地上下滑动,吸的时候力度刚好,清晰的水口声混着呼吸声,持续了几分钟,整个人越来越紧,头皮有点发麻。 …

❤3

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

Posts edited after publishing

@szAudiRS7 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
15 November 2026
Most recent edit
15 November 2026

Mentions

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

“深圳出击报告【奥迪俱乐部】” (@szAudiRS7), 16,947 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/szAudiRS7.

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.