Telegram RegisterThe public register of Telegram
Telegram profile photo for 董事会业务通知频道

Channel

董事会业务通知频道

@Dsh_888

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

27,759subscribers

-16,201 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001525707602
TypeChannel
Username@Dsh_888
Description担保导航频道:@Dsh_DB888/@dshdb 业务通知频道: @Dsh_888 公群频道:@dshgq1 所有交易认准 担保 谨防代码
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/Dsh_888

Topic

Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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

27,75943,96035,859.57 August 20265 November 2026
61 measurements spanning 90 days, net -16,201. 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 25,329–46,390 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
5 Nov 2026, 22:5427,759-108
5 Nov 2026, 01:2027,867-64
4 Nov 2026, 02:5027,931-70
3 Nov 2026, 02:2828,001-39
2 Nov 2026, 03:1628,040-40
1 Nov 2026, 04:5828,080-73
31 Oct 2026, 05:3128,153-128
30 Oct 2026, 03:0028,281-87
28 Oct 2026, 23:5028,368-40
28 Oct 2026, 01:1128,408-109
26 Oct 2026, 22:4728,517-82
26 Oct 2026, 00:0528,599-110
24 Oct 2026, 20:4828,709-64
23 Oct 2026, 20:1928,773-42
22 Oct 2026, 21:4628,815-44
21 Oct 2026, 15:3528,859-27
20 Oct 2026, 11:3628,886-4
19 Oct 2026, 13:1528,890-42
18 Oct 2026, 15:2728,932-42
17 Oct 2026, 13:3628,974first reading

Engagement

2,353 posts held, back to 7 August 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 167 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.115%
avg views ÷ 27,759 subscribers
Avg views / post
32.0
795 posts measured
Reaction rate
2.55%
reactions ÷ views · ER floor
Posts in window
795
of 2,353 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. It is computed over the 25 of 795 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 November 2026
Posts held2,353 (7 August 2026 – 6 November 2026)
Views total25,426
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 14:21 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
≈378,000
Videos
≈92
Links
≈859

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

Reaction mix

27 reactions across 27 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1866.7%
❤933.3%

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 32 of the 1,000 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 30 September 2026 to 6 November 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

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

6 Nov 2026, 14:16 UTC11 viewsread 6 November 2026

🌩一手ai24小时在线 中国免 邮政免 认准群里头衔 😂😂😂😂中国AI免密 🤣🤣🤣🤣 建设AI 无需沉淀 秒出款 😂😂😂😂邮政AI免密 任意卡/地方AI取款密码来 九天狐24小时客服🌩 @JTH9767

Signed 九天狐 🇨🇳(24小时在线)

6 Nov 2026, 14:15 UTC12 viewsread 6 November 2026
Photo

2999支付宝必过码 吃余额和卡付必过 必过 必过!首次不过赔u 不过你来骂我!不害人!吃全额,米奇重回 必属独家!有图有真相,从不搞虚假宣传,认准米奇 @miqi0861 花重金购买的唯一四字ID米奇 @syyy

Signed 米奇(认准@syyy)

6 Nov 2026, 14:13 UTC16 views1 reactionsread 6 November 2026

建设ai正常 上去稳吃1.3w➕ 中国ai免密正常 各大行免密正常 各大行小行 ai正常 境外一码4000连刷 高铁正常 345信用卡正常 大额数字正常 秒出款 剑7 @jian7

👍1

Signed 剑7

6 Nov 2026, 14:13 UTC8 views1 reactionsread 6 November 2026
Photo

云扣zc出款2-10w 任意卡支持信用卡 境外大额 数字 云扣 正常 建设ai 中国ai 大额正常 首次卡 多渠道全额出款 ❤️认准思悦 ✈️@siyue8188

👍1

Signed 思悦(招远控 驾驶证团队)

6 Nov 2026, 14:13 UTC86 views1 reactionsread 6 November 2026
Photo

支付宝独家通道全额拿下,来鱼来鱼 必过必过,宝子们来鱼来鱼,美女姐姐在线接单中 @yaoyao1230

👍1

Signed 瑶瑶 (24小时码接回u)

6 Nov 2026, 14:10 UTC12 views1 reactionsread 6 November 2026
Photo

💋个人码、经营码、聚合码、缴费、话费、 2️⃣群引导、反扫、 大麦、 支付宝亲情卡 3️⃣数字 高铁 苹果 建设中国Ai正常 ❄️四大银行 取款Ai 快捷5码一万 认准✈️ @Wan5088

👍1

Signed 浪虎一手AI支付工作频道

6 Nov 2026, 14:05 UTC16 views1 reactionsread 6 November 2026

财富钱包卸货 单笔2000-5000 税务微信2千-1万连刷 无视改密刷脸 扫码热力 户号热力统统额度都有 微信热力原密必过 2000-10000连刷 @king99456

👍1

6 Nov 2026, 14:02 UTC17 views1 reactionsread 6 November 2026
Photo

🕶支付宝境外码连刷 两笔 远控可过 🥵@yyyqqq

👍1

Signed 燕青

6 Nov 2026, 14:01 UTC17 views1 reactionsread 6 November 2026

建设ai正常 上去稳吃1.3w➕ 中国ai免密正常 各大行免密正常 各大行小行 ai正常 境外一码4000连刷 高铁正常 345信用卡正常 大额数字正常 秒出款 剑7 @jian7

👍1

Signed 剑7

6 Nov 2026, 13:58 UTC20 views1 reactionsread 6 November 2026

云扣 聚分期 境外 数字 快捷 大额境外需取款单笔5万内 邮储Ai免密 其他银行带取款 光亭✈️@guangti0

👍1

Signed 光亭(效率出款)

6 Nov 2026, 13:53 UTC29 views1 reactionsread 6 November 2026

建设ai正常 上去稳吃1.3w➕ 中国ai免密正常 各大行免密正常 各大行小行 ai正常 境外一码4000连刷 高铁正常 345信用卡正常 大额数字正常 秒出款 剑7 @jian7

👍1

Signed 剑7

6 Nov 2026, 13:45 UTC47 views1 reactionsread 6 November 2026
Photo

2999支付宝必过码 吃余额和卡付必过 必过 必过!首次不过赔u 不过你来骂我!不害人!吃全额,米奇重回 必属独家!有图有真相,从不搞虚假宣传,认准米奇 @miqi0861 花重金购买的唯一四字ID米奇 @syyy

👍1

Signed 米奇(认准@syyy)

Showing the 12 most recent of 2,353 posts we hold for @Dsh_888. 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

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.

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.

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

“董事会业务通知频道” (@Dsh_888), 27,759 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Dsh_888.

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.