Channel
ASSIGNMENTS GULF TIMES
@AGTjob
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,781subscribers
-148 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001212968631 |
|---|---|
| Type | Channel |
| Username | @AGTjob |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 26 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 26 October 2026 |
| On Telegram | t.me/AGTjob |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 26 Oct 2026, 04:01 | 4,781 | -8 |
| 23 Oct 2026, 08:34 | 4,789 | -17 |
| 20 Oct 2026, 11:46 | 4,806 | -5 |
| 17 Oct 2026, 18:57 | 4,811 | -3 |
| 14 Oct 2026, 11:46 | 4,814 | -17 |
| 10 Oct 2026, 20:36 | 4,831 | -12 |
| 5 Oct 2026, 00:41 | 4,843 | -7 |
| 26 Sept 2026, 00:41 | 4,850 | -29 |
| 15 Sept 2026, 20:58 | 4,879 | -6 |
| 12 Sept 2026, 09:40 | 4,885 | -12 |
| 8 Sept 2026, 06:58 | 4,897 | -22 |
| 3 Sept 2026, 02:37 | 4,919 | -4 |
| 1 Sept 2026, 22:20 | 4,923 | no change |
| 30 Aug 2026, 14:47 | 4,923 | -7 |
| 27 Aug 2026, 18:14 | 4,930 | +1 |
| 27 Aug 2026, 11:45 | 4,929 | 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.
@gulfinterview · 23,699
Telegram ranks this channel #29 of 81 here — alongside 80 others — read 16 September 2026
@cstalaunchpad · 20,713
Telegram ranks this channel #40 of 51 here — alongside 50 others — read 26 September 2026
@oilandgasbyfa · 26,685
Telegram ranks this channel #42 of 67 here — alongside 66 others — read 11 September 2026
@thozhilvaartha_pdf · 47,956
Telegram ranks this channel #54 of 64 here — alongside 63 others — read 27 August 2026
@MCHQatar · 44,045
Telegram ranks this channel #60 of 83 here — alongside 82 others — read 8 September 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 26 October 2026 — this entry's latest reading, not the date you are reading this.
“ASSIGNMENTS GULF TIMES” (@AGTjob), 4,781 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/AGTjob.
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.