Telegram RegisterThe public register of Telegram
Telegram profile photo for 木牌本地商家导航

Channel

木牌本地商家导航

@HDJPZ_MPNav

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

32,582subscribers

-4,801 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001875077884
TypeChannel
Username@HDJPZ_MPNav
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live23 October 2026
Measurements held47
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/HDJPZ_MPNav

Topic

Local community — 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 87% 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

27,59247,68037,6367 August 2026 — 37,383 subscribers7 August 2026 — 37,375 subscribers8 August 2026 — 37,320 subscribers9 August 2026 — 37,216 subscribers10 August 2026 — 37,059 subscribers11 August 2026 — 37,022 subscribers12 August 2026 — 29,029 subscribers13 August 2026 — 28,250 subscribers14 August 2026 — 28,250 subscribers15 August 2026 — 28,163 subscribers16 August 2026 — 28,074 subscribers17 August 2026 — 27,928 subscribers18 August 2026 — 27,787 subscribers19 August 2026 — 32,361 subscribers20 August 2026 — 47,680 subscribers21 August 2026 — 47,652 subscribers23 August 2026 — 47,583 subscribers24 August 2026 — 44,221 subscribers25 August 2026 — 43,711 subscribers26 August 2026 — 42,839 subscribers27 August 2026 — 38,403 subscribers28 August 2026 — 38,234 subscribers29 August 2026 — 37,975 subscribers30 August 2026 — 37,839 subscribers1 September 2026 — 37,558 subscribers2 September 2026 — 37,339 subscribers3 September 2026 — 37,261 subscribers4 September 2026 — 37,047 subscribers7 September 2026 — 31,518 subscribers10 September 2026 — 31,165 subscribers12 September 2026 — 30,836 subscribers14 September 2026 — 30,674 subscribers15 September 2026 — 30,504 subscribers18 September 2026 — 30,257 subscribers1 October 2026 — 28,722 subscribers6 October 2026 — 28,037 subscribers10 October 2026 — 27,592 subscribers13 October 2026 — 30,602 subscribers15 October 2026 — 33,124 subscribers16 October 2026 — 32,994 subscribers17 October 2026 — 32,929 subscribers18 October 2026 — 32,877 subscribers19 October 2026 — 32,835 subscribers20 October 2026 — 32,775 subscribers21 October 2026 — 32,702 subscribers22 October 2026 — 32,618 subscribers23 October 2026 — 32,582 subscribers32,5827 August 202623 October 2026
47 measurements spanning 77 days, net -4,801. 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 24,579–50,693 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
23 Oct 2026, 10:2732,582-36
22 Oct 2026, 07:3732,618-84
21 Oct 2026, 02:4832,702-73
20 Oct 2026, 03:3732,775-60
19 Oct 2026, 01:0132,835-42
18 Oct 2026, 02:0732,877-52
17 Oct 2026, 03:0532,929-65
16 Oct 2026, 06:2032,994-130
15 Oct 2026, 05:3633,124+2,522
13 Oct 2026, 23:4630,602+3,010
10 Oct 2026, 22:2027,592-445
6 Oct 2026, 20:3728,037-685
1 Oct 2026, 20:3828,722-1,535
18 Sept 2026, 09:5930,257-247
15 Sept 2026, 23:5930,504-170
14 Sept 2026, 04:1630,674-162
12 Sept 2026, 14:1830,836-329
10 Sept 2026, 10:5931,165-353
7 Sept 2026, 06:5631,518-5,529
4 Sept 2026, 15:5737,047first reading

Engagement

No public post preview. We read this entry on 14 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

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.

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

“木牌本地商家导航” (@HDJPZ_MPNav), 32,582 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/HDJPZ_MPNav.

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.