Channel
@Config_Cloud1
On this record: Topic · Growth · Engagement · Posts · Cite this entry
115subscribers
-27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003963893064 |
|---|---|
| Type | Channel |
| Username | @Config_Cloud1 |
| Created | Between 1 April 2026 and 7 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/Config_Cloud1 |
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 26 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 22:42 | 115 | -1 |
| 26 Sept 2026, 10:01 | 116 | -4 |
| 13 Sept 2026, 21:17 | 120 | -4 |
| 6 Sept 2026, 01:20 | 124 | -3 |
| 29 Aug 2026, 13:16 | 127 | -6 |
| 22 Aug 2026, 11:57 | 133 | -3 |
| 15 Aug 2026, 03:13 | 136 | -4 |
| 8 Aug 2026, 22:31 | 140 | no change |
| 8 Aug 2026, 10:36 | 140 | -2 |
| 7 Aug 2026, 19:22 | 142 | first reading |
20 posts held, back to 7 June 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 9 June 2026. An engagement rate over an empty window would be a number about nothing.
vmess://eyJhZGQiOiIyMTMuMTU2LjE0MS41MiIsImFpZCI6IjAiLCJhbHBuIjoiIiwiZnAiOiIiLCJob3N0IjoiIiwiaWQiOiIwNDYyMWJhZS1hYjM2LTExZWMtYjkwOS0wMjQyYWMxMjAwMDIiLCJpbnNlY3VyZSI6IjAiLCJuZXQiOiJ0Y3AiLCJwYXRoIjoiLyIsInBvcnQiOiIyMjMyNCIsInBzIjoiaHR0cHM6Ly90Lm1lL0NvbmZpZ19DbG91ZDEiLCJzY3kiOiJhdXRvIiwic25pIjoiIiwidGxzIjoiIiwidHlwZSI6Im5vbmUiLCJ2IjoiMiJ9 @Config_Cloud1
vless://[email protected]:993?security=reality&encryption=none&pbk=UvQ2HZFkQXrBiaprbcmks-aFo1dvnfPlHXcUKcl-i04&headerType=none&fp=chrome&type=tcp&flow=xtls-rprx-vision&sni=dl.google.com#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
vless://[email protected]:80?path=%2F&security=none&encryption=none&host=max-gb1.global.ssl.fastly.net&type=ws#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
vless://[email protected]:443?security=reality&encryption=none&pbk=D-7qX4fqUFKDS2dQWFgGT4fXJnABnpM6IkU8SDHLMC0&headerType=none&fp=chrome&type=tcp&flow=xtls-rprx-vision&sni=saorg.ir&sid=6ba85179e30d4fc2#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
vmess://eyJhZGQiOiIxNjUuMTQwLjIxNi4xNDEiLCJhaWQiOiIwIiwiYWxwbiI6IiIsImZwIjoiIiwiaG9zdCI6IiIsImlkIjoiZTdkNzJhOGQtMjZmMi00YjU0LWIzNjYtMGM0M2UwYmNiYTdkIiwiaW5zZWN1cmUiOiIwIiwibmV0IjoidGNwIiwicGF0aCI6IiIsInBvcnQiOiI0NDMiLCJwcyI6Imh0dHBzOi8vdC5tZS9Db25maWdfQ2xvdWQxIiwic2N5IjoiYXV0byIsInNuaSI6IiIsInRscyI6IiIsInR5cGUiOiJub25lIiwidiI6IjIifQ== @Config_Cloud1
vless://[email protected]:443?security=none&encryption=none&headerType=none&type=tcp#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
vless://[email protected]:443?security=reality&encryption=none&pbk=enBIOTqlP6CHTvic3CLgpUd_AcJAAbAQIa-oFIk4dVU&headerType=none&fp=chrome&spx=%2F&type=tcp&sni=yahoo.com&sid=302e#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
vless://[email protected]:19105?security=reality&encryption=none&pbk=IS6TNMONlIVvcUBvo2RXQvx2Jopcv4wzPyZhxPhWqT8&headerType=none&fp=chrome&type=tcp&flow=xtls-rprx-vision&sni=www.microsoft.com&sid=e6#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
👤 @Config_Cloud1
vless://[email protected]:31413?security=reality&encryption=none&pbk=nMlxwhP34_5wFPscbso_hOfRDmsj9DonMpDSXUrnJR8&headerType=none&fp=chrome&spx=%2F&type=tcp&flow=xtls-rprx-vision&sni=yahoo.com&sid=ead3d6f82a9d#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
vmess://eyJhZGQiOiI4Mi4xOTguMjQ2LjIzMyIsImFpZCI6IjAiLCJhbHBuIjoiIiwiZnAiOiIiLCJob3N0IjoianAyLThzYi42MTIxOTk5LmRwZG5zLm9yZyIsImlkIjoiZDEzZmMyZjUtM2UwNS00Nzk1LTgxZWItNDQxNDNhMDllNTUyIiwiaW5zZWN1cmUiOiIwIiwibmV0IjoidGNwIiwicGF0aCI6Ii8iLCJwb3J0IjoiMTgwIiwicHMiOiJodHRwczovL3QubWUvQ29uZmlnX0Nsb3VkMSIsInNjeSI6ImF1dG8iLCJzbmkiOiIiLCJ0bHMiOiIiLCJ0eXBlIjoibm9uZSIsInYiOiIyIn0= @Config_Cloud1
vless://[email protected]:443?security=reality&encryption=none&pbk=QVkd5uoSbUA7rHVLtIoJB4iRp4l0zuw0H9qzQBh3lHs&headerType=none&fp=edge&type=tcp&flow=xtls-rprx-vision&sni=jp.s3-cloud.org&sid=7a3f9e2b1c8d4f6a#https%3A%2F%2Ft.me%2FConfig_Cloud1 @Config_Cloud1
Showing the 12 most recent of 20 posts we hold for @Config_Cloud1. 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“Config Cloud” (@Config_Cloud1), 115 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/Config_Cloud1.
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.