Channel
@zjndufuf
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
798subscribers
-99 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003696764852 |
|---|---|
| Type | Channel |
| Username | @zjndufuf |
| Created | 28 December 2025 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/zjndufuf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 15:58 | 798 | -86 |
| 7 Aug 2026, 13:09 | 884 | -13 |
| 6 Aug 2026, 19:50 | 897 | no change |
| 6 Aug 2026, 19:49 | 897 | first reading |
19 posts held, back to 28 December 2025 — 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (28 December 2025 – 6 August 2026) |
| Views total | 32 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 19:50 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 19 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 28 December 2025 to 6 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.
🔥TeleTop 频道推荐 📢TGRSS 总频道🔥Telegram ... 📢【真人】DB｜PA｜DG 📢Cosplay写真|封疆疆V 📢【一手】谷歌邮箱💋 推特账号💋ins... 📢电报精准获客｜高效涨粉 📢吃瓜搞笑 🪻 📢cosplay|六二二同学 📢电报零粉起步轻松涨粉 📢远控搭建修复. 📢欧博代理 亚星代理 欧博私网 亚星私网 💎广告推荐 📢东南亚今日头条|新闻|爆料|悬赏|通缉|... 📢182体育综合平台,电子,棋牌,百家乐,... 📢✅【辉煌娱乐城93.CC】柬埔寨某盘总3... 🔍互推公示 🪧流量互推说明
来自速搜推荐 @SSOU 📢美女|性感热舞|火辣摇摆 📢亚星包杀 欧博包杀 亚星... 📢缅甸◉新闻曝光🌎 📢欧博代理 欧博私网 亚星... 📢科学·科普·气象·生物·... 📢🇹🇼本土優質外送茶推... 📢欧博包杀 欧博私网 亚星... 📢足球下注 世界杯买球 世... 📢泰国新闻 🌎 📢超级文爱语爱色涩裸聊 📢性感瑜伽|美女紧身裤|短... 📢🥇🥇🥇温州商务kt... 📢利博私网🅰️万利私网�... 📢深圳95口爆会所 📢万利私网🅰️欧博私网�... 👉流量互推规则介绍💥 以下是广告推荐 📢⚽️爱博体育-佣金55%-玩家首存即升VIP7等级⚽️ ✅【铂莱娱乐bolai.com】8年老台 世界杯指定投注平台 全网上押1300万u 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 📢🅾️免费试玩✅大客必备✅注册送158🅾️ 📢⚽️注册送138🧧百家乐/棋牌/电竞体育信誉平台 🇨🇳 简体中文包 ————————…
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
来自速搜推荐 @SSOU 📢她在照顾过程中彻底沉沦 📢中本葱姜蒜 📢利博代理 利博官网 利博... 📢欧博代理 亚星代理 欧博... 📢南歌 ♡ 北诗 📢万利私网🅰️亚星私网�... 📢欧博代理 亚星代理 欧博... 📢亚星私网/欧博私网/利博... 📢知识|黑科技❤️ 📢利博官网 利博代理 利博... 📢欧博官网 亚星官网 皇冠... 📢亚星私网 欧博私网 利博... 📢全网稀缺资源 📢亚星私网🅰️欧博私网�... 📢欧博私网🅰️万利私网�... 👉流量互推规则介绍💥 以下是广告推荐 ✅【铂莱娱乐bolai.com】8年老台 世界杯指定投注平台 全网上押1300万u 📢⚽️注册送138🧧百家乐/棋牌/电竞体育信誉平台 ✅东南亚大事件✅柬埔寨大事件✅东南亚新闻 🚀蓝图数据🚀SDK+DPI｜106通道技术分析全行业💰技术实力诚邀合作🔥 📢球速体育相信品牌的力量、老品牌值得信赖、不限ip、免实名。 🇨🇳 简体中文包 ————…
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
来自速搜推荐 @SSOU 📢绅士福利中文频道 📢【七七】网贷数据|股票数... 📢🔞爱撸管|萝莉|国产|... 📢LSP学舞蹈 📢黄油社永久免费 📢中国石油洗口-话费代充洗... 📢频道帖子浏览量｜群组上粉 📢车展模特|现场直拍|性感... 📢电报零粉起步轻松涨粉 📢利博代理 利博官网 利博... 📢亚星代理 欧博代理 亚星... 📢皇冠百家乐 欧博百家乐 ... 📢科技怪谈|奇闻异事|真实... 📢足球比赛 世界杯比赛 世... 📢午夜资源馆 👉流量互推规则介绍💥 以下是广告推荐 📢🅾️免费试玩✅大客必备✅注册送158🅾️ 📢182体育 2026世界杯指定投注平台、 免实名、不限ip、u存u提无上限 ✅南风数据全行业✅，sdk，DPI，106短信劫持，诚邀合作 ✅东南亚大事件✅柬埔寨大事件✅东南亚新闻 📢XX789🔞成人资源一站式导航 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设…
❤1
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
Showing the 12 most recent of 19 posts we hold for @zjndufuf. 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 — 330,846 of 1,548,671entries 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.
Named by 33 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@zjndufuf named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“欧博私网 皇冠私网 欧博包杀 皇冠百家乐” (@zjndufuf), 798 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/zjndufuf.
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.