Telegram RegisterThe public register of Telegram
Telegram profile photo for مشکی |meshki

Channel

مشکی |meshki

@imeshki

On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

8,970subscribers

-348 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-1001481370745
TypeChannel
Username@imeshki
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/imeshki

Growth

8,9709,3189,1446 August 2026 — 9,318 subscribers7 August 2026 — 9,318 subscribers7 August 2026 — 9,314 subscribers10 August 2026 — 9,281 subscribers14 August 2026 — 9,225 subscribers17 August 2026 — 9,186 subscribers20 August 2026 — 9,157 subscribers24 August 2026 — 9,121 subscribers27 August 2026 — 9,084 subscribers30 August 2026 — 9,046 subscribers2 September 2026 — 9,011 subscribers7 September 2026 — 8,970 subscribers6 August 20267 September 2026
12 measurements spanning 32 days, net -348. 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 8,918–9,370 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 14:018,970-41
2 Sept 2026, 12:169,011-35
30 Aug 2026, 16:579,046-38
27 Aug 2026, 08:259,084-37
24 Aug 2026, 10:489,121-36
20 Aug 2026, 14:429,157-29
17 Aug 2026, 14:089,186-39
14 Aug 2026, 07:259,225-56
10 Aug 2026, 16:419,281-33
7 Aug 2026, 09:039,314-4
7 Aug 2026, 00:009,318no change
6 Aug 2026, 23:599,318first reading

Engagement

20 posts held, back to 30 September 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 31 pages of 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 30 January 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 May 2025, 10:29 UTC≈19,300 viewsread 28 August 2026

به درد کسی خوردی به دردت نخورد به دردش بخوری به درد نخوری.

7 May 2025, 10:47 UTC≈19,900 viewsread 28 August 2026

یکی‌از باگای دنیا اینه که با هرکی حال میکنی ازت دوره

3 May 2025, 11:27 UTC≈20,500 viewsread 28 August 2026

جهنم خالیه ؛ شیاطین واقعی اینجان.

27 Mar 2025, 10:33 UTC≈26,100 viewsread 28 August 2026

من پر از تاریکی ام ولی برای تو همیشه پر نور :)

26 Mar 2025, 14:52 UTC≈25,100 viewsread 28 August 2026

من روح مرده ام بی تو ، تو بی من چگونه ای؟!

26 Mar 2025, 14:51 UTC≈24,400 viewsread 28 August 2026

من خیلی دلتنگتم؛ ولی از این به بعد دیگه هروقت که بیای دیره!

2 Jan 2025, 08:51 UTC≈51,400 viewsread 28 August 2026

منو غرقم کن تو اون مشکی موهات .. 🖤

1 Dec 2024, 19:47 UTC≈55,500 viewsread 28 August 2026

تویی که ادعات میشد ، از همه ناکس تری ؛

Showing the 12 most recent of 20 posts we hold for @imeshki. 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.

Mentions

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

Named by

Channels on the register whose posts name this channel's handle.

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.

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.

"𝐐𝐨𝐟𝐥𝐞 𝐀𝐡𝐚𝐧𝐠" آهنگای قفلی
@QofleAhang · 63,027
Telegram ranks this channel #59 of 85 here — alongside 84 others — read 21 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“مشکی |meshki” (@imeshki), 8,970 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/imeshki.

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.