iepl 50元/m 代售4G 通报可以换ip 有兴趣联络 @oneprovide

Channel
Recloud 三鸽窝
@reclouds
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,171subscribers
+61 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001167588197 |
|---|---|
| Type | Channel |
| Username | @reclouds |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/reclouds |
Topic
Technology — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 08:59 | 1,171 | +7 |
| 14 Nov 2026, 02:09 | 1,164 | +4 |
| 9 Nov 2026, 02:47 | 1,160 | +1 |
| 5 Nov 2026, 20:49 | 1,159 | -1 |
| 2 Nov 2026, 13:19 | 1,160 | +2 |
| 30 Oct 2026, 18:58 | 1,158 | +4 |
| 27 Oct 2026, 20:48 | 1,154 | +1 |
| 21 Oct 2026, 21:10 | 1,153 | +1 |
| 18 Oct 2026, 15:18 | 1,152 | -1 |
| 15 Oct 2026, 13:44 | 1,153 | +4 |
| 12 Oct 2026, 19:50 | 1,149 | +3 |
| 5 Oct 2026, 23:56 | 1,146 | +3 |
| 28 Sept 2026, 18:20 | 1,143 | -3 |
| 16 Sept 2026, 06:41 | 1,146 | +4 |
| 12 Sept 2026, 17:20 | 1,142 | +3 |
| 8 Sept 2026, 19:21 | 1,139 | +4 |
| 3 Sept 2026, 05:49 | 1,135 | +2 |
| 31 Aug 2026, 01:05 | 1,133 | +6 |
| 27 Aug 2026, 20:55 | 1,127 | -1 |
| 24 Aug 2026, 12:45 | 1,128 | first reading |
Engagement
20 posts held, back to 20 May 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 20 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
日本联通优化完成 三网高峰期都可以跑了
Photo, posted without a caption
JPBGP 三网优化完成 刚刚掉线是因为优化联通
hkt全线恢复 移动已经优化完成 再次恢复三网优化
急用的的可以先 手动限制小鸡网卡MTU到1400
香港hkt 出现部分ip 空路由 正在联系上游处理
马来西亚母鸡进行电力检修,预计4小时完成。
Signed Oneprovide客服
香港hkt高峰期測速 非常nice 1u/mbps 歡迎體驗! 性價比首選
服務器今天會升級 全部機器可能有重啓的需求
Photo, posted without a caption
香港极限优化 电信 单线程1G 准备回归 会附上白名单ip (特殊优化三网30-40ms) 价格预计在1.x usd/mbps
Showing the 12 most recent of 20 posts we hold for @reclouds. 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.
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 19 November 2026 — this entry's latest reading, not the date you are reading this.
“Recloud 三鸽窝” (@reclouds), 1,171 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/reclouds.
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.