Channel
@zjzjjsneso
On this record: Growth · Engagement · Posts · Citations · Cite this entry
101subscribers
+27 since we began measuring on 7 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004208585006 |
|---|---|
| Type | Channel |
| Username | @zjzjjsneso |
| Created | Between 1 May 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 November 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/zjzjjsneso |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 20:41 | 101 | +27 |
| 7 Nov 2026, 15:22 | 74 | first reading |
15 posts held, back to 7 November 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 7 November 2026 |
|---|---|
| Posts held | 15 (7 November 2026 – 7 November 2026) |
| Views total | 1,014 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 15: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.
Telegram’s own ‘edited’ marker: 0 of 15 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🎰 宝安中心希雅半价抽奖 📮 参与条件： 🎫 加入-深圳研究协会备用 🎫 加入-深圳研究协会 └ 🎟️ 发言数大于 10 条 🎫 加入-希雅（日常分享） 🎫 加入-深圳研究协会报告录 🎫 加入-深圳研究协会榜 🎁 奖品内容： 💰️ 半价p × 1 ⚠️ 抽奖说明： 1.中奖请在24小时之内联系老师 2.七天内使用，写报告素质出击 3.退群及频道默认放弃抽奖资格 炸号者无效 4.禁止🚫刷屏乱水 5. 深圳研究协会群内每日现金红包🧧 半价劵 等你来拿 🔋 人品加成：⚡️× 9 规则 📅 开奖日期：(北京时间) 2026年11月11日 16时16分00秒
🎰 宝安希雅P半价工兵卷 📮 参与条件： 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-希雅（日常分享） 🎫 加入-野寻 · 深圳学生交流群 └ 🎟️ 发言数大于 15 条 🎫 加入-野寻 · 深圳修车档案 🎫 加入-野寻 · 深圳活动公告 🎫 加入-野寻 · 深圳打卡通告群 🎁 奖品内容： 💰️ 宝安希雅P半价工兵卷 × 1 ⚠️ 抽奖说明： 1.中奖24小时之内联系南汐发放工兵凭证 @chase_nx 2.3天内完成报告向 @chaseszxc_bot 提交 3.出击必须提交报告！ 🔋 人品加成：⚡️× 9 规则 📅 开奖日期：(北京时间) 2026年11月09日 20时00分00秒
希雅（日常分享） pinned a photo
♥️CHASE | ♡ SHENZHEN 💌 0条车评，综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 艺名 : #希雅 地区 : #宝安区 宝安中心 数据 : 2005_165_49_B 价格 : #12P #22PP #35YE 服务 : #舌吻 #69 #角色扮演 #可外出 #可过夜 标签 : #兼职学生 🌍 联系老师 ✉️ 评价老师 真实大学生 可看证 不是本人退双倍 💌 学生交流 💌 作业评价 💌 工兵活动 💌 会员制度
https://t.me/n6s6s
希雅（日常分享） pinned a photo
🎁更多抽奖 https://t.me/xiu8che 🎟️ 抽奖标题：宝安希雅老师半价券抽奖 📪抽奖说明：中奖者机器人会发送中奖信息 汤臣一品独家福利 中奖截图联系老师：@xiyao05 老师信息：https://t.me/tcypa5/4305 🎫 参与条件: 🎫 加入-深圳【汤臣一品】精选榜 🎫 加入-汤臣一品学生会 🔰 （修车白嫖出击） 🎫 加入-希雅（日常分享） 🎁 奖品内容: 💰️ p半价券 × 1 📅 开奖时间：2026-11-10 00:00自动开奖 👉 参与抽奖链接: https://t.me/tgLotteryuw8bot?start=join-L179405728087
🎁 希雅老师半价优惠活动 积分抽奖（定时开奖） ├开奖时间: 2026-11-10 21:01 ├参与需加入: │⭐ 深圳花荟群 │└消耗积分: 5 │🎫 希雅（日常分享） │🎫 深圳花荟资源录 │🎫 深圳花荟动态榜 │🎫 深圳花荟日记 ├奖品列表: ├单P半价劵 × 1 ├加成上限: 50次 ├抽奖说明：抽奖消耗5积分，社群签到就有10积分，人人可无门槛参加本次优惠活动 注：1.有效期5天，过期无效，花荟群回收！ 2.工兵专属补贴金活动，凭中奖记录联系老师兑奖，不可折现，属约课抵现！ 3..炸号中奖作废回收！ 4.中奖出击后需要提供真实报告给与群里发布，供后面群友出击参考！ 中奖联系：@xiyao05 ├发奖人员：希雅 宝安中心 [如何参与？]点击下面抽奖按钮消耗5积分，参与抽奖
https://t.me/luolibang/5748
🎉 茶百道希雅-半价卷 🎁 奖品清单 • p半价卷（必须写报告） × 1 🛡️ 参与条件 • 加入 深圳茶百道【免费上榜】 • 加入 希雅（日常分享） • 加入 深圳茶百道娱乐榜 • 加入 深圳茶百道报告 • 参加抽奖后需在 深圳茶百道【免费上榜】 内发言20次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10奶茶币 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-11-11 23:36:00 📜 抽奖说明 ①本次活动由老师本人赞助 ②兑奖联系老师 ③开奖日起奖品有效期5天 ④兑奖后不写报告拉黑踢出群 ⑤出击后提交报告到：@lele585_bot ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
主群: https://t.me/mzcxutoe 榜单: https://t.me/NUFthre 📡 上榜管理：@chaoliu123_bot
希雅（日常分享） pinned a photo
Showing the 12 most recent of 15 posts we hold for @zjzjjsneso. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 10 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.
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.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“希雅（日常分享）” (@zjzjjsneso), 101 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/zjzjjsneso.
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.