Telegram RegisterThe public register of Telegram
Telegram profile photo for مشارق

Channel

مشارق

@maasharegh

On this record: Topic · Growth · Engagement · Cite this entry

3,034subscribers

+217 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001284592829
TypeChannel
Username@maasharegh
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 September 2026
Last confirmed live5 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/maasharegh

Topic

Personal blog — 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 46% 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

2,8173,0342,925.57 August 2026 — 2,817 subscribers9 August 2026 — 2,819 subscribers12 August 2026 — 2,818 subscribers15 August 2026 — 2,825 subscribers18 August 2026 — 2,881 subscribers20 August 2026 — 2,883 subscribers24 August 2026 — 2,887 subscribers27 August 2026 — 2,893 subscribers30 August 2026 — 2,900 subscribers2 September 2026 — 2,901 subscribers7 September 2026 — 2,909 subscribers11 September 2026 — 2,914 subscribers12 September 2026 — 2,914 subscribers15 September 2026 — 2,924 subscribers30 September 2026 — 2,946 subscribers7 October 2026 — 2,968 subscribers15 October 2026 — 2,970 subscribers19 October 2026 — 2,980 subscribers22 October 2026 — 2,986 subscribers24 October 2026 — 2,993 subscribers27 October 2026 — 2,998 subscribers30 October 2026 — 2,999 subscribers2 November 2026 — 3,019 subscribers5 November 2026 — 3,034 subscribers7 August 20265 November 2026
24 measurements spanning 91 days, net +217. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,784–3,067 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
5 Nov 2026, 19:573,034+15
2 Nov 2026, 22:363,019+20
30 Oct 2026, 22:362,999+1
27 Oct 2026, 23:192,998+5
24 Oct 2026, 23:312,993+7
22 Oct 2026, 01:212,986+6
19 Oct 2026, 02:182,980+10
15 Oct 2026, 21:272,970+2
7 Oct 2026, 05:362,968+22
30 Sept 2026, 02:212,946+22
15 Sept 2026, 19:212,924+10
12 Sept 2026, 00:552,914no change
11 Sept 2026, 22:372,914+5
7 Sept 2026, 08:562,909+8
2 Sept 2026, 11:042,901+1
30 Aug 2026, 09:442,900+7
27 Aug 2026, 18:082,893+6
24 Aug 2026, 09:422,887+4
20 Aug 2026, 20:342,883+2
18 Aug 2026, 06:422,881first 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.

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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“مشارق” (@maasharegh), 3,034 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/maasharegh.

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.