Telegram RegisterThe public register of Telegram

Channel

远程招商推广💋各种职能岗

@ZSmazouri

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

717subscribers

-8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002064139006
TypeChannel
Username@ZSmazouri
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/ZSmazouri

Growth

7177257217 Aug 2026, 17:26 — 725 subscribers8 Aug 2026, 02:05 — 725 subscribers8 Aug 2026, 13:47 — 717 subscribers7 Aug 2026, 17:268 Aug 2026, 13:47
3 measurements taken within a single day, net -8. 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 716–726 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 13:47717-8
8 Aug 2026, 02:05725no change
7 Aug 2026, 17:26725first reading

Engagement

17 posts held, back to 28 May 2025the 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 · 30 days
3.07%
avg views ÷ 717 subscribers
Avg views / post
22.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 17 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 27 July 2026
Posts held17 (28 May 202527 July 2026)
Views total22
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:05 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
8s
Average length
8s

Measured directly from 1 video 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

11 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 81.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
981.8%
👌19.09%
🥰19.09%

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

Measured over the 17 most recent posts we hold, published 28 May 2025 to 27 July 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

27 Jul 2026, 06:57 UTC22 viewsread 8 August 2026
Photo

你们都是怎么找到这种女朋友的呀 能教下我吗

7 Jul 2026, 09:23 UTC72 viewsread 8 August 2026
Photo

#动漫 #里番 #二次元 🤠>>>> 新闻曝光吃瓜<<<<🐸 🐣 中文语言包 🎵 IOS解除限制 🐺 中文语言包Ⅱ 🤬 狗推代理红蓝群 🧀>>>> 解锁长夜漫漫 <<<<🛟 😆动漫里番二次元 🐗猫鼠文案素材 😀东南亚新闻情报 🏋‍♀️内涵吃瓜猎奇 😛NTR反差女教师 🥰JK學妹的雙馬尾 🏯>>>>经典动漫里番目录<<<<😎 😄里番漫画本子 🐤动漫里番老番 🤤擦边吃瓜段子 🎖带派头像壁纸 🐴AV日本中文字幕 💜H漫本子涩里番 🐺>>>>>>新里番播放量排行<<<<<<🎢 😍商务桃子:https://t.me/tryzz

22 Mar 2026, 18:26 UTC≈4,300 views2 reactionsread 8 August 2026
Photo

招聘线上运营,可以兼职 要求头脑灵活,有telegram使用经验,ins,x推特使用者也可以 中文可以阅读 薪资人民币:2000+,远程线上可兼职

2

21 Mar 2026, 18:30 UTC≈4,270 views3 reactionsread 8 August 2026
Photo

新年快乐 🎧🎧【开云集团】泰国/迪拜/马来西亚/菲律宾官方直招🎧🎧 🐣亚洲龙头企业,体育综合盘🐣 ⭐️诚聘英才,年终奖13-17薪水⭐️ 【KY集团 岗位大全】 ♻️推广专员 ♻️维护专员 ♻️转化专员 ♻️推广组长 ♻️招聘专员 ♻️SEO专员 ♻️代理维护 ♻️运营专员 ♻️平台体验专员♻️渠道专员 ♻️SEO学徒 ♻️自媒体推广 ♻️风控专员 ♻️客服专员 ♻️发展专员 ♻️招商专员 ♻️红利专员 ♻️自媒体运营 ♻️UI专员 ♻️部门助理 ♻️网管专员 ♻️网络工程师 ♻️运维工程师 ♻️产品经理 ♻️初/中/高级产品专员 ♻️Web前端 ♻️Java高级/专家 ♻️ios开发工程师♻️安卓开发工程师 ♻️渗

2🥰1

18 Mar 2026, 16:45 UTC≈4,220 viewsread 8 August 2026
Photo

