16 Apr 2025, 01:07 UTC2 viewsread 15 August 2026
test
Channel
跨越树收发室
@crosstree
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+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 | -1001813042340 |
|---|---|
| Type | Channel |
| Username | @crosstree |
| Created | 26 November 2022 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/crosstree |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 10:46 | 1 | no change |
| 7 Aug 2026, 09:54 | 1 | first reading |
Engagement
7 posts held, back to 26 November 2022 — 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 pageof 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 7 posts for this entry, the most recent from 16 April 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Videos
- 1
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 15 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.
- Video runtime
- 8s
- Average length
- 8s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
16 Apr 2025, 01:07 UTC2 viewsread 15 August 2026
dsafd
23 Mar 2024, 00:48 UTC10 viewsread 15 August 2026
https://github.com/IceWhaleTech/CasaOS
13 Oct 2023, 16:10 UTC7 viewsread 15 August 2026
Forwarded from @feiyangofficalchannelPhoto
今天新开了一台VPS，4H8G NVME，直接用 1panel 作为主力运维面板，体验秒杀宝塔，面板绑定域名+证书后，不仅方便还可以屏蔽端口访问， 1panel 以Go+Vue组合，在整体体验上我觉得优于宝塔的Python+非前端框架组合，自带docker和docker-compose，所有商店应用都是基于类似docker-image封装，不是宿主机直接安装运行，所以部署起来非常的快，基本上安装一个nginx和mysql+Redis也就两三分钟全部就好了，整体界面体验非常不错，提供大量现代化部署服务！
23 Aug 2023, 04:24 UTC12 viewsread 15 August 2026
测试2
26 Nov 2022, 09:26 UTC13 viewsread 15 August 2026
测试
26 Nov 2022, 09:22 UTCviews —
Channel created
Showing the 7 most recent of 7 posts we hold for @crosstree. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“跨越树收发室” (@crosstree), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/crosstree.
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.