Telegram RegisterThe public register of Telegram
Telegram profile photo for نَفَـــسِ عِشـــق

Channel

نَفَـــسِ عِشـــق

@nafasse_eshgh

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

5,204subscribers

-25 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-1001149821311
TypeChannel
Username@nafasse_eshgh
CreatedBetween 1 October 2017 and 31 January 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/nafasse_eshgh

Growth

5,2045,2295,216.56 August 2026 — 5,229 subscribers6 August 2026 — 5,229 subscribers7 August 2026 — 5,228 subscribers9 August 2026 — 5,220 subscribers13 August 2026 — 5,216 subscribers16 August 2026 — 5,218 subscribers19 August 2026 — 5,209 subscribers22 August 2026 — 5,207 subscribers25 August 2026 — 5,204 subscribers6 August 202625 August 2026
9 measurements spanning 19 days, net -25. 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 5,200–5,233 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 07:025,204-3
22 Aug 2026, 13:355,207-2
19 Aug 2026, 12:035,209-9
16 Aug 2026, 15:535,218+2
13 Aug 2026, 04:365,216-4
9 Aug 2026, 20:115,220-8
7 Aug 2026, 00:375,228-1
6 Aug 2026, 04:305,229no change
6 Aug 2026, 04:245,229first reading

Engagement

20 posts held, back to 2 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.40%
avg views ÷ 5,204 subscribers
Avg views / post
385
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 July 2026
Posts held20 (2 June 202629 July 2026)
Views total385
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:35 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

18 Jul 2026, 08:13 UTC664 viewsread 12 August 2026
Photo

چه زیباست که پس از آرزویی، پلک‌ها را بگشاییم ... در بامدادی و ببینیم که در تاریکیِ شبِ پیش، برای شادی ما جهانی تازه ساخته‌اند. ‌ #اسکار_وایلد

17 Jul 2026, 20:24 UTC559 viewsread 12 August 2026
Photo

یا به کنار من درآ 💖 تا بروم به خواب خوش یا به خیال خود بگو تا رود از مقابلم. #سروش_اصفهانی

17 Jul 2026, 17:19 UTC510 viewsread 12 August 2026

دوباره می‌سازمت وطـن❤️ اگرچه با خشت جان خویش ستون به سقف تو می زنم اگر چه با استخوان خویش. #سیمین_بهبهانی

15 Jul 2026, 08:23 UTC555 viewsread 12 August 2026
Photo

صبـح که از خواب بیدار می‌شوی به خودت یادآوری کن: امروز با کسانی روبه‌رو می‌شوم که فضول، ناسپاس، خودخواه و پرمدعا هستند اما من نباید بگذارم هیچ‌کدامشان مهربانی من را کم‌رنگ کنند. #مارکوس_اورلیوس

14 Jul 2026, 04:54 UTC577 viewsread 12 August 2026
Photo

تمام زندگیم بوی جنگ میده تـو اما شبیه صلحی😍 تمام چیزی که ... یه جنگ‌زده میخواد، صلحه. #کیمیا_رجبی

13 Jul 2026, 18:25 UTC514 viewsread 12 August 2026
Photo

در هیاهوی شــب عشـق✨ کسـی یـاد تــو نیسـت، دلِ بیچـاره ...💔 به امید کـه اینجا ماندی؟! #محمد_شیخی

11 Jul 2026, 07:28 UTC627 viewsread 12 August 2026
Photo

سـلام بر آن‌ها که در پنهان خویش بهاری برای شکفتن دارند. #سلمان_هراتی

9 Jul 2026, 19:57 UTC647 viewsread 12 August 2026
Photo

گویی باز هم پیرزنی روی دار قالیچه ی شـب✨ نقش دردی از دوری تـو روی چله های ذهن من می‌بافد. #حسام_عزیزی

8 Jul 2026, 08:08 UTC670 viewsread 12 August 2026
Photo

دوستت خواهم داشت♥️ در سکوت در کلام در صلح در جنگ. #بابک_زمانی

26 Jun 2026, 12:32 UTC909 viewsread 12 August 2026
Photo

کسی باور نمی‌کند لبخندش می‌توانست پلی باشد که جمعـه را به همه‌ی روزهای هفته پیوند بزند. #احمدرضا_احمدی

26 Jun 2026, 10:01 UTC787 viewsread 12 August 2026
Photo

آمدی رویای من تعبیر شد😍 عشق پیش روی من تصویر شد آمدی و زادگاه عشـــق من♥️ فصل تابستان‌ و ماه تیر شد. #امیرعباس_خالقوردی

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

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.

محافظ چنل
@samaedell · 2
Telegram ranks this channel #44 of 96 here — alongside 95 others — read 24 August 2026
استور‌ی خاص
@StoryeKhas · 100,228
Telegram ranks this channel #78 of 82 here — alongside 81 others — read 15 August 2026

This channel appears in 2 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“نَفَـــسِ عِشـــق” (@nafasse_eshgh), 5,204 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/nafasse_eshgh.

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.