
Channel
All Trade ITI Job information
@Govt_ITI_apprentice_job
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,391subscribers
-21 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002201665540 |
|---|---|
| Type | Channel |
| Username | @Govt_ITI_apprentice_job |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/Govt_ITI_apprentice_job |
Topic
Job listings — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 15 Sept 2026, 13:02 | 6,391 | -5 |
| 11 Sept 2026, 18:39 | 6,396 | -19 |
| 7 Sept 2026, 10:18 | 6,415 | -18 |
| 2 Sept 2026, 19:46 | 6,433 | -9 |
| 31 Aug 2026, 04:35 | 6,442 | -8 |
| 28 Aug 2026, 19:31 | 6,450 | no change |
| 28 Aug 2026, 09:24 | 6,450 | -5 |
| 25 Aug 2026, 15:47 | 6,455 | +11 |
| 22 Aug 2026, 10:39 | 6,444 | +12 |
| 19 Aug 2026, 01:52 | 6,432 | +8 |
| 16 Aug 2026, 08:38 | 6,424 | +12 |
| 15 Aug 2026, 11:21 | 6,412 | 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.
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.
@itiexamyt · 39,363
Telegram ranks this channel #11 of 65 here — alongside 64 others — read 30 August 2026
@globaliti · 100,970
Telegram ranks this channel #14 of 70 here — alongside 69 others — read 15 August 2026
@Majhi_Naukri_Update · 29,976
Telegram ranks this channel #25 of 55 here — alongside 54 others — read 7 September 2026
@Ganpati_Bappa_Videos · 23,456
Telegram ranks this channel #51 of 56 here — alongside 55 others — read 18 September 2026
@Law_Judiciary_CLAT_PDF_PW_Wallah · 53,977
Telegram ranks this channel #62 of 62 here — alongside 61 others — read 23 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“All Trade ITI Job information” (@Govt_ITI_apprentice_job), 6,391 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Govt_ITI_apprentice_job.
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.