Telegram RegisterThe public register of Telegram
Telegram profile photo for 指南针出海 供需频道

Channel

指南针出海 供需频道

@znzgxpd

2 usernames

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

11,133subscribers

-522 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002229669962
TypeChannel
Usernames@zhinanzhen0011 @znzgxpd
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live18 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/znzgxpd

Growth

11,13311,65511,39415 August 2026 — 11,655 subscribers15 August 2026 — 11,655 subscribers15 August 2026 — 11,561 subscribers16 August 2026 — 11,467 subscribers16 August 2026 — 11,343 subscribers17 August 2026 — 11,274 subscribers17 August 2026 — 11,201 subscribers18 August 2026 — 11,133 subscribers15 August 202618 August 2026
8 measurements spanning 3 days, net -522. 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 11,055–11,733 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 12:0411,133-68
17 Aug 2026, 21:0411,201-73
17 Aug 2026, 13:2411,274-69
16 Aug 2026, 22:2311,343-124
16 Aug 2026, 04:1311,467-94
15 Aug 2026, 18:1611,561-94
15 Aug 2026, 02:4711,655no change
15 Aug 2026, 02:4711,655first reading

Engagement

22 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
40.0%
avg views ÷ 11,133 subscribers
Avg views / post
4,460
22 posts measured
Reaction rate
1.64%
reactions ÷ views · ER floor
Posts in window
22
of 22 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 3 of 22 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 16 August 2026
Posts held22 (27 July 202616 August 2026)
Views total98,055
Reactions total266
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 09:09 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.

Reaction mix

266 reactions across 3 posts, in 15 distinct kinds. The most used accounts for 11.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😈3011.3%
🍌2910.9%
🤬2910.9%
👎2810.5%
🥱2810.5%
🤮269.77%
😢228.27%
💩207.52%
🖕186.77%
💔176.39%
😡134.89%
20.752%
🔥20.752%
💋10.376%
🥰10.376%

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

Measured over the 22 most recent posts we hold, published 27 July 2026 to 16 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

16 Aug 2026, 20:53 UTC415 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品: 欧混交友 产品要求:收 欧混交友、WS接粉、25+男女不限、 有精筛、二筛的也可以,价格和质量一起提升!!! 主流国家为主、素材类型可以我们提供,人设多样,渠道不限!!! ✅联系方式: @hjin688 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

15 Aug 2026, 16:49 UTC763 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求产品:肯尼亚、贝宁 常规兼职 产品要求:收 肯尼亚、贝宁 兼职网赚粉、允许 常规素材图文视频 底粉肯尼亚4500、贝宁2300、可以打的私我!带素材私 ✅联系方式:@klxs995 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

14 Aug 2026, 18:44 UTC≈4,880 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品: 美国减肥药素材粉 产品要求:收美国减肥药素材粉(多肽粉),能打的私我,FB和TK 谷歌都可以,带上价格!!! 卡35+女性、人种不限、素材样式我们可以提供、代投也行、 海王工单底粉2W不到、还有一个新工单1000不到、有实力的来,价钱不是问题!! ✅联系方式: @QQvip85 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

14 Aug 2026, 13:24 UTC507 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品:✅(大量收)🇬🇧 英国 法国 网赚粉 (常规 口播 手工活素材)FB投流,TK官媒,INS 谷歌落地页 产品要求:✅(大量收)🇬🇧 英国 法国 网赚粉 (常规 口播 手工活素材)FB投流,TK官媒,INS 谷歌落地页 ✅(国家) 苹果rcs盘口包量 包机房 实力工作室来 ✅招募范围:Tik Tok官媒 Facebook诚招代投广告选手 📌 仅对接真实流量源 优先一手机房、自投团队合作 拒绝转包、虚假数据、多层中介 。 长期需求更新,欢迎资源方交流合作。不是广告来的参假一律全不结算 能验证机房的联系 ✅联系方式: @yema678678 @shanwan168 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验

14 Aug 2026, 12:39 UTC≈5,420 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品: 欧洲兼职/网赚粉 产品要求:Tk 谷歌 FB 欧洲地区看视频素材/线上素材/手工活素材/做任务/常规兼职,目前(德国、意大利、波兰、捷克、瑞士、丹麦)缺量 长期收量,随时放单测试,上门发素材和渠道、对应价格可谈。看上就会回复,彼此的时间都很宝贵废话少说,不预付,骗子不用来、可担保 ✅联系方式: @yalisd88 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

13 Aug 2026, 21:22 UTC≈5,080 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求产品:巴西 印尼 产品要求:收 巴西 印尼兼职网赚粉、常规素材图文视频都可以。。FB/TK/GG 都可以!!! 报价带素材和渠道,发地址验证机房,中介勿扰.......目前底粉不超1W、新盘价格合适回复! ✅联系方式:@spiygod 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

13 Aug 2026, 03:20 UTC≈3,660 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品:罗马尼亚 官媒 兼职 商品要求:收罗马尼亚 官媒 兼职、做任务、看视频、常规都可以 只要官媒、不要FB、不要私信、不要数据!!! 担保不预付····带上价格素材私我,工单底粉2000不到,中介勿扰!!!! ✅联系方式: @kiss88you 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

12 Aug 2026, 19:06 UTC≈3,040 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品:厄瓜、墨西哥 兼职粉 产品要求:常规或者做任务的素材 渠道不限带上你的地址和素材 来有效沟通不浪费时间 合作先发地址和素材 盘口直收,现广立即下单,一手工作室来聊。 可以担保的来,验证机房、、、不预付!!!! ✅联系方式: @jdfur7 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

12 Aug 2026, 19:03 UTC≈5,840 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品:西班牙,意大利,手工兼职粉 打线索 产品要求:西班牙,意大利,手工兼职粉,tk官媒打线索表单的!西班牙5u一个日需5000,别的粉商打重复率一半不到,意大利4.5u一个日需2000个,重复率百分之20几,有实力的一手工作室来,打不动的单枪匹马的别来打扰啊,测得头都大 ✅联系方式: @wl67890 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

12 Aug 2026, 10:47 UTC≈4,370 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品:兼职网赚投流 产品要求:亚美尼亚 兼职粉 FB 官媒都可以 新工单 不到1000底 带上你的素材和价格,对应渠道!只担保不预付、可日结、假粉一律不付、会员来! ✅联系方式: @guug556 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

11 Aug 2026, 06:59 UTC≈6,250 views1 reactionsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品:欧混兼职 产品要求:收欧混常规兼职,:投流粉、官媒优先,fb也可以,年龄25+、售后22以下色和捣乱。目前底库4800 打WS接粉,来靠谱的粉商,可以担保的来!!!!带上价格和地址!!! ✅联系方式: @facai7_89 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

🔥1

10 Aug 2026, 16:34 UTC≈6,770 viewsread 18 August 2026

合作盘总需求—群内不定时更新推送❗️❗️❗️ 类型:需求 需求商品:日本、韩国交友粉 商品要求:收日本、韩国交友粉可以打私我、年龄要求35+,任意渠道。。 新工单,担保不预付····带上渠道和价格素材私我,不满意不回 ✅联系方式: @stool88 💎会员发布广告30U/条 💎非会员发布广告60U/条 🙅‍♂️付费广告真假未验证 办理广告联系👉小北 小东

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

Citation-graph rank

Citation-graph rank — 648,586 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“指南针出海 供需频道” (@znzgxpd), 11,133 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/znzgxpd.

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.