Telegram RegisterThe public register of Telegram
Telegram profile photo for 贫民窟导航频道🌱

Channel

贫民窟导航频道🌱

@PMKZZNB

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

45,015subscribers

+763 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-1002406674060
TypeChannel
Username@PMKZZNB
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held19
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/PMKZZNB

Growth

44,25245,01544,633.57 August 2026 — 44,252 subscribers7 August 2026 — 44,252 subscribers8 August 2026 — 44,294 subscribers9 August 2026 — 44,312 subscribers10 August 2026 — 44,334 subscribers11 August 2026 — 44,366 subscribers12 August 2026 — 44,382 subscribers14 August 2026 — 44,436 subscribers16 August 2026 — 44,546 subscribers17 August 2026 — 44,613 subscribers18 August 2026 — 44,681 subscribers19 August 2026 — 44,750 subscribers20 August 2026 — 44,804 subscribers21 August 2026 — 44,835 subscribers22 August 2026 — 44,879 subscribers23 August 2026 — 44,901 subscribers25 August 2026 — 44,924 subscribers26 August 2026 — 44,975 subscribers27 August 2026 — 45,015 subscribers7 August 202627 August 2026
19 measurements spanning 20 days, net +763. 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 44,138–45,129 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 04:5745,015+40
26 Aug 2026, 03:3444,975+51
25 Aug 2026, 04:5244,924+23
23 Aug 2026, 23:2544,901+22
22 Aug 2026, 10:3444,879+44
21 Aug 2026, 01:2444,835+31
20 Aug 2026, 03:5244,804+54
19 Aug 2026, 06:4644,750+69
18 Aug 2026, 09:1144,681+68
17 Aug 2026, 11:3644,613+67
16 Aug 2026, 02:2544,546+110
14 Aug 2026, 09:1444,436+54
12 Aug 2026, 21:5844,382+16
11 Aug 2026, 22:1144,366+32
10 Aug 2026, 23:2344,334+22
9 Aug 2026, 21:5244,312+18
8 Aug 2026, 19:2444,294+42
7 Aug 2026, 16:2244,252no change
7 Aug 2026, 14:4544,252first reading

Engagement

21 posts held, back to 21 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 47 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
16.5%
avg views ÷ 45,015 subscribers
Avg views / post
7,410
4 posts measured
Reaction rate
0.749%
reactions ÷ views · ER floor
Posts in window
4
of 21 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 August 2026
Posts held21 (21 August 202516 August 2026)
Views total29,650
Reactions total222
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Aug 2026, 03:42 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

Video runtime
6m 06s
Average length
1m 32s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1,127 reactions across 21 posts, in 20 distinct kinds. The most used accounts for 34.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
38334.0%
👍25422.5%
😭15113.4%
🥰887.81%
🤬756.65%
😍635.59%
👎322.84%
🤓201.77%
🤔131.15%
🤯80.71%
🗿60.532%
👏50.444%
🔥50.444%
🕊50.444%
😁50.444%
🍌40.355%
😱40.355%
🤩40.355%
😇10.089%
🙏10.089%

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

Measured over the 21 most recent posts we hold, published 21 August 2025 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
2
of 21 we hold a reading for · 10%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @PMKZZNB. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 21 most recent posts we hold for this entry, published 21 August 2025 to 16 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

16 Aug 2026, 03:02 UTC≈5,010 views37 reactionsread 27 August 2026

体验服注入购卡: https://o.8x.fit/shop/UPABA104 已适配最新体验服,安装包看下单后的使用说明

👍30🕊52

14 Aug 2026, 14:27 UTC≈6,090 views51 reactionsread 27 August 2026
File

贫民窟免费纯C-3.0 ## 2026年8月14日 更新日志: 1.修复人物数组没效果 被下发加密绘制没效果了在设置页面切换人物数组可解决该问题 该版本为临时更新,全新版本即将与大家见面

👍377🍌4🥰3

13 Aug 2026, 06:30 UTC≈6,850 views22 reactionsread 27 August 2026

贫民窟最新QQ群:1022121237 体验服注入的包在群文件,自己进群下载

👍166

5 Aug 2026, 00:55 UTC≈11,700 views112 reactions1 Starread 27 August 2026
File

和平精英追踪-11.0 更新内容: 1.更换半裸奔追踪函数(修复特征) 直装网盘: https://wannianyyds.lanzouv.com/b007uiraed 密码:6666 直装有旁路,目前不封号,暂不更新(懒)

🤬6021👍19👎10🥰2

22 Jul 2026, 11:43 UTC≈16,500 views175 reactionsread 27 August 2026
File

体验服免费追踪(最后一次更新) 更新内容: 1.适配最新体验服

😭112👍3612🤔12🤬2👏1

21 Jul 2026, 01:59 UTC≈15,200 views27 reactionsread 27 August 2026

和平精英体验服可以申请资格了 申请方法:和平营地→首页的营地工具→体验服申请 预计开服时间:8月中旬 现在有足够的时间把申请要求做完

21👍4🔥2

20 Jul 2026, 07:43 UTC≈10,600 views23 reactionsread 27 August 2026

贫民窟主频道 --------------------------- https://t.me/+gh7ggNd-EBZiYTZl https://t.me/+gh7ggNd-EBZiYTZl --------------------------- 点击上面链接进入主频道↑ 认准十万订阅量主频道 请及时退出假频道 假频道存在被诈骗的风险

16👍7

7 Jul 2026, 10:28 UTC≈16,500 views29 reactions3 Starsread 27 August 2026

贫民窟最新QQ群:1022121237 有问题可以进来反馈,没有也可以进来聊聊天 有好东西都会分享在QQ群

👍214😱4

3 Jul 2026, 10:29 UTC≈18,400 views22 reactionsread 27 August 2026
Video

康娜美化使用以及写配置教程 电报下载速度慢点我前往浏览器查看

👍166

2 Jul 2026, 01:55 UTC≈17,300 views34 reactionsread 27 August 2026
File

贫民窟免费纯C-2.9 更新内容: 1.修复子弹追踪硬件断点方案没效果

👍284🔥2

1 Jul 2026, 08:48 UTC≈16,600 views15 reactionsread 27 August 2026

贫民窟最新QQ群:1022121237 有问题可以进来反馈,没有也可以进来聊聊天 有好东西都会分享在QQ群

👍113😇1

1 Jul 2026, 08:48 UTC≈17,400 views11 reactionsread 27 August 2026
File

康娜配置美化-2.8 更新内容: 1.新增物品数据表比较 2.修复人物美化不捡头盔背包也会自动美化 3.改进了物品数据表导出的格式 4.优化启动方式,可在任意路径执行程序

11

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

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

“贫民窟导航频道🌱” (@PMKZZNB), 45,015 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/PMKZZNB.

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.