Channel
@yishichangan8
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
28subscribers
+16 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004300735495 |
|---|---|
| Type | Channel |
| Username | @yishichangan8 |
| Created | 26 August 2026 — measured — dated from the channel’s first post |
| First recorded | 28 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/yishichangan8 |
Hacking & security — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 12 Oct 2026, 11:49 | 28 | +1 |
| 15 Sept 2026, 15:39 | 27 | -1 |
| 8 Sept 2026, 02:01 | 28 | +14 |
| 29 Aug 2026, 10:25 | 14 | +2 |
| 28 Aug 2026, 14:45 | 12 | first reading |
5 posts held, back to 26 August 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.
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 27 August 2026. An engagement rate over an empty window would be a number about nothing.
30 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 18 | 60.0% | |
| 💩 | 8 | 26.7% | |
| 👍 | 4 | 13.3% |
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 4 of the 5 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 26 August 2026 to 27 August 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.
山东 浙江 贵州源头出单有多少吃多少市面上出不了我们一样可以 山东 浙江 江苏 河南 陕西 甘肃 云南 内蒙 新疆 天津 安徽 这几个地区房产一口价出所有15U 天津 西藏 新疆 海南 湖南 湖北 四川 广东 福建 山西 河北 重庆 广西 江西 吉林 辽宁 黑龙 青海 北京 这几个地区房产一口价出所有30U 套地区全国名下所有房产 55U 不可排除车位宅基地有多少出多少 一套也是这价 破解名下卡2u 自带银行报 自己出单有量就有价格 联系方式：@yishichanan https://t.me/yishichangan8
❤6💩4
江苏 河南 陕西 甘肃 云南 内蒙 浙江 新疆 贵州 天津 山东这些地区房产 有单速来一口价1️⃣5️⃣🔤
❤4👍4💩1
新增查询内蒙古全省名下房产 只需要名字身份证大头 空不收费 以上两张板子都可选择 一套2️⃣0️⃣🔤 次套1️⃣0️⃣🔤 名下有其他证件我也会顺手送
❤4💩1
浙江房产 稳定正常 提供名字,身份证 不需要大头（假地址关后自带头来） 出名下房产证件 已测试 一个小时内回单 首套1️⃣5️⃣🔤 每套1️⃣2️⃣🔤 @yishichanan
❤4💩2
Channel created
Showing the 5 most recent of 5 posts we hold for @yishichangan8. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“长安” (@yishichangan8), 28 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/yishichangan8.
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.