Channel
Cloud Engineers | AWS | Azure | GCP Devops Notes
@AWS_GCP_Azure
On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
5,684subscribers
+462 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002098768388 |
|---|---|
| Type | Channel |
| Username | @AWS_GCP_Azure |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 21 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 21 October 2026 |
| On Telegram | t.me/AWS_GCP_Azure |
Topic
Education — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Oct 2026, 19:58 | 5,684 | +15 |
| 18 Oct 2026, 06:49 | 5,669 | +9 |
| 15 Oct 2026, 05:48 | 5,660 | +21 |
| 12 Oct 2026, 11:19 | 5,639 | +38 |
| 5 Oct 2026, 14:39 | 5,601 | +49 |
| 28 Sept 2026, 02:58 | 5,552 | +87 |
| 18 Sept 2026, 22:38 | 5,465 | +24 |
| 14 Sept 2026, 11:57 | 5,441 | +16 |
| 10 Sept 2026, 22:38 | 5,425 | +32 |
| 5 Sept 2026, 17:16 | 5,393 | +25 |
| 1 Sept 2026, 17:03 | 5,368 | +3 |
| 31 Aug 2026, 12:40 | 5,365 | no change |
| 29 Aug 2026, 22:58 | 5,365 | +11 |
| 27 Aug 2026, 09:34 | 5,354 | +6 |
| 24 Aug 2026, 14:35 | 5,348 | +17 |
| 21 Aug 2026, 07:35 | 5,331 | +17 |
| 18 Aug 2026, 03:52 | 5,314 | +19 |
| 15 Aug 2026, 02:24 | 5,295 | +15 |
| 12 Aug 2026, 04:27 | 5,280 | +31 |
| 9 Aug 2026, 09:53 | 5,249 | first 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.
Mentions
Named by 6 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
@leadcoding · 35,32610 postsBest AI Tools | ChatGPT | Perplexity | Deepseek | Artificial Intelligence
@AI_Best_Tools · 59,5867 postsFreelancing Tips: Earn Money Online
@freelancing_upwork · 22,3914 postsProgramming Resources | Python | Javascript | Artificial Intelligence Updates | Computer Science Courses | AI Books
@programming_guide · 55,8852 postsCoding Interview Resources
@crackingthecodinginterview · 52,0771 postትኩስ የስራ ማስታወቂያ
@mrtmrt_ch · 2091 post
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@masscoders · 69,230
Telegram ranks this channel #5 of 35 here — alongside 34 others — read 28 August 2026
@SkillsUnlock · 19,862
Telegram ranks this channel #10 of 37 here — alongside 36 others — read 29 September 2026
@datalemur · 20,758
Telegram ranks this channel #11 of 72 here — alongside 71 others — read 26 September 2026
@AIjobz · 20,964
Telegram ranks this channel #15 of 81 here — alongside 80 others — read 25 September 2026
@Interview_Jobs · 22,527
Telegram ranks this channel #15 of 72 here — alongside 71 others — read 20 September 2026
@aichads · 22,914
Telegram ranks this channel #15 of 87 here — alongside 86 others — read 19 September 2026
@generativeai_gpt · 31,036
Telegram ranks this channel #15 of 82 here — alongside 81 others — read 7 September 2026
@Skillsiya · 27,612
Telegram ranks this channel #17 of 48 here — alongside 47 others — read 10 September 2026
@aisigma · 19,850
Telegram ranks this channel #18 of 68 here — alongside 67 others — read 30 September 2026
@aiindi · 59,752
Telegram ranks this channel #20 of 85 here — alongside 84 others — read 23 August 2026
@EthicalHackingToday · 44,039
Telegram ranks this channel #21 of 67 here — alongside 66 others — read 25 September 2026
@udemy_free_courses_with_certi · 70,558
Telegram ranks this channel #22 of 80 here — alongside 79 others — read 20 August 2026
@learncodewithdurgesh · 21,119
Telegram ranks this channel #23 of 62 here — alongside 61 others — read 23 September 2026
@digitalmarketing_trick · 22,364
Telegram ranks this channel #24 of 78 here — alongside 77 others — read 21 September 2026
@Learn_Startup · 33,154
Telegram ranks this channel #27 of 81 here — alongside 80 others — read 4 September 2026
@Curiousprogrammer · 42,113
Telegram ranks this channel #27 of 81 here — alongside 80 others — read 29 August 2026
@Bitcoin_Crypto_Web · 23,085
Telegram ranks this channel #29 of 77 here — alongside 76 others — read 19 September 2026
@datascience69 · 20,459
Telegram ranks this channel #30 of 82 here — alongside 81 others — read 27 September 2026
@nareshit · 59,706
Telegram ranks this channel #30 of 67 here — alongside 66 others — read 22 August 2026
@jobinterviewsprep · 27,651
Telegram ranks this channel #33 of 72 here — alongside 71 others — read 10 September 2026
@FAANGJob · 26,868
Telegram ranks this channel #34 of 76 here — alongside 75 others — read 11 September 2026
@webdevelopmentbook · 32,513
Telegram ranks this channel #36 of 75 here — alongside 74 others — read 5 September 2026
@InterviewBooks · 40,468
Telegram ranks this channel #36 of 78 here — alongside 77 others — read 30 August 2026
@free4unow_backup · 74,517
Telegram ranks this channel #37 of 78 here — alongside 77 others — read 30 September 2026
This channel appears in 67 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 21 October 2026 — this entry's latest reading, not the date you are reading this.
“Cloud Engineers | AWS | Azure | GCP Devops Notes” (@AWS_GCP_Azure), 5,684 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/AWS_GCP_Azure.
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.