Telegram 简体中文语言包 语言包交流群组: https://t.me/JPZCHW 如果翻译不对或有异议或未翻译到的地方,可以在群组中交流讨论,谢谢! ----------------------------------------- 各个语言包: * 中文(简体)-聪聪: https://t.me/setlanguage/zhcncc * 中文(简体)-微软中文: https://t.me/setlanguage/mshans * 中文(简体)-简体: https://t.me/setlanguage/classic-zh * 中文(简体)-langCN: https://t.me/setlanguage/zhlangcn * 中文(简体)-瓜体: https://t.me/setlanguage/duang-zh-cn * 中文(简体)-瓜皮中文: https://t.me/setlanguage/duang-z

18 Mar 2026, 16:43 UTC≈4,170 viewsread 8 August 2026
Photo

常用的各个TG语言包(点击蓝色字体,即可安装表情包) 简体中文 【* 中文(简体)-聪聪 】 【* 中文(简体)-@zh_CN 】 【* 中文(简体)-简体】 【* 中文(简体)-瓜体】【* 中文(简体)-小哇🐸花里胡哨】 【* 中文(简体)-简体字】【* 中文(简体)-爱吃辣条的小学生】 【* 中文(简体)-江湖中文版 】 其他中文 【* 中文(香港)-繁体1】【* 中文(香港)-繁体2】【* 中文(香港)-广东话1】 【 * 中文(香港)-廣東話 】【* 中文(台灣)-正体】【* 中文(台灣)-繁体】 【* 中文(台灣)-文言】【* 中文(台灣)-魔法師】 日文 【* 日文】 注: 打开 Telegram 客户端,然后在客户端内点击语言包链接,再点击确认按钮即可转换为相应的语言界面。 这里提供简体中文和繁体中

19 Feb 2026, 07:11 UTC≈4,210 viewsread 8 August 2026
Photo

新年快乐 🎧🎧【开云集团】泰国/迪拜/马来西亚/菲律宾官方直招🎧🎧 🐣亚洲龙头企业,体育综合盘🐣 ⭐️诚聘英才,年终奖13-17薪水⭐️ 【KY集团 岗位大全】 ♻️推广专员 ♻️维护专员 ♻️转化专员 ♻️推广组长 ♻️招聘专员 ♻️SEO专员 ♻️代理维护 ♻️运营专员 ♻️平台体验专员♻️渠道专员 ♻️SEO学徒 ♻️自媒体推广 ♻️风控专员 ♻️客服专员 ♻️发展专员 ♻️招商专员 ♻️红利专员 ♻️自媒体运营 ♻️UI专员 ♻️部门助理 ♻️网管专员 ♻️网络工程师 ♻️运维工程师 ♻️产品经理 ♻️初/中/高级产品专员 ♻️Web前端 ♻️Java高级/专家 ♻️ios开发工程师♻️安卓开发工程师 ♻️渗

1 Nov 2025, 04:28 UTC≈4,300 viewsread 8 August 2026

#岗位需求: 招聘专员 #薪资待遇: 12K #上班时间: 9休6 #工作地点:菲律宾 清迈 均可 #岗位需求: 招聘助理 #薪资待遇: 12-15K #上班时间: 9休6 #工作地点:菲律宾 清迈 均可 #岗位需求: 招聘主管 #薪资待遇: . 面议 #上班时间: 9休6 #工作地点: 菲律宾 清迈 均可

1 Nov 2025, 04:27 UTC≈4,260 viewsread 8 August 2026

职位:风控组长(二审C端) 薪资:15-18K 工作时间:8休8 三班倒 餐補:12600-16500P 房補:17000P—22000P #岗位职责 审核各博彩项目的客户以及注单 报表分析并提供止损方案 协助建立风控后台 需协助相关部门解决客户疑问 #岗位要求 有体育以及其他博彩项目的风控经验 熟悉电脑操作以及办公软件 有足够的逻辑思考能力且能独自解决业务上的一些问题 优先能建议风控后台工具的实用性 会英文优先。 要求在菲或者斯里兰卡

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

Mentions

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

“远程招商推广💋各种职能岗” (@ZSmazouri), 717 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ZSmazouri.

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.