Telegram RegisterThe public register of Telegram
Telegram profile photo for 山海资源对接

Channel

山海资源对接

@shanhaizydj

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Cite this entry

135subscribers

+6 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003322115300
TypeChannel
Username@shanhaizydj
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/shanhaizydj

Previous handles

@shanhaizydj was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@shanhaizydj
held 9 August 20269 August 2026

Growth

1271351317 August 2026 — 129 subscribers9 August 2026 — 129 subscribers15 August 2026 — 127 subscribers23 August 2026 — 129 subscribers30 August 2026 — 135 subscribers7 August 202630 August 2026
5 measurements spanning 23 days, net +6. 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 126–136 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 23:28135+6
23 Aug 2026, 09:16129+2
15 Aug 2026, 18:53127-2
9 Aug 2026, 01:31129no change
7 Aug 2026, 18:22129first reading

Engagement

19 posts held, back to 16 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

85 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 51.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4451.8%
👍2023.5%
👏78.24%
🤝44.71%
👀33.53%
22.35%
👎22.35%
🍌11.18%
🔥11.18%
🦄11.18%

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

Measured over the 19 most recent posts we hold, published 16 May 2026 to 8 August 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

8 Aug 2026, 23:08 UTC359 viewsread 9 August 2026

丝滑123 存,万内来, 3D料,微支个人码,重点丝滑!!!

6 Aug 2026, 11:24 UTC78 viewsread 9 August 2026

微信视频号发bc单图,学生团 宝妈团多的来谈价格

25 Jul 2026, 09:04 UTC≈2,090 views3 reactionsread 9 August 2026

真机机房 号商 码商来谈下新项目

3

14 Jul 2026, 00:01 UTC476 views5 reactionsread 9 August 2026

收全渠道兼职粉,粉真包结

2👎2👍1

6 Jul 2026, 18:09 UTC≈2,520 views2 reactionsread 9 August 2026

色站 劫持 全渠道来谈,ip cpc cpa大量要

1👍1

3 Jul 2026, 16:41 UTC≈3,220 views2 reactionsread 9 August 2026

三人群38 数据管够 支持担保

1👍1

1 Jul 2026, 03:32 UTC764 views0 reactionsread 9 August 2026

BC IM不看效果:0.3 三人群:38 抖音代发破百浏览就算有效:30 无限收量,支持一切担保

29 Jun 2026, 07:34 UTC≈1,820 views4 reactionsread 9 August 2026

近期缺量业务:抖音世界杯代发 微信三人群 微信推名片 有小程序 H5 公众号接兼职粉的号商也要

3👍1

22 Jun 2026, 00:44 UTC910 views3 reactionsread 9 August 2026

世界杯抖音代发单图,中午发布 晚上结算 不用等24小时 不用过加热 不用企业认证 破百浏览量即为有效单

2👍1

19 Jun 2026, 14:50 UTC926 views11 reactionsread 9 August 2026

麻烦不要无脑问问题,看上面规则 也别拿外面需要24h 需要冲抖+过加热的来对比 这个基本发了破100浏览就算有效,而且封号概率极低 外面2个素材130过加热 沉淀24小时 还要绑定企业 发不了两次就封号 自己动动脑子也能权衡出来那个利润大啊 而且目前这个项目刚开始,跟上就是吃肉,后期肯定会涨价

6👀3👍2

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

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

“山海资源对接” (@shanhaizydj), 135 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/shanhaizydj.

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.