Telegram RegisterThe public register of Telegram
Telegram profile photo for 山海-ShanHai-Channel

Channel

山海-ShanHai-Channel

@shanhai_1

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

9,955subscribers

-663 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-1001988709678
TypeChannel
Username@shanhai_1
Description群组:https://t.me/shanhai_2 官网①:https://shanhai.me 官网②:https://shanhai.one 官网③:https://shanhai.sbs 官网④:https://shanhai.cfd 官网⑤:https://shanhai.click 官网⑥:https://shanhai.cyou
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 November 2026
Measurements held43
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/shanhai_1

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 84% 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,92810,61810,2737 August 2026 — 10,618 subscribers7 August 2026 — 10,618 subscribers8 August 2026 — 10,611 subscribers9 August 2026 — 10,602 subscribers10 August 2026 — 10,579 subscribers12 August 2026 — 10,573 subscribers13 August 2026 — 10,544 subscribers14 August 2026 — 10,542 subscribers16 August 2026 — 10,531 subscribers17 August 2026 — 10,510 subscribers18 August 2026 — 10,492 subscribers19 August 2026 — 10,499 subscribers20 August 2026 — 10,505 subscribers21 August 2026 — 10,503 subscribers22 August 2026 — 10,486 subscribers24 August 2026 — 10,475 subscribers25 August 2026 — 10,454 subscribers26 August 2026 — 10,448 subscribers27 August 2026 — 10,429 subscribers28 August 2026 — 10,401 subscribers29 August 2026 — 10,361 subscribers31 August 2026 — 10,330 subscribers1 September 2026 — 10,286 subscribers2 September 2026 — 10,236 subscribers3 September 2026 — 10,210 subscribers4 September 2026 — 10,200 subscribers7 September 2026 — 10,168 subscribers10 September 2026 — 10,143 subscribers12 September 2026 — 10,102 subscribers14 September 2026 — 10,070 subscribers16 September 2026 — 10,039 subscribers18 September 2026 — 10,030 subscribers2 October 2026 — 9,972 subscribers8 October 2026 — 9,955 subscribers14 October 2026 — 9,950 subscribers17 October 2026 — 9,934 subscribers20 October 2026 — 9,928 subscribers23 October 2026 — 9,933 subscribers26 October 2026 — 9,929 subscribers29 October 2026 — 9,937 subscribers1 November 2026 — 9,953 subscribers4 November 2026 — 9,958 subscribers7 November 2026 — 9,955 subscribers9,9557 August 20267 November 2026
43 measurements spanning 92 days, net -663. 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,825–10,722 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
7 Nov 2026, 17:589,955-3
4 Nov 2026, 19:209,958+5
1 Nov 2026, 21:469,953+16
29 Oct 2026, 14:469,937+8
26 Oct 2026, 08:479,929-4
23 Oct 2026, 08:309,933+5
20 Oct 2026, 03:199,928-6
17 Oct 2026, 01:289,934-16
14 Oct 2026, 01:009,950-5
8 Oct 2026, 19:389,955-17
2 Oct 2026, 17:169,972-58
18 Sept 2026, 14:0110,030-9
16 Sept 2026, 04:5610,039-31
14 Sept 2026, 08:5810,070-32
12 Sept 2026, 18:5810,102-41
10 Sept 2026, 22:0110,143-25
7 Sept 2026, 23:3710,168-32
4 Sept 2026, 21:5910,200-10
3 Sept 2026, 07:3910,210-26
2 Sept 2026, 03:3310,236first reading

Engagement

25 posts held, back to 19 March 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 53 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.9%
avg views ÷ 9,955 subscribers
Avg views / post
2,380
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
7
of 25 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 8 November 2026
Posts held25 (19 March 2024 – 8 November 2026)
Views total16,676
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 10:24 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

Links
2

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

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

8 Nov 2026, 18:01 UTC≈1,110 viewsread 10 November 2026

新增适配 小火箭 Shadowrocket 需要参考网站使用文档教程使用。 另外新增抗阻断DNS,超时的用户再次更新订阅即可获取最新配置文件。

7 Nov 2026, 21:10 UTC≈1,470 viewsread 10 November 2026

DNS新增适配客户端以及内核 客户端: Surfboard 内核: sing-box 默认走sing-box内核的客户端包含如下 安卓 SFA、NekoBox for Android、Karing、Hiddify、官方 sing-box iOS / macOS Streisand、Hiddify、Karing、官方 sing-box Windows Hiddify、Karing、NekoBox、GUI.for.SingBox(以及大多数基于官方内核的 GUI 外壳)、官方 sing-box 跨平台通用 Hiddify(Windows / macOS / Linux / Android / iOS) Karing(Windows / macOS / Android / iOS) 目前已经停止公共解析,需要使用正常山海ShanHai,可以参考以上客户端,上述未发clash内核客户端,clash内核类客户端之前已经发布,…

7 Nov 2026, 09:16 UTC976 viewsread 8 November 2026

入口扩容迁移,大约卡10-15分钟后恢复,不会断连。

6 Nov 2026, 10:27 UTC≈1,890 viewsread 10 November 2026

重构OpenWrt客户端插件,全新UI,修复以往BUG。 下载地址: https://app.shanhai.one

31 Oct 2026, 15:45 UTC≈4,280 viewsread 10 November 2026

#其它通知 免费升级:国际套餐-小杯→国际套餐-大杯(免费升级) 新增套餐:国际套餐-大杯 特别注意:山海 ShanHai所有套餐请查看使用文档进行客户端下载,才能使线路稳定。 由于上次迁移面板设置遗漏,导致部分账号未及时重置流量,除了不限时套餐外,所有套餐将于今日凌晨0.00重置一次,次月再开启按月重置。

27 Oct 2026, 21:46 UTC≈5,200 viewsread 8 November 2026

GFW把订阅跟客户端的API端口给墙了,已经采用API调用的形式提供订阅以及客户端,端外订阅失败的可以前往网站获取最新的订阅链接,客户端内的客户可以大退软件重新进入即可。

28 Sept 2026, 19:49 UTC≈11,100 viewsread 8 November 2026

端内外已经恢复正常使用,发放补偿以及活动,内容如下👇 补偿码(礼品兑换码): ILP2y21W18LE0y9L 前往网站或者APP→个人中心→礼品卡→输入礼品码进行兑换 内容: 3元账户余额,限量1000份, 国庆75折优惠码: GcAHQCs8 兑换码以及优惠码起止时间为: 2026/09/29 03:47 ~ 2026/10/07 03:47 请在周期内完成兑换或使用,逾期不补。

27 Sept 2026, 04:48 UTC≈10,200 viewsread 10 November 2026

目前实验性开放端外通用客户端: 可使用客户端如下 stash surfboard surge clash verge clash mi clash meta

24 Sept 2026, 03:00 UTC≈10,100 viewsread 10 November 2026

订阅域名被墙了,如节点超时,客户端内可直接更新订阅,获取最新节点状态,端外的话需要重新前往网站获取最新的订阅链接进行使用。 目前国内可直接访问的官网: shanhai.one shanhai.sbs shanhai.cyou 其余均被墙

2 Sept 2026, 11:05 UTC≈13,400 viewsread 8 November 2026

通知: 因使用的阿里云账户异常,导致原先节点入口的域名无法使用,已经更换新域名,若出现超时无法使用,请尽快更新订阅。

Showing the 12 most recent of 25 posts we hold for @shanhai_1. 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 @shanhai_1 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
27 August 2026
Most recent seen missing
27 August 2026
Median time before seen missing
3 months
Seen missing in the last 30 days
0

Mentions

Named by 1 registered channel — 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.

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

“山海-ShanHai-Channel” (@shanhai_1), 9,955 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/shanhai_1.

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.