Channel
@Army_Area
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
15,502subscribers
-308 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001086010124 |
|---|---|
| Type | Channel |
| Username | @Army_Area |
| Created | 2 January 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/Army_Area |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 01:48 | 15,502 | -9 |
| 2 Sept 2026, 00:03 | 15,511 | +14,986 |
| 26 Aug 2026, 07:14 | 525 | -15,395 |
| 25 Aug 2026, 07:22 | 15,920 | -5 |
| 24 Aug 2026, 09:08 | 15,925 | -10 |
| 22 Aug 2026, 20:13 | 15,935 | -2 |
| 21 Aug 2026, 10:44 | 15,937 | -15 |
| 20 Aug 2026, 12:03 | 15,952 | -14 |
| 19 Aug 2026, 11:46 | 15,966 | -9 |
| 18 Aug 2026, 09:52 | 15,975 | -7 |
| 17 Aug 2026, 09:54 | 15,982 | -8 |
| 15 Aug 2026, 20:52 | 15,990 | +57 |
| 14 Aug 2026, 12:46 | 15,933 | +153 |
| 13 Aug 2026, 01:02 | 15,780 | +5 |
| 12 Aug 2026, 00:43 | 15,775 | -6 |
| 11 Aug 2026, 03:18 | 15,781 | -16 |
| 10 Aug 2026, 04:20 | 15,797 | +1 |
| 9 Aug 2026, 07:54 | 15,796 | -4 |
| 8 Aug 2026, 09:41 | 15,800 | -6 |
| 7 Aug 2026, 06:21 | 15,806 | first reading |
332 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 40 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 1 of 332 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 August 2026 |
|---|---|
| Posts held | 332 (5 August 2026 – 25 August 2026) |
| Views total | 354,630 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Aug 2026, 14:22 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.
Measured directly from 51 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
حالا ما که ایشان رو از چنل بن و ریموو کردیم ولی نمیدونید ادمینهایی که بدون انگیزه مالی و صرف عشق به آیدلاشون واسه این چنل و هر چنل فنبیس دیگهای وقت و انرژی میذارن چه زجری میکشن که مجبورن هر سری قصد و نیتشونو به چهارتا تازه وارد که چاک دهنشونم بسط نداره ثابت کنن. شاید تا الان من این جنبهی چنل رو به وضوح وارد صحنه رسمی چنل نمیکردم و خودمون حلش میکردیم یا زبان به دهن میگرفتیم و تحمل میکردیم ولی به نظرم دیگه بسه…
خوشگلایی که نمیدونید بعضی شبه آرمیا حاضرن از چه کاهی کوه بسازن میتونید درامارو ازینجا دنبال کنید https://t.me/bfreply/112723 🦋 ⁞ 𝑴𝒂𝒏𝒊 𝑴𝒐𝒏𝒊 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
بعضی چنلهای دیفند بنگتن که صاحباشون زیر ۱۳ سالشونه هم خوب آبروی آرمی رو به صورت ملی و بینالمللی بردن. عزیزم به خودت بیا :)) ده سال سابقهی Ot7 بودن با رگ غیرت تو زیر سوال نمیره💋 این خطاب به اون نانازاییه که مثل کفتار نشستن کف چنل منتظر که سریع سوتی بگیرنو فوروارد کنن تا دو نفر دیگه مثل خودشون که فکر میکنن یه شوخیم حق نداریم بکنیم با پسرا بریزن سرمون و انواع اقسام اتهامارو بزنن 😂 🦋 ⁞ 𝑴𝒂𝒏𝒊 𝑴𝒐𝒏𝒊 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
همونقدر که برای تمام عکسهای یونگی، میم گربهای داریم، برای جئون هم میم داریم :دی 🌻 ⁞ 𝒔𝒖𝒏 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
بنگتن به عنوان جاسوییچی: +thv IG Update 🍉 ⁞ 𝑴𝒆𝒍𝒐𝒏 🪫 ⁞ 𝑵𝒐𝒙 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
بخش سایبری فندوم فهمیدن اکانت تیکتاک جیمین 2021 ساخته شده و الانم قابل شیر کردن نیست چون هنوز از پرایوتی در نیومده، به گمانم مردی از دیروز که تصمیم گرفته یه اپ به اپای تار عنکبوت بستهاش اضافه کنه، نشسته تمام guilty pleasureهایی که لایک کرده رو پاک میکنه تا ابروش در سطح فندوم مثل آب جاری نشه. 🍉 ⁞ 𝑴𝒆𝒍𝒐𝒏 🏹 ⁞ 𝑸𝒖𝒑𝒊𝒅 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
یه اکانت به اسم جیمین تو تیکتاک پابلیش شده که تیک آبی گرفته و فندوم حدس میزنن یحتمل خود جیمین باشه. یکی بره به این بلوند خانه خراب کن بگه تو اگه بیل زنی رمز اینستاتو یادت نره، الان پاشدی تیکتاک زدی رمز اینم یادت بره مارو خون به جیگر کنی؟ 🍉 ⁞ 𝑴𝒆𝒍𝒐𝒏 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
«ما غمانگیزترین خداحافظی فستا رو خواهیم دید.» «برای دیدن اینکه دوباره همگی توی لایو هفت نفره جمع بشن باید بیشتر از ۷۳۰ روز صبر کنی.» «فیل کوچولوی بازوی تهیونگ قراره به یه تیرانوسوروس تبدیل بشه.» 💠 ⁞ 𝑲𝒂𝒘𝒂𝒊𝒊 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
«هرکدومشون دیگه توی خونهی خودشون زندگی میکنن.» «یونگی یه گربهی سیاهِ بامزه به اسم تنگی داره.» «همهی آلبومهای سولوشون منتشر شده و هرکدوم یه دنیای جداست.» «اکانت اینستاگرام همهشون فعاله.» «یونتان دیگه پیشمون نیست.» «جونگکوک یه دوبرمن به اسم بَم داره.» «و جین، هنوزم مکنهی واقعی گروهه.😭» 🃏 ⁞ 𝑱𝒐𝒌𝒆𝒓 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
«یونگی شونهشو سپرد به تیغ جراحی» «پسرا سربازی رو تموم کردن» «بدون حضور BT21، لختِ همه رو دیدیم» «نامجون با جاده به صلح رسید و بالاخره گواهینامه گرفت» «جیمین گیسوی طلاییش رو بلند کرد» 🃏 ⁞ 𝑱𝒐𝒌𝒆𝒓 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
انیگما جئون و آلفا مین؟🥵 🃏 ⁞ 𝑱𝒐𝒌𝒆𝒓 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
طوری که هوبی بچه تربیت کرده vs طوری که جین بچه تربیت میکنه 🫧 ⁞ 𝑩𝒖𝒃𝒃𝒍𝒆 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
Showing the 12 most recent of 332 posts we hold for @Army_Area. 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.
@Army_Area edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
کدوم یکی از ممبرها میتونه یک روز کامل بدون حرف زدن دوام بیاره؟ 🌻 ⁞ 𝒔𝒖𝒏 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
کدوم قسمت ران بیتیاس رو بیشتر دوست داشتین؟ 🌻 ⁞ 𝒔𝒖𝒏 ‧₊˚✧ 𝑨𝒓𝒎𝒚𝑨𝒓𝒆𝒂
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 332 most recent posts we hold, published 5 August 2026 to 25 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 296,402 of 1,630,085 entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 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.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“•. 𝐁𝐚𝐧𝐠𝐭𝐚𝐧 𝐅𝐚𝐦𝐢𝐥𝐲⁷ .•” (@Army_Area), 15,502 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/Army_Area.
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.