Channel
@lxk0301_scripts
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
6,791subscribers
-78 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001169507011 |
|---|---|
| Type | Channel |
| Username | @lxk0301_scripts |
| Created | 8 July 2020 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/lxk0301_scripts |
Ecommerce storefront — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 16 Sept 2026, 05:40 | 6,791 | -11 |
| 12 Sept 2026, 10:19 | 6,802 | -13 |
| 8 Sept 2026, 04:21 | 6,815 | -11 |
| 2 Sept 2026, 19:26 | 6,826 | -5 |
| 30 Aug 2026, 20:43 | 6,831 | -5 |
| 28 Aug 2026, 04:34 | 6,836 | -2 |
| 24 Aug 2026, 19:54 | 6,838 | -9 |
| 21 Aug 2026, 07:32 | 6,847 | -5 |
| 18 Aug 2026, 09:52 | 6,852 | -5 |
| 15 Aug 2026, 00:36 | 6,857 | -8 |
| 12 Aug 2026, 02:32 | 6,865 | -3 |
| 9 Aug 2026, 04:12 | 6,868 | -1 |
| 8 Aug 2026, 15:30 | 6,869 | first reading |
4 posts held, back to 8 July 2020 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 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 4 posts for this entry, the most recent from 7 January 2025. An engagement rate over an empty window would be a number about nothing.
京东 PLUS会员权益再升级 1， 兑生活服务包 每个年卡周期送12积分，积分可以兑换家政保洁（全年1次），洗衣洗鞋（全年2次），标准洗车（全年1次），免费寄快递（全年4次），免费体检等权益！ 2， 自营秒送免邮 京东APP首页顶部切换至“秒送”选择自营店铺（如七鲜超市、京东大药房等）下单可享包邮，跟京东自营商品一样，无限免邮！ 3， 半年只换不修 京东自营电器（包括手机通讯、数码、电脑办公、家用电器、灯饰照明等）带有“PLUS 180天只换不修”服务标识的，签收之后180天内从“免费维修”升级成“只换不修”！ 权益：https://u.jd.com/QrIvPkB
🎉新年快乐🎉
京东车🚗 https://p.lxk0301.top/
Signed 030
Channel created
Showing the 4 most recent of 4 posts we hold for @lxk0301_scripts. 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Scripts” (@lxk0301_scripts), 6,791 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/lxk0301_scripts.
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.