7 measurements spanning 39 days, net -10. 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 102–115 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Sept 2026, 02:37
103
-1
8 Sept 2026, 07:39
104
-3
30 Aug 2026, 02:45
107
-1
22 Aug 2026, 05:25
108
-1
15 Aug 2026, 00:47
109
-4
9 Aug 2026, 06:17
113
no change
7 Aug 2026, 17:48
113
first reading
Engagement
19 posts held, back to 8 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 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 19 posts for this entry, the most recent from 31 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
1m 05s
Average length
22s
Measured directly from 3 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.
Reaction mix
14 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5999319239423430783
6
42.9%
❤
6
42.9%
👍
2
14.3%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 3 of the 19 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 8 January 2026 to 31 January 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.
خب دوستان سیزن بهم میخوره
با توجه به شرایط
کسایی که شاپ زدن برقرار و در مدرن قایل استفاده هست
لینک چنل مدرن عضو گیری به زودی آغاز خواهد شد
@blueup_news
✯𝙱𝚄𝙿 𝚃𝙾𝚃𝙰𝙻 𝙲𝙷𝙰𝙽𝙽𝙴𝙻𝚂✯
「📢」- ɴᴇᴡs ➫ @blueup_news
「📚」- ʀᴜʟᴇs ➫ @blueup_rule
「⚔」- ᴡᴀʀs ➫ @blueup_war
「🛍」- sʜᴏᴘ ➫ @blue_up_shop
「💬」- ɢᴀᴘ ➫ @blueup_gape
═══════════════
𝑶𝑾𝑵𝑬𝑹𝑺:
♕ @Hossein8hm
♔ @Am_dVvV
BUP
NEWS 🗞️ information ✅
تحلیل اوضاع منطقه بالکان «بلغارستان-رومانی-یوگوسلاوی-یونان»
--------------------------------------
💢منطقه بالکان شاهد اتفاقات گسترده و مرکز توجه جنگ های پر شمار در تمام زمینه های دریایی زمینی و هوایی بود
🌟یوگوسلاوی با تقویت به شدن زیاد ارتش خود توانست به قدرت زیادی دست پیدا کند اما همین زنگ خطری برای نیروهای محور شد تا ایتالیا آلمان سوعد و به خصوص بلغارستان دشمن شماره یک آنها جنگ های متعددی…
لیست پلیر هایی که کشور داشتن
کسایی که فعلا اعلام اعلام آمادگی کردند تیک خورده بقیه فعلا افن
اونایی که نیازمند پلیر نوشته شده قطعاً خالیه و برای دریافت پیام بدید
بریتانیا ✅
سوعد ✅
شوروی✅
هند✅
آمریکا ✅
آلمان ❌ نیازمند پلیر 🎖️
یوگوسلاوی✅
بلغارستان ❌
مجارستان ✅
یونان✅
رومانی ✅
بلژیک ✅
ایتالیا ❌ نیازمند پلیر
ژاپن✅
ترکیه ✅
چین✅
نروژ❌
مکزیک❌ نیازمند پلیر
کانادا✅
فنلاند ✅
فرانسه ✅
بر و بچ نتا اوکی شد اگه موافقید استارت کنیم از فردا شب
امشبم یه خلاصه جامع میزنم بفهمید جریان چی بوده کی با کی بوده
کلا جریان بازی چی بوده
اگر موافق هستید بگید
BUP
NEWS 📰 army 🪖
-----------------------------------------
حملات غافلگیر کننده ایتالیایی ها به یوگوسلاوی
✔️ایتالیا نیر از شرایط موجود تمام استفاده را کرده و به
سمت شمال این کشور تهاجم کرد
⚠️مناطق مشخص شده در نقشه به اشغال نیروهای موسولینی در آمد
ایتالیایی که تا الان اقدام نظامی موثری انجام نداده بود با این تهاجم قدرت خود را نشان داد
اوضاع برای یوگوسلاوی جالب نیست و شدید تر شدن حملات نتایجی جبران ناپذیر برای این ک…
علت حمله به بلغارستان ما این بود که به دولت شوروی و حکومت کمونیستی حمله کرد و ما نیز حکومتمان کمونیستیس و برای نشان دادن قدرت کمونیست این کار را کردیم ما بلغارستان را در نقشه مشاهده نمیکنیم در برابر عظمت نقشه خودمان تصمیم شما چه بود؟ آیا دلیلی بر این کار دارید؟
👤 یک بیانیه جدید از: Yugoslavia II BUP
BUP
NEWS 📰 army 🪖
-----------------------------------------
حملات سریع رومانی به بلغارستان
💢ارتش رومانی از درگیری و تمرکز بلغار ها به شرق تمام حد استفاده لازم را برد
⚠️طی این حملات آنها بر تمامی رود دانوب مسلط شده و شهر روبه و سلسترا را به اشغال خود در آوردند
تمامی مکان های مهم و حاصلخیز اطراف مرز نیز به اشغال رومانی در آمد‼️
گرچه پیشروی زیاد نبود اما مانع طبیعی یعنی رود دانوب که زد شدن از آن در مواقع اضطراری سخت…
همانگونه که تو با مشورت اعضای برخی متفقین به بلغارستان حمله کردی بلغارستان با تصمیم خودش اقدام کرده ، اعضای متحدین دستوری از سوی المان نمیگیرند چون مستقلن
👤 یک بیانیه جدید از: Germany II BUP
خطاب به آلمان نازی:
اگر هدف شما امنیت مردم بود میتوانستید در تصمیمات دولت بلغارستان مشورت هایی داشته باشید آنها به مردم بی دفاع ما حمله کردند و ما حق پاسخ داشتیم ولی اینکه شما ۳ نفر وارد میدان شدین ینی جنگی تمام عیار ینی بزدلی که بجای گفتگو و حل مشکل و صلح به جنگافرازی ادامه دادید هیچ پاسخ منطقی ای ندارید در جواب این چون شما کاری علیه ما انجام دادین که نوعی اعلان جنگ است و پاسخش را به زودی خواهید دید منتظر باشید
…
Signed blue game
Showing the 12 most recent of 19 posts we hold for @news_blueup_ww2. 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.
Polls
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.
دوستان الان ریست کنم یا اینکه همینجوری که تحلیل زدم واسه همه کشورها تحلیل بزنن بفهمم اوضاع شون چیه
ریست کن74%
نه همین تحلیل کن ادامه بدیم26%
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 19 most recent posts we hold, published 8 January 2026 to 31 January 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.
Mentions
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.
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 16 September 2026 — this
entry's latest reading, not the date you are reading this.
“𝗕𝗟𝗨𝗘 𝗨𝗣 ll” (@news_blueup_ww2), 103 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/news_blueup_ww2.
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.