
Channel
My Major - محفظة
@my_major
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,012subscribers
-1 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001915298767 |
|---|---|
| Type | Channel |
| Username | @my_major |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/my_major |
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 15 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 16:21 | 3,012 | -4 |
| 11 Sept 2026, 13:48 | 3,016 | no change |
| 8 Sept 2026, 12:37 | 3,016 | -2 |
| 2 Sept 2026, 23:46 | 3,018 | +4 |
| 30 Aug 2026, 13:18 | 3,014 | -1 |
| 20 Aug 2026, 12:53 | 3,015 | +4 |
| 17 Aug 2026, 21:16 | 3,011 | -1 |
| 14 Aug 2026, 19:04 | 3,012 | -1 |
| 14 Aug 2026, 08:04 | 3,013 | 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.
@drtahaalbalasmeh · 43,371
Telegram ranks this channel #15 of 74 here — alongside 73 others — read 28 August 2026
@drillingmanual2 · 30,367
Telegram ranks this channel #65 of 86 here — alongside 85 others — read 13 September 2026
@iraqi_HR · 35,705
Telegram ranks this channel #67 of 93 here — alongside 92 others — read 2 September 2026
@iraq_careers · 29,885
Telegram ranks this channel #71 of 94 here — alongside 93 others — read 8 September 2026
@basrahvacancies · 86,613
Telegram ranks this channel #71 of 87 here — alongside 86 others — read 18 August 2026
@BasrajobsCh · 36,695
Telegram ranks this channel #74 of 89 here — alongside 88 others — read 1 September 2026
@t3iniq · 118,448
Telegram ranks this channel #92 of 97 here — alongside 96 others — read 14 August 2026
This channel appears in 7 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“My Major - محفظة” (@my_major), 3,012 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/my_major.
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.