Telegram RegisterThe public register of Telegram

Channel

โ•ฏ ๐Ÿ’ โ•ญ

@Maha_1N1

On this record: Growth ยท Engagement ยท Posts ยท Citations ยท Cite this entry

3,595subscribers

-13 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-1001366491616
TypeChannel
Username@Maha_1N1
CreatedBetween 1 April 2018 and 31 July 2021โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Maha_1N1

Growth

3,5953,6083,601.56 August 2026 โ€” 3,608 subscribers6 August 2026 โ€” 3,608 subscribers9 August 2026 โ€” 3,600 subscribers12 August 2026 โ€” 3,595 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -13. 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 3,593โ€“3,610 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:063,595-5
9 Aug 2026, 06:423,600-8
6 Aug 2026, 08:313,608no change
6 Aug 2026, 08:293,608first reading

Engagement

20 posts held, back to 18 January 2026 โ€” the reader has not yet reached the start of this channelโ€™s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegramโ€™s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute โ€” we hold 20 posts for this entry, the most recent from 18 January 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Jan 2026, 21:39 UTCโ‰ˆ1,200 viewsread 7 August 2026

โ€ุฌุนู„ูƒ ู…ุนูŠ ุนูู…ุฑ ูˆ ุฃูƒุซุฑ .

18 Jan 2026, 21:37 UTCโ‰ˆ1,150 viewsread 7 August 2026

โ€ุจู‚ุจู„ู‡ ูˆุงุญุฏู‡ ู…ู†ูƒูŽ ูŠุณุชุญู„ู†ูŠ ุงู„ุฏูุก .

18 Jan 2026, 21:36 UTCโ‰ˆ1,150 viewsread 7 August 2026

โ€ุงุบุงุฑ ู„ุง ุดูุช ุงู„ุจุดุฑ ูŠุทุฑูˆู†ูƒูŽ .

18 Jan 2026, 21:35 UTCโ‰ˆ1,170 viewsread 7 August 2026

โ€ูŠูŽุงุฐูˆู‚ูŠ ูˆ ูŠูŽุงุฐุฑูˆุฉ ุฅุนุฌูŽุงุจูŠ .

18 Jan 2026, 21:34 UTCโ‰ˆ1,180 viewsread 7 August 2026

โ€ู†ุงุฏุฑ ู…ุงู„ู‡ ุจุงู„ู†ุงุณ ุดูƒู„ ูˆ ู…ุซูŠู„ .

18 Jan 2026, 21:33 UTCโ‰ˆ1,190 viewsread 7 August 2026

ู…ุง ูŠุนุฌุจู†ูŠ ุงู„ุนุฌุจ .. ุชุนุฌุจู†ูŠ ุฃู†ุชูŽ .

18 Jan 2026, 21:32 UTCโ‰ˆ1,190 viewsread 7 August 2026

โ€ุญูŽุจูŠุจูŠ ู‡ูˆ ู‚ุฏูŠู…ูŠ ู‡ูˆ ุฌุฏูŠุฏูŠ .

18 Jan 2026, 21:32 UTCโ‰ˆ1,210 viewsread 7 August 2026

โ€ูŠุงู‚ุณูˆุฉ ุงู„ูˆู‚ุช ู…ู† ุฏูˆู†ูƒูŽ .

18 Jan 2026, 21:30 UTCโ‰ˆ1,210 viewsread 7 August 2026

โ€ูŠุง ุฏููˆุฉ ุดุชุงูŠ ูˆ ุฑุถุงูŠ ูˆุฃู…ู†ูŠุฉ ู„ูŠู„ูŠ .

18 Jan 2026, 21:30 UTCโ‰ˆ1,220 viewsread 7 August 2026

โ€ู…ุจุณู…ูƒูŽ ู‚ู…ุฑ ูŠุถูˆูŠ ู„ูŠูŠูŠู‘ุงู„ูŠ ุงู„ุนู…ุฑ .

18 Jan 2026, 21:29 UTCโ‰ˆ1,210 viewsread 7 August 2026

โ€ูŠุง ุฃุญู† ู…ูƒุณุจ ู…ู† ุงู„ุณู†ูŠู† ูƒู„ู‡ุง .

18 Jan 2026, 21:29 UTCโ‰ˆ1,210 viewsread 7 August 2026

โ€ุฃู†ุง ูƒูู„ู‘ูŠ ุฃู†ุช ุŒ ูˆุฃู†ุช ุฃุตุจูŽุญุช ูƒูู„ู‘ูŠ .

Showing the 12 most recent of 20 posts we hold for @Maha_1N1. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked โ‰ˆ was rounded by Telegram before we ever saw it โ€” t.me prints views in full below 1,000 and to three significant figures above, so โ‰ˆ1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank โ€” 1,192,778 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below โ€” republished posts weigh more than named mentions โ€” and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channelโ€™s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page โ€” a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 5 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.

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.

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 August 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œโ•ฏ ๐Ÿ’ โ•ญโ€ (@Maha_1N1), 3,595 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Maha_1N1.

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.