Channel
@shuzi12312
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 12 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004452466386 |
|---|---|
| Type | Channel |
| Username | @shuzi12312 |
| Created | 6 September 2026 — measured — dated from the channel’s first post |
| First recorded | 17 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/shuzi12312 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 05:22 | 2 | no change |
| 12 Sept 2026, 08:47 | 2 | first reading |
4 posts held, back to 6 September 2026 — 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 page of 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 September 2026 |
|---|---|
| Posts held | 4 (6 September 2026 – 6 September 2026) |
| Views total | 230 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Sept 2026, 05:22 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.
代理部 推广专员 5 直招 业绩岗 迪拜 不限 20-35 无 中文 中国 1800U 转 2000+提成 "12休2（满半年休15） 两班倒" "1、负责国内主流社交媒体及内容平台的推广工作，挖掘潜在用户资源。 2、通过各类线上渠道进行用户引流与拓展，持续扩大推广渠道。 3、维护现有推广渠道关系，提升用户转化及活跃度。 4、根据市场情况不断尝试新的推广方式，提升整体推广效果。 5、收集市场信息及用户反馈，及时优化推广策略。" "1、熟悉国内主流社交媒体平台（如社群平台、短视频平台、论坛等）优先。 2、具备一定的网络推广或渠道拓展经验。 3、具备良好的沟通能力和执行力，能够独立完成推广任务。 4、工作积极主动，责任心强，2年以上BC体育行业工作经验。"
运营部 运营专员 2 直招 职能 迪拜 不限 20-35 无 中文 外籍 1800U 转 2000+绩效 "12休2（满半年休15） 两班倒" "1、参与游戏平台综合运营工作，包括后台操作与设置、活动审核与派发、数据统计与分析等 2、解决玩家、代理关于体育、真人、彩票、棋牌等等相关游戏、结算、登录、派奖等问题 3、对接第3方，协调处理玩家关于游戏中各类问题 4、处理账单、数据等各类需求，查询代理，玩家账务相关问题" "1、2年以上BC体育行业运营、维护、客服等岗位工作经验 2、熟悉真人、体育及彩票某一个或者多个产品 3、精通Excel,PPT等常用办公软件 4、亲和力，善于与人沟通协调，做事积极主动，学习能力强，能主动发掘问题和提出解决方案 5、暂不考虑大陆籍，条件优秀者可适当放宽要求"
运营部 运营主管 1 直招 职能 迪拜 不限 20-35 无 中文 中国 面议（根据经验评估）+绩效 "12休2（满半年休15） 两班倒" "1.负责运营后台的权限管理、角色管理、内容审核以及数据报表等工作； 2.搭建平台运营各流程，并按照流程执行处理各事项，包括特殊申请如信息更改，异常注单咨询，游戏规则矛盾，以及其他异常问题处理等 3.运营相关的配置设定与定期更新，包括如活动配置，轮播banner图配置，参数配置等 4.关注和对比同类型产品，以及行业动态，利用各方渠道收集内部与外部建议，识别并理解用户需求，优化用户游戏体验。" "1.具备2年以上行业C端运营相关工作经验者，熟悉并热爱体育竞技游戏行业，足球和篮球优先。 2.有整体的行业运营理论框架，且能够落地执行，并根据实际运营情况做出对应调整。 3.逻辑清晰，沟通能力强，抗压性强，执行力强，综合素质高，能够站在用户、运营、市场等不同视角思考问题"
Channel created
Showing the 4 most recent of 4 posts we hold for @shuzi12312. 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.
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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“迪拜数字集团” (@shuzi12312), 2 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/shuzi12312.
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.