Telegram RegisterThe public register of Telegram
Telegram profile photo for DY号商通知频道

Channel

DY号商通知频道

@dyhaoshangtongzhi

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

453subscribers

-10 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1003974412402
TypeChannel
Username@dyhaoshangtongzhi
Created7 May 2026 — measured — dated from the channel’s first post
First recorded31 August 2026
Last confirmed live12 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/dyhaoshangtongzhi

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

Growth

45346345831 August 2026 — 463 subscribers31 August 2026 — 463 subscribers10 September 2026 — 459 subscribers17 September 2026 — 455 subscribers2 October 2026 — 454 subscribers12 October 2026 — 453 subscribers31 August 202612 October 2026
6 measurements spanning 42 days, net -10. 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 452–465 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 14:39453-1
2 Oct 2026, 11:56454-1
17 Sept 2026, 05:18455-4
10 Sept 2026, 03:55459-4
31 Aug 2026, 03:45463no change
31 Aug 2026, 03:35463first reading

Engagement

10 posts held, back to 7 May 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 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 10 posts for this entry, the most recent from 7 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Jun 2026, 11:34 UTC≈2,010 viewsread 31 August 2026

清退的号,后面有位置了,都可以重新上回来哈,没清退的还是正常按半天结算,安抚手底下的号主不要顶号,顶号的复工当天直接退,不予结算!

6 Jun 2026, 00:01 UTC926 viewsread 31 August 2026
Forwarded from @linlin22256

通知 由于环境影响,公司暂时停工2-3天,停工期间公司不使用号,号钱将对半算,复工了统一结算。跟公司合作久的号商都知道我们从来没有拖欠过号款,形势不好我们也是迫不得已,希望大家能理解一下。大家安抚好手底下的号主不要去顶号,顶号的复工当天直接退,不予结算哈!复工了第一时间会在频道里通知

5 Jun 2026, 16:13 UTC860 viewsread 31 August 2026
Forwarded from @linlin22256

张清跟长风已经被公司开除,跟他有任何交易被骗,概不负责哈,有什么事联系,@men8859 @pingguo888888888888 @gjbqz @gjbcz1 @DZ7788M

2 Jun 2026, 16:26 UTC≈1,250 viewsread 31 August 2026

通知 明天早上11点开工 叫号主别顶号 明天开始结账

1 Jun 2026, 10:23 UTC≈1,150 viewsread 31 August 2026

通知📢 由于特殊情况! 公司放假 2号开始我们暂时不使用号 号款费用将会对半结算 通知号主别自己顶号,PC不要退设备改资料 今天开始后面的款开工一起结算 望大家谅解!!! 多关注此频道 有变会及时通知!

7 May 2026, 11:56 UTC≈1,820 viewsread 31 August 2026

明天停工一天 ,后天统一结算,请大家耐心等待,都合作这么久了,也没有说拖欠过租号费用,这次是特殊情况,特殊对待,大家稍安勿躁哈!正常使用的后天都会按全天结算,该给号主的还是给号主,不要出现顶号的情况哈,若出现顶号改资料的,后天直接退,不予结算!

Showing the 10 most recent of 10 posts we hold for @dyhaoshangtongzhi. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“DY号商通知频道” (@dyhaoshangtongzhi), 453 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/dyhaoshangtongzhi.

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.