Telegram RegisterThe public register of Telegram
Telegram profile photo for 垃圾站

Channel

垃圾站

@lajizhan1

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001562731425
TypeChannel
Username@lajizhan1
CreatedBetween 1 August 2021 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live16 September 2026
Measurements held2
On Telegramt.me/lajizhan1

Growth

27 August 2026 — 2 subscribers13 August 2026 — 2 subscribers7 August 202613 August 2026
2 measurements spanning 7 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 18:452no change
7 Aug 2026, 01:342first reading

Engagement

20 posts held, back to 31 October 2021the 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 20 posts for this entry, the most recent from 30 December 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Links
13

Lifetime counters from Telegram’s own channel header, read 13 August 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.

Recent posts

30 Dec 2021, 03:33 UTC22 viewsread 13 August 2026
Forwarded from @fdd_JSBPhoto

机器人/bean 1用不了 然后机器人日志显示没有prettytable 解决方案 ssh进入容器 pip3 install PrettyTable 或者 docker exec -it qinglong bash -c "pip3 install PrettyTable"(qinglong改成你的青龙容器的名字) 水群的时候DDO帮人解决的 我只分享

26 Dec 2021, 00:18 UTC22 viewsread 13 August 2026
Forwarded from @fdd_JSB

青龙基本指令 1. ql update # 更新并重启青龙 2. ql extra # 运行自定义脚本 3. ql raw <fileurl> # 更新单个脚本文件 4. ql repo 4. ql repo <库地址> <拉什么> <不拉什么> <依赖> <分支> # 更新单个仓库的脚本 5. ql rmlog <days> # 删除旧日志 6. ql bot

12 Dec 2021, 05:19 UTC15 viewsread 13 August 2026

强制更新 git fetch --all git reset --hard origin/main git pull

30 Nov 2021, 12:53 UTC16 viewsread 13 August 2026
Forwarded from @fdd_JSB

禁用重复任务脚本 ql raw https://raw.githubusercontent.com/Oreomeow/VIP/main/Scripts/py/disable.py #### 禁用重复任务脚本 #环境变量 #1️⃣RES_SUB #2️⃣RES_ONLY #说明 #1️⃣需保留的脚本前缀列表(不管是否重复),用 & 分割,默认保留 Aaron-lv_sync #2️⃣保留后是否禁用重复的带其他前缀脚本,默认禁用 #示例 #1️⃣Aaron-lv_sync&smiek2121_scripts #2️⃣true 或 false export RES_SUB="Aaron-lv_sync&smiek2121_scripts& /ql/scripts/jd_zjd.py" export RES_ONLY="true" BY:https://t.me/Oreomsg 不敢用的就去备份/ql/db/crontab.db

30 Nov 2021, 12:53 UTC13 viewsread 13 August 2026
Forwarded from @fdd_JSB

因为说了“用 & 分割” 所以两个 &之间是一个整体 所以export RES_SUB="Aaron-lv_sync&smiek2121_scripts& /ql/scripts/jd_zjd.py"有三个变量 分别是 Aaron-lv_sync smiek2121_scripts /ql/scripts/jd_zjd.py 所以变量的第二种写法是 /ql/scripts/jd_zjd.py 不会有人看不懂吧 不会吧 不会吧

27 Nov 2021, 23:21 UTC11 viewsread 13 August 2026
Forwarded from @kejiwanjiarss

【宝塔7.6.0专业版(企业版)破解教程】 玩家:阿雯 查看:https://www.kejiwanjia.com/jiaocheng/45316.html

27 Nov 2021, 04:02 UTC10 viewsread 13 August 2026
Forwarded from @sheeplostFile

过期京豆兑换为喜豆,每次最大限制1000豆 脚本默认不兑换豆子,如需兑换请设置环境变量exjxbeans为true

26 Nov 2021, 01:15 UTC11 viewsread 13 August 2026
Forwarded from @fdd_JSB

分享一个有人维护的extra.sh(我自用的就是在这个基础上自己改的) 作用:拉裤 安装和修复依赖(code的功能) 启动更新NINJA BY:https://t.me/Oreomsg 需要的自取(别问我咋用 我只分享) https://raw.githubusercontent.com/Oreomeow/VIP/main/Tasks/qlrepo/extra.sh

26 Nov 2021, 01:15 UTC9 viewsread 13 August 2026
Forwarded from @fdd_JSB

https://www.zhihu.com/question/383046120/answer/1772928641 建议把这个塞到你的垃圾桶!可爱的猫猫!

17 Nov 2021, 06:10 UTC10 viewsread 13 August 2026
Forwarded from @fdd_JSBFile

评论助手 老板的 需要的自取

17 Nov 2021, 06:10 UTC10 viewsread 13 August 2026
Forwarded from @fdd_JSBFile

上面的是脚本依赖下载 for Curtinlv 仓库 配合最新的评论助手 https://raw.githubusercontent.com/qiu-lzsnmb/jd_lzsnmb/jd/Evaluation.py 需要的自取

17 Nov 2021, 03:27 UTC10 viewsread 13 August 2026
Forwarded from @carrotchoublog

【Windows 10 Enterprise LTSC 2021】 64位: C117C5DDBC51F315C739F9321D4907FA50090BA7B48E7E9A2D173D49EF2F73A3 https://msproduct.download.prss.microsoft.com/pr/SW_DVD9_WIN_ENT_LTSC_2021_64BIT_ChnSimp_MLF_X22-84402.ISO?t=6bd43df0-c878-4264-a125-dbe5a2def536&e=1637125338&h=35502ea598d019ad8e8e5e96ca76445ea5e7a434bc232b7e192d5d79d4de6b77 32位: 9F855FCC4CB44C119F9CE73DABE569FCB7F4F4D85F922206BF2E108116A34F25 https://mspro

Showing the 12 most recent of 20 posts we hold for @lajizhan1. 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.

Forward network

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.

Mentions

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.

Cite this entry

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“垃圾站” (@lajizhan1), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/lajizhan1.

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.