Telegram RegisterThe public register of Telegram

Channel

深圳车友会报告

@SH_BG798

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

5,401subscribers

+49 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-1003812848737
TypeChannel
Username@SH_BG798
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/SH_BG798

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 70% 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 why it has no browse page of its own yet.

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 word for word 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
@SZ_0088/4515 Aug 2026, 00:59 UTC@SH_BG798/83 · this entry5 Aug 2026, 00:59 UTC1.00under a minute
@SZ_0088/4525 Aug 2026, 04:37 UTC@SH_BG798/84 · this entry5 Aug 2026, 04:37 UTC1.00under a minute
@SZ_0088/4605 Aug 2026, 14:09 UTC@SH_BG798/87 · this entry5 Aug 2026, 14:09 UTC1.00under a minute
@SZ_0088/4797 Aug 2026, 05:42 UTC@SH_BG798/92 · this entry7 Aug 2026, 05:42 UTC1.00under a minute
@SZ_0088/4857 Aug 2026, 13:17 UTC@SH_BG798/93 · this entry7 Aug 2026, 13:17 UTC1.00under a minute
@SZ_0088/4927 Aug 2026, 15:01 UTC@SH_BG798/94 · this entry7 Aug 2026, 15:01 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@SZ_008813 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (76)

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. 3 of the 6 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 27 comparable posts for this entry, running 1 August 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @SZ_0088. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5,3495,4015,3756 August 2026 — 5,352 subscribers7 August 2026 — 5,349 subscribers10 August 2026 — 5,401 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net +49. 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 5,341–5,409 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:155,401+52
7 Aug 2026, 13:375,349-3
6 Aug 2026, 20:175,352first reading

Engagement

49 posts held, back to 1 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 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.40%
avg views ÷ 5,401 subscribers
Avg views / post
75.7
49 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
49
of 49 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 49 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 11 August 2026
Posts held49 (1 August 202611 August 2026)
Views total3,707
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:20 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
84
Links
92

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

11 Aug 2026, 08:53 UTC54 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178620427402 🎰 福田 小辣椒 半价优惠劵 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 💁 参与情况:110达标 / 112报名 🎅 联系领奖:@xxw3823 1. 阮 经天 奖品:P半价 祝大家心想事成好运连连!

11 Aug 2026, 06:43 UTC56 viewsread 12 August 2026
Photo

🎰 深圳 Dilys 半价优惠 📮 参与条件: 🪪 必须设置用户名 🎫 加入-深圳车友会 └ 🔑 发送口令﹝欢迎 Dilys 入住车友会﹞ 🎫 加入-深圳车友会公开榜 🎫 加入-深圳车友会报告 🎫 加入-Dilys个人兼职只外出🏖️ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ P半价 × 1 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 📅 开奖日期:(北京时间) 2026年08月14日 14时42分00秒

11 Aug 2026, 06:39 UTC40 viewsread 12 August 2026
Photo

🎰 深圳 OK茜 半价优惠劵 📮 参与条件: 🪪 必须设置用户名 🎫 加入-OK茜 ❤️ 私密空间 🎫 加入-深圳车友会 └ 🔑 发送口令﹝欢迎 OK茜 入住车友会﹞ 🎫 加入-深圳车友会公开榜 🎫 加入-深圳车友会报告 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ P半价 × 1 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 📅 开奖日期:(北京时间) 2026年08月14日 14时39分00秒

11 Aug 2026, 05:49 UTC43 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178620397375 🎰 南山 梓菡 半价优惠劵 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 💁 参与情况:107达标 / 112报名 🎅 联系领奖:@zixin221 1. 装逼 失误 奖品:P半价 祝大家心想事成好运连连!

11 Aug 2026, 05:22 UTC50 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178616561089 🎰 南山 安迪 半价优惠劵 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 💁 参与情况:93达标 / 93报名 🎅 联系领奖:@andi5201 1. 来世再 上985 奖品:P 半价 祝大家心想事成好运连连!

11 Aug 2026, 04:34 UTC50 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178611954169 🎰 龙华 甜甜酱 半价优惠劵 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 💁 参与情况:86达标 / 89报名 🎅 联系领奖:@yyyaa123451 1. 北极 小企鹅 奖品:P 半价 祝大家心想事成好运连连!

11 Aug 2026, 04:17 UTC49 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178611599053 🎰 龙岗 瑶瑶酱 半价优惠劵 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 💁 参与情况:91达标 / 94报名 🎅 联系领奖:@aaqqq999888 1. 亚当 (空想家) 奖品:P 半价 祝大家心想事成好运连连!

10 Aug 2026, 15:17 UTC78 viewsread 12 August 2026
Photo

🎰 南山 小七 半价优惠劵 📮 参与条件: 🪪 必须设置用户名 🎫 加入-小七的秘密小窝 🎫 加入-深圳车友会 └ 🔑 发送口令﹝欢迎 小七 入住车友会﹞ 🎫 加入-深圳车友会公开榜 🎫 加入-深圳车友会报告 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ P半价 × 1 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 📅 开奖日期:(北京时间) 2026年08月13日 14时16分00秒

10 Aug 2026, 11:50 UTC75 viewsread 12 August 2026
Photo

🎰 宝安 思语 半价优惠劵 📮 参与条件: 🪪 必须设置用户名 🎫 加入-宝安思语贵宾室 🎫 加入-深圳车友会 └ 🔑 发送口令﹝欢迎 思语 入住车友会﹞ 🎫 加入-深圳车友会公开榜 🎫 加入-深圳车友会报告 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ P半价 × 1 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 📅 开奖日期:(北京时间) 2026年08月13日 14时49分00秒

10 Aug 2026, 10:34 UTC64 viewsread 12 August 2026
Photo

🎰 宝安 呦呦 半价优惠劵 📮 参与条件: 🪪 必须设置用户名 🎫 加入-呦呦的朋友圈 🎫 加入-深圳车友会 └ 🔑 发送口令﹝欢迎 呦呦 入住车友会﹞ 🎫 加入-深圳车友会公开榜 🎫 加入-深圳车友会报告 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ P半价 × 1 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 📅 开奖日期:(北京时间) 2026年08月13日 12时34分00秒

10 Aug 2026, 08:16 UTC66 viewsread 12 August 2026
Photo

🎰 龙岗 灿灿 半价优惠 📮 参与条件: 🪪 必须设置用户名 🎫 加入-深圳车友会 └ 🔑 发送口令﹝欢迎 灿灿 入住车友会﹞ 🎫 加入-灿灿小课堂 🎫 加入-深圳车友会公开榜 🎫 加入-深圳车友会报告 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ P半价 × 1 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 📅 开奖日期:(北京时间) 2026年08月13日 16时16分00秒

10 Aug 2026, 07:18 UTC63 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178611487578 🎰 南山 三三 半价优惠劵 ⚠️ 抽奖说明: 1.兑奖联系对应奖品提供方 2.抽奖请先设置用户名 3.兑奖有效期7天,过期无效 4.因炸号、注销、超时等原因一律不兑奖 5.中奖后退出群组和频道,炸号,不予兑奖 6.该活动所有解释权归群管理所有 💁 参与情况:100达标 / 102报名 🎅 联系领奖:@SanS3333 1. 超级 皮卡丘 奖品:P半价 祝大家心想事成好运连连!

Showing the 12 most recent of 49 posts we hold for @SH_BG798. 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 — 267,860 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.

Mentions

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

“深圳车友会报告” (@SH_BG798), 5,401 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/SH_BG798.

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.