Channel
@chasenj_zypj
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5,622subscribers
+585 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002264048272 |
|---|---|
| Type | Channel |
| Username | @chasenj_zypj |
| Created | 11 June 2025 — measured — dated from the channel’s first post |
| First recorded | 30 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/chasenj_zypj |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 73% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 18:37 | 5,622 | +510 |
| 14 Sept 2026, 09:37 | 5,112 | +28 |
| 10 Sept 2026, 20:41 | 5,084 | +28 |
| 6 Sept 2026, 05:57 | 5,056 | +18 |
| 1 Sept 2026, 21:25 | 5,038 | +1 |
| 30 Aug 2026, 01:15 | 5,037 | no change |
| 30 Aug 2026, 01:00 | 5,037 | first reading |
3 posts held, back to 11 June 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 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 29 August 2026 |
|---|---|
| Posts held | 3 (11 June 2025 – 29 August 2026) |
| Views total | 6 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 01:15 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.
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.
♡ 芷宁严选 ♡ ⌚️ 评价时间：2026-08-29 👩🏻🎓 服务老师：小纯纯 👨🏻💻 留名：匿名 颜值：9.5 环境：8.8 身材：9 态度：8.5 服务：9.8 人照：9 综合：9.1 💌 服务过程 ： 今天周末休息，心有点痒痒的就约了小纯，还好离的不远。 到达战场洗浴，摸一摸粉嫩的馒头，摸摸小嫩嫩水出来了，滑滑的，确实可以，激动不已，小纯就帮我口了，直接快顶不住，怕受不了就直接后入式，没几分钟就第一次完事了。 然后就在床上聊聊天按按摩，摸来摸去哈哈哈，可能太久没出击了，太敏感一下出水，第二次总体还算正常，嗯嗯体验很不错👍好评 🔗 老师资料 ：https://t.me/chasenj_lsda/978
😀 野寻 · 南京修车导航 😀 ~秦淮风轻月色柔，金陵邂逅意相投~ ~天涯若得知心友，不负江南一段秋~ 新手中心 : 😀【野寻 · 南京使用手册】 😀 野寻大讲堂 └ 作业模版 └ 积分商城 └ 会员制度 └ 工兵模版 😀 南京榜单导航 └ 按价格 └ 按区域 └ 按服务 └ 按标签 😀 其他资源 └ 野寻· 南京外围 └ 野寻· 南京包养 └ 野寻· 南京商家 ⚡【野寻· 南京】榜单结构 ├ 学生交流群 @chasenj_jlq ├ 打卡通告群 @chasenj_tgq ├ 小喇叭 @chasenj_xlb ├ 榜单导航 @chasenj_bddh ├ 修车档案 @chasenj_lsda ├ 精选榜单 @chasenj_lsjx ├ 作业评价 @chasenj_zypj ├ 活动公告 @chasenj_hdgg ├ 官方入口 @nj_ooxx ├ …
Channel created
Showing the 3 most recent of 3 posts we hold for @chasenj_zypj. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 6 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“野寻·南京作业评价” (@chasenj_zypj), 5,622 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/chasenj_zypj.
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.