Video message, posted without a caption
❤7

Channel
@bhnazixplanstory
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,688subscribers
+15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003106530606 |
|---|---|
| Type | Channel |
| Username | @bhnazixplanstory |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/bhnazixplanstory |
Marketing & affiliate — 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 61% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 17:38 | 2,688 | -6 |
| 12 Sept 2026, 09:37 | 2,694 | -11 |
| 7 Sept 2026, 21:39 | 2,705 | -16 |
| 3 Sept 2026, 06:19 | 2,721 | -13 |
| 30 Aug 2026, 14:16 | 2,734 | -6 |
| 27 Aug 2026, 21:48 | 2,740 | -5 |
| 24 Aug 2026, 11:05 | 2,745 | -5 |
| 20 Aug 2026, 22:45 | 2,750 | +30 |
| 17 Aug 2026, 18:44 | 2,720 | +12 |
| 14 Aug 2026, 14:25 | 2,708 | +12 |
| 11 Aug 2026, 12:58 | 2,696 | +21 |
| 8 Aug 2026, 02:37 | 2,675 | +2 |
| 7 Aug 2026, 17:02 | 2,673 | first reading |
20 posts held, back to 5 August 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 1 page 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
218 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 81.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 177 | 81.2% | |
| 👍 | 15 | 6.88% | |
| 👏 | 14 | 6.42% | |
| 🥰 | 5 | 2.29% | |
| 😢 | 4 | 1.83% | |
| 🗿 | 2 | 0.917% | |
| 👀 | 1 | 0.459% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 18 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 218 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Video message, posted without a caption
❤7
سه تا سناریو برات فرستادم بروووو عشششق کن👀
❤6🥰3
هوک: «دیدی مهمونا توی همون چند دقیقه اول، درباره پذیرایی یه نظر توی ذهنشون میسازن؟» مشکل: «اگه میز پذیرایی نامرتب یا ساده باشه، زحمتت کمتر دیده میشه.» راهحل: «چیدمان حرفهای فینگرفود، بدون اینکه کار اضافهای انجام بدی، میزت رو شیکتر نشون میده.🤍»
👍5❤1
هوک: «دیدی تا مهمونی تموم میشه، اولین فکری که به ذهنت میاد اینه که: “نکنه غذا کم اومده باشه؟”» مشکل: «این استرس باعث میشه نصف مهمونی رو اصلاً ازش لذت نبری.» راهحل: «برای همین قبل از ثبت سفارش، تعداد مهمونها رو بررسی میکنیم تا مقدار فینگرفود متناسب با مراسمت انتخاب بشه.
❤3
هوک: «دیدی توی مهمونی، به جای کنار مهمونات بودن، مدام درگیر سرو غذا میشی؟» مشکل: «آخر مراسم میفهمی اصلاً فرصت نکردی از مهمونی لذت ببری.» راهحل: «فینگرفود باعث میشه پذیرایی راحتتر باشه و وقت بیشتری کنار مهمونات بگذرونی.»
❤3
#پیام_ناشناس غذا بهناز جان تورو خدا برای فروش دوره ی غذا بگو برای فینگرفود @HarfBeManBot
👍1
هوک: «دیدی بعد از خرید خونه، تازه متوجه یه عالمه ایرادش میشی؟» مشکل: «نور کم، همسایه، صدای خیابون… چیزایی که توی بازدید ۱۰ دقیقهای معلوم نیست.» راهحل: «برای همین قبل از معرفی هر فایل، فقط ظاهرش رو نمیبینیم؛ جزئیاتی رو بررسی میکنیم که بعداً باعث پشیمونی نشن کلمه ملک و بفرست چک لیست رایگانشو بزات بفرستم!!!
👍4
#پیام_ناشناس املاااک @HarfBeManBot
میخوام برا یه حوزه خیلی سخت مثال بزنم بفرستین اگ فک میکنید کم توجهی شده به حوزه اتون https://t.me/HarfBeManBOT?start=HBM10305391 . .
❤3🗿1
ماشالللللله تکنیکامون در لحظه میترکونه 😂
❤4🗿1
#پیام_ناشناس بهناز جون برای حوزه عطر دیشب ایده دادین امروز پیاده سازی کردم یدونه فروختمممم💙💙 ایدی خودتو ندارم بهت نشون بدم اسلایدامو @HarfBeManBot
هوک: «دیدی همه میگن روز عروسی فقط خوش بگذرون… ولی نصف عروس و دامادا تا آخر مراسم درگیر هماهنگی سالنن؟» مشکل: «مدام باید حواسشون به پذیرایی، موزیک و برنامهها باشه.» راهحل: «برای همین توی این تالار، تیم اجرایی همه چیز رو مدیریت میکنه تا شما فقط از شبتون لذت ببرید.🤍»
❤11
Showing the 12 most recent of 20 posts we hold for @bhnazixplanstory. 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.
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“پلن فعالسازی فالوور روح” (@bhnazixplanstory), 2,688 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/bhnazixplanstory.
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.