Channel
@shanghaihhy
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Declared links · Cite this entry
252subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001807501786 |
|---|---|
| Type | Channel |
| Username | @shanghaihhy |
| Created | Between 1 October 2022 and 8 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 15 August 2026 |
| On Telegram | t.me/shanghaihhy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:47 | 252 | +1 |
| 8 Aug 2026, 09:30 | 251 | no change |
| 8 Aug 2026, 06:01 | 251 | first reading |
10 posts held, back to 8 April 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 23 January 2025. An engagement rate over an empty window would be a number about nothing.
11 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 90.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 90.9% | |
| 👍 | 1 | 9.09% |
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 7 of the 10 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 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 8 April 2023 to 23 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
SH034 #公开信息 地址：徐汇区三江路 价格：6P 联系方式: 2483208819 Lucky-Anie520 19823932819
❤1
SH034 #公开信息 地址：静安区 价格：6P20BY 联系方式: 3260523289 BYRLZ555
❤2
SH033 #公开信息 地址：闵行区 价格：6P15BY 联系方式: 2634282171
SH032 #公开信息 地址：普陀区中环大厦 价格：5P 联系方式: 1549850439 kkwemake
SH031 #公开信息 地址：宝山纪念路 价格：6P16BY 联系方式: 1535334710
SH030 #公开信息 地址：普陀区 价格：5P 联系方式: xtao1121010289
❤2
🌵#后花园 NPC 社区导航🌵 https://t.me/lsjhouhuayuan 点击蓝色文字，可跳转频道或群 ➖➖👇➖➖➖➖👇➖➖ ✨⛩【后花园楼凤修车小姐姐资源】⛩✨ 🔞北京 🔞上海 🔞广州 🔞深圳 🔞南京 🔞武汉 🔞长沙 🔞郑州 🔞成都 🔞重庆 🔞杭州 🔞西安 免费修车咨询 每日推送 更多频道正在陆续搭建中！ 投稿 或者小姐姐入驻私聊 @houhuayuantg_bot
❤2
SH029 #公开信息 地址：青浦 价格：5P 联系方式: 2503152833
❤2
SH028 #公开信息 地址：普陀铜川路 价格：6P 联系方式: 2673076689 177270346
❤1👍1
Showing the 10 most recent of 10 posts we hold for @shanghaihhy. 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 — 1,204,535 of 1,549,704entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 3 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.
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.
@shanghaihhy named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“上海楼凤修车公开榜” (@shanghaihhy), 252 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/shanghaihhy.
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.