粽叶迎风香,岁岁皆安康,端午喜乐常伴 。
😁23👍13❤5

Channel
@xsijishe
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
33,722subscribers
+2,331 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001888098202 |
|---|---|
| Type | Channel |
| Username | @xsijishe |
| Description | 防失联频道,请关注防迷路~ |
| Created | 12 May 2023 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/xsijishe |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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, 11:20 | 33,722 | +105 |
| 16 Sept 2026, 03:18 | 33,617 | +81 |
| 14 Sept 2026, 12:00 | 33,536 | +72 |
| 12 Sept 2026, 21:00 | 33,464 | +96 |
| 11 Sept 2026, 01:37 | 33,368 | +172 |
| 8 Sept 2026, 06:00 | 33,196 | +184 |
| 4 Sept 2026, 22:40 | 33,012 | +74 |
| 3 Sept 2026, 09:28 | 32,938 | +29 |
| 2 Sept 2026, 05:13 | 32,909 | +26 |
| 1 Sept 2026, 05:18 | 32,883 | +35 |
| 31 Aug 2026, 06:03 | 32,848 | +48 |
| 30 Aug 2026, 06:33 | 32,800 | +48 |
| 29 Aug 2026, 03:01 | 32,752 | +33 |
| 28 Aug 2026, 01:54 | 32,719 | +62 |
| 27 Aug 2026, 03:53 | 32,657 | +40 |
| 26 Aug 2026, 01:33 | 32,617 | +55 |
| 25 Aug 2026, 04:25 | 32,562 | +54 |
| 24 Aug 2026, 01:56 | 32,508 | +130 |
| 22 Aug 2026, 11:57 | 32,378 | +82 |
| 21 Aug 2026, 02:44 | 32,296 | first reading |
10 posts held, back to 12 May 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 70 pages 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 10 posts for this entry, the most recent from 19 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 20 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
566 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 39.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 226 | 39.9% | |
| 👍 | 206 | 36.4% | |
| 👏 | 60 | 10.6% | |
| 😁 | 32 | 5.65% | |
| 🍾 | 16 | 2.83% | |
| 👀 | 6 | 1.06% | |
| 😱 | 5 | 0.883% | |
| 🥰 | 5 | 0.883% | |
| 👎 | 4 | 0.707% | |
| 🔥 | 4 | 0.707% | |
| ❤🔥 | 2 | 0.353% |
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 9 of the 10 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 566 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 12 May 2023 to 19 June 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.
粽叶迎风香,岁岁皆安康,端午喜乐常伴 。
😁23👍13❤5
愿你劳有所获,生活一帆风顺,事业一步登天,假期快乐无忧。
👏52❤14👍8❤🔥2
关于社区大多数常见问题,请参考社区帮助中心 👉:https://xsijishe.net/plugin.php?id=keke_help
❤13👍3
新年快乐!!
👍89🍾16❤13👏1
https://t.me/+DeO6EHsP3Tc2YTRk 新群已建。
❤13👍12😁4👏3
目前TG盗号严重,请各位切勿轻易相信所谓的验证机器人,尤其是中文信息的。
❤31👀5👍1
吾爱映梓制作的迅雷12.1.9.2870【11.2.2.1716】精简绿色融合版是在11.2.2.1716版本的基础上制作的,实际版本号显示为12.1.9.2870,不是真正意义的迅雷12.1.9.2870精简绿色版,本实质上还是11.2.2.1716精简绿色复活版,功能上与11.2.2.1716精简绿色版基本一致。 👉可自行添加 XMP(边下边播功能组件): https://www.lanzouw.com/ij6COj0l3pi 👉视频添加解码器codecs组件: https://www.lanzouw.com/idlQL2ilecgj
❤37👍27
转:今天开始有类似的盗号机器人,给第三方机器人做了超链接,外面看起来显示的是telegram官方,实际是盗号机器人,点进去之后会通过你的账号给你所加的群进行群发,以此扩散,请各位千万不要点击!!
👍23❤17😱5👀1
Signed 風華絕代™
司机社 最新地址 请选择最新地址 大陆地址1 https://dlsjs.com 大陆地址2 https://dlsjs.net 大陆地址3 https://sjs96.com 永久地址 https://xsijishe.net 永久地址发布站 地址: https://47447.net 国产浏览器(如 UC、360、QQ、百度) 不定期可能会屏蔽网站,建议使用谷歌浏览器或者Edge观看 如果不想更换浏览器请将浏览器的安全云拦截和广告屏蔽服务关闭即可 若你是 iPhone、Mac 的用户,建议使用系统自带的 Safari 浏览器
❤83👍30🥰5😁5👎4👏4🔥4
Channel created
Showing the 10 most recent of 10 posts we hold for @xsijishe. 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.
@xsijishe edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
“司机社官方频道” (@xsijishe), 33,722 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xsijishe.
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.