Telegram RegisterThe public register of Telegram
Telegram profile photo for 上海419修车认证榜

Channel

上海419修车认证榜

@sh419yh

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry

9,694subscribers

-1,940 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-1001271523899
TypeChannel
Username@sh419yh
Description上海419认证榜单: https://t.me/sh419yh 上海419修车交流群:https://t.me/sh419bd 上海中圈: https://t.me/shxclmzq 上海中圈认证客服: @shzqkfxm 上榜管理员①: @sh419jqb3 上榜管理员②: @sh419td2
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 November 2026
Measurements held44
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/sh419yh

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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.

Growth

9,69411,80210,7487 August 2026 — 11,634 subscribers7 August 2026 — 11,634 subscribers8 August 2026 — 11,698 subscribers9 August 2026 — 11,802 subscribers10 August 2026 — 11,797 subscribers11 August 2026 — 11,761 subscribers12 August 2026 — 11,726 subscribers13 August 2026 — 11,641 subscribers14 August 2026 — 11,571 subscribers16 August 2026 — 11,488 subscribers17 August 2026 — 11,400 subscribers18 August 2026 — 11,321 subscribers19 August 2026 — 11,268 subscribers20 August 2026 — 11,242 subscribers21 August 2026 — 11,213 subscribers23 August 2026 — 11,114 subscribers24 August 2026 — 11,234 subscribers25 August 2026 — 11,149 subscribers26 August 2026 — 11,108 subscribers27 August 2026 — 11,105 subscribers28 August 2026 — 11,090 subscribers29 August 2026 — 11,048 subscribers30 August 2026 — 11,002 subscribers31 August 2026 — 10,949 subscribers1 September 2026 — 10,919 subscribers3 September 2026 — 10,875 subscribers4 September 2026 — 10,865 subscribers7 September 2026 — 10,774 subscribers10 September 2026 — 10,694 subscribers12 September 2026 — 10,598 subscribers14 September 2026 — 10,529 subscribers15 September 2026 — 10,523 subscribers18 September 2026 — 10,478 subscribers1 October 2026 — 10,300 subscribers6 October 2026 — 10,184 subscribers10 October 2026 — 10,090 subscribers13 October 2026 — 10,054 subscribers14 October 2026 — 9,983 subscribers18 October 2026 — 9,922 subscribers21 October 2026 — 9,935 subscribers24 October 2026 — 9,912 subscribers27 October 2026 — 9,804 subscribers30 October 2026 — 9,740 subscribers2 November 2026 — 9,694 subscribers7 August 20262 November 2026
44 measurements spanning 87 days, net -1,940. 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 9,378–12,118 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 44
Measured (UTC)SubscribersChange
2 Nov 2026, 10:109,694-46
30 Oct 2026, 17:299,740-64
27 Oct 2026, 20:019,804-108
24 Oct 2026, 23:059,912-23
21 Oct 2026, 16:559,935+13
18 Oct 2026, 06:369,922-61
14 Oct 2026, 23:589,983-71
13 Oct 2026, 20:5610,054-36
10 Oct 2026, 06:3910,090-94
6 Oct 2026, 04:3810,184-116
1 Oct 2026, 01:3910,300-178
18 Sept 2026, 05:4010,478-45
15 Sept 2026, 22:4010,523-6
14 Sept 2026, 07:5710,529-69
12 Sept 2026, 16:3910,598-96
10 Sept 2026, 16:5610,694-80
7 Sept 2026, 12:3810,774-91
4 Sept 2026, 17:2110,865-10
3 Sept 2026, 00:0510,875-44
1 Sept 2026, 20:1510,919first reading

Engagement

50 posts held, back to 17 January 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 48 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.07%
avg views ÷ 9,694 subscribers
Avg views / post
6.8
4 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
4
of 50 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 4 November 2026
Posts held50 (17 January 2026 – 4 November 2026)
Views total27
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 20:52 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
≈6,770
Videos
≈542
Links
≈301

Lifetime counters from Telegram’s own channel header, read 4 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.

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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 4 posts held from the last 30 days (0%) 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).

4 Nov 2026, 12:38 UTC8 viewsread 4 November 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

4 Nov 2026, 04:36 UTC5 viewsread 4 November 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

3 Nov 2026, 12:39 UTC6 viewsread 3 November 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

3 Nov 2026, 04:35 UTC8 viewsread 3 November 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

1 Sept 2026, 12:35 UTC11 viewsread 1 September 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

29 Aug 2026, 04:35 UTC10 viewsread 29 August 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

28 Aug 2026, 12:36 UTC10 viewsread 28 August 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

28 Aug 2026, 04:35 UTC8 viewsread 28 August 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

27 Aug 2026, 12:35 UTC13 viewsread 27 August 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

27 Aug 2026, 04:35 UTC9 viewsread 27 August 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

26 Aug 2026, 12:35 UTC8 viewsread 26 August 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

26 Aug 2026, 04:36 UTC2 viewsread 26 August 2026
Photo

🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

Showing the 12 most recent of 50 posts we hold for @sh419yh. 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 recorded as deleted after publishing

We recorded 4 posts on @sh419yh as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
10 August 2026
Median time before seen missing
16 hours
Seen missing in the last 30 days
0

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

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

“上海419修车认证榜” (@sh419yh), 9,694 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/sh419yh.

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.