Channel
@chasecs_sjda
On this record: Growth · Engagement · Posts · Citations · Cite this entry
5,050subscribers
+5 since we began measuring on 25 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002310639764 |
|---|---|
| Type | Channel |
| Username | @chasecs_sjda |
| Created | 21 December 2024 — measured — dated from the channel’s first post |
| First recorded | 25 September 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/chasecs_sjda |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 23:57 | 5,050 | +5 |
| 25 Sept 2026, 19:22 | 5,045 | no change |
| 25 Sept 2026, 18:47 | 5,045 | first reading |
5 posts held, back to 21 December 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 30 August 2026. An engagement rate over an empty window would be a number about nothing.
😀 野寻 · 长沙修车导航 😀 ~岳麓风来书意远，橘洲灯火照星城~ ~人间最好相逢处，恰是长沙夜未停~ 新手中心: 😀【野寻 · 长沙使用手册】 😀 野寻大讲堂 └ 作业模版 └ 积分商城 └ 会员制度 └ 工兵模版 └ 查找老师 └ 野寻招募令 😀 长沙榜单导航 └ 按价格 └ 按地区 └ 按服务 └ 按标签 😀 其它资源 └ 野寻· 长沙外围 └ 野寻· 长沙包养 └ 野寻· 长沙商家 ⚡【野寻· 长沙】榜单结构 ├ 打卡通告群 @chasecs_tgq ├ 学生交流群 @chasecs_jlq ├ 小喇叭 @chasecs_xlb ├ 榜单导航 @chasecs_bddh ├ 修车档案 @chasecs_lsda ├ 作业评价 @chasecs_zypj ├ 活动公告 @chasecs_hdgg ├ 官方入口 @cs_o…
Channel photo updated
Channel name was changed to «野寻·长沙商家档案»
Channel name was changed to «野寻 长沙商家档案»
Channel created
Showing the 5 most recent of 5 posts we hold for @chasecs_sjda. 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 2 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“野寻·长沙商家档案” (@chasecs_sjda), 5,050 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/chasecs_sjda.
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.