Telegram RegisterThe public register of Telegram
Telegram profile photo for Cloud Releases

Channel

Cloud Releases

@newcloudrls

Has discussion group

On this record: Topic · Growth · Engagement · Cite this entry

3,120subscribers

-162 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-1002126148544
TypeChannel
Username@newcloudrls
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live5 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/newcloudrls

Topic

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

3,1203,2823,2017 August 2026 — 3,282 subscribers8 August 2026 — 3,279 subscribers11 August 2026 — 3,266 subscribers15 August 2026 — 3,260 subscribers18 August 2026 — 3,254 subscribers20 August 2026 — 3,246 subscribers24 August 2026 — 3,243 subscribers27 August 2026 — 3,234 subscribers30 August 2026 — 3,217 subscribers1 September 2026 — 3,211 subscribers6 September 2026 — 3,201 subscribers10 September 2026 — 3,201 subscribers10 September 2026 — 3,189 subscribers14 September 2026 — 3,179 subscribers18 September 2026 — 3,162 subscribers27 September 2026 — 3,137 subscribers5 October 2026 — 3,120 subscribers7 August 20265 October 2026
17 measurements spanning 59 days, net -162. 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 3,096–3,306 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 08:403,120-17
27 Sept 2026, 12:363,137-25
18 Sept 2026, 13:363,162-17
14 Sept 2026, 02:153,179-10
10 Sept 2026, 18:573,189-12
10 Sept 2026, 00:163,201no change
6 Sept 2026, 01:393,201-10
1 Sept 2026, 23:193,211-6
30 Aug 2026, 06:243,217-17
27 Aug 2026, 10:043,234-9
24 Aug 2026, 13:153,243-3
20 Aug 2026, 19:123,246-8
18 Aug 2026, 03:323,254-6
15 Aug 2026, 04:143,260-6
11 Aug 2026, 10:133,266-13
8 Aug 2026, 06:313,279-3
7 Aug 2026, 18:113,282first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 5 October 2026 — this entry's latest reading, not the date you are reading this.

“Cloud Releases” (@newcloudrls), 3,120 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/newcloudrls.

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.