Telegram RegisterThe public register of Telegram

Channel

Jᴜʙᴀʏᴇʀ Aʀᴍʏ

@Jubayer_Army

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,135subscribers

+159 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004320921936
TypeChannel
Username@Jubayer_Army
Created9 July 2026measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Jubayer_Army

Growth

9761,1351,055.57 August 2026 — 976 subscribers8 August 2026 — 976 subscribers8 August 2026 — 1,000 subscribers11 August 2026 — 1,060 subscribers14 August 2026 — 1,135 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +159. 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 952–1,159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:481,135+75
11 Aug 2026, 17:021,060+60
8 Aug 2026, 13:531,000+24
8 Aug 2026, 00:46976no change
7 Aug 2026, 23:03976first reading

Engagement

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

ERR · 30 days
100.3%
avg views ÷ 1,135 subscribers
Avg views / post
1,140
14 posts measured
Reaction rate
0.119%
reactions ÷ views · ER floor
Posts in window
14
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. It is computed over the 10 of 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (9 July 20265 August 2026)
Views total15,943
Reactions total14
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:46 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.

Reaction mix

20 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1050.0%
😁315.0%
🐳210.0%
👍210.0%
🔥210.0%
15.00%

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 13 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 20reactions 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 9 July 2026 to 5 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.

Recent posts

5 Aug 2026, 01:38 UTC693 views1 reactionsread 8 August 2026
Photo

✅ PREMIUM FREE FIRE TELEGRAM EMOTE BOT SOURCE LEAK ✅ 💥 Finally Released! One of the cleanest and most powerful Free Fire Emote Telegram Bot Sources is now available. ✨ Premium Features ⚡️ Lightning-fast emote processing 🎭 Advanced emote management system 👥 Multi-admin support 📢 Broadcast system for all users 📊 Live bot statistics dashboard 📡 API health monitoring 🗄 SQLite database integration 🔒 Secure owner & admin

🐳1

1 Aug 2026, 15:01 UTC866 viewsread 8 August 2026
Photo

💀 TELEGRAM REFER TO EARN BOT SOURCE LEAK 💀 🔥 The Premium Telegram Refer To Earn Bot Source Code is now LEAKED! Looking to launch your own Telegram Refer & Earn bot or customize a powerful referral system? This source includes everything you need. ⚡️ Features Included 👤 User Panel 💰 Wallet System 🎁 Refer & Earn Rewards 📊 Balance Checker 💸 Withdraw Request System 👥 Referral Statistics 📜 Transaction History 🛠 Admin

1 Aug 2026, 02:39 UTC≈1,430 viewsread 8 August 2026
Photo

💀 NEW DARK DESIRE BUNDLE SPINNER SOURCE LEAK 💀 ❤️ Features : ✅ Extrem Level Ui ✅ OB54 Updated ✅ 100% Working Source ✅ Just Add Your token.json ✅ And Run This Source ✅ Get Free Dark Desire Bundle ☠️ Leaked By : @jubayer_codex 🔥 Give A Reaction For My Hard Works

31 Jul 2026, 13:53 UTC908 views1 reactionsread 8 August 2026
Photo

💀 DARK DESIRE Bundle ID Leak 💀 🔥 The wait is finally over! The DARK DESIRE Bundle ID has officially been leaked. 📦 Leak Includes: ✅ Latest Bundle ID ✅ 100% Anti Ban ID ✅ Freshly collected information 😎 Leaked By : @jubayer_codex ❤️ Give A Reaction For My Hard Work

1

26 Jul 2026, 12:21 UTC≈1,230 viewsread 8 August 2026
Photo

🛡 JUBAYER PROTECTOR IS NOW LIVE! 🛡 Protect your Telegram groups with JUBAYER PROTECTOR — an advanced security bot designed to keep your community safe automatically. ✨ Main Features 🔗 Anti-Link Protection 📩 Anti-Forward Messages 👤 Anti-Username Filter 🚫 Anti-Spam System 🤖 Anti-Fake Account Detection 🛡 Anti-Bot Detection ⚡️/Protect on & /protect off to enable or disable protection instantly 🔇 Reply-based Mute / Unm

25 Jul 2026, 06:52 UTC≈1,430 views1 reactionsread 8 August 2026
Photo

🤖 PARMANENT AI API SOURCE LEAK 🤖 ✅ Python Flask Based ✅ g4f Client Integrated ✅ Simple GET API ✅ Fast & Easy to Setup ✅ Just Install & Run 💎 Ready-to-use source code is now available. 💀 Source By : @jubayer_Codex ❤️ Give A Reaction For My Hard Works

1

24 Jul 2026, 15:02 UTC619 viewsread 8 August 2026
Photo

🚀 TELEGRAM VIEWS API SOURCE LEAK 🚀 🔥 Finally Released! The powerful Telegram Views API Source is now available. ⚡️ Features: ✅ Fast Telegram Views API ✅ .env Configuration ✅ Just add your API_ID, API_HASH, and SESSION_STRING ✅ Clean & Well-Organized Source Code ✅ Easy Setup & Ready to Use ✅ Stable Performance 📦 Setup is Simple: Add your API_ID Add your API_HASH Generate & paste your SESSION_STRING 💀 Made By : @

24 Jul 2026, 05:48 UTC761 views2 reactionsread 8 August 2026
Photo

☠️ TELEGRAM REPORT API LEAK ☠️ ✅ Unlimited Report ✅ Account/Channels/Groups Supported ✅ 100% Free Access ✅ No SubsCription ✅ But Limited Time Access 💀 Made By : @jubayer_Codex ❤️ Give A Reaction For My Hard Works

11

23 Jul 2026, 15:42 UTC886 views2 reactionsread 8 August 2026
Photo

🔥 AUTO TELEGRAM JOIN API SOURCE LEAK 🔥 ⚡️ Auto Join Groups & Channels ⚡️ Unlimited Session Support ⚡️ Auto .env Generation ⚡️ Easy Setup & Ready to Use Run: 1️⃣ session.py → Generate Session & .env 2️⃣ app.py → Start API 🌐 Endpoint: /get_join?group_like={group_or_channel_link} 💀 Made By : @jubayer_Codex ❤️ Give A Reaction For My Hard Works

1👍1

22 Jul 2026, 11:43 UTC≈1,570 views1 reactionsread 8 August 2026

✅ FREE FIRE ALL SOURCE ARE AVAIABLE ✅ ❤️ Avaiable Source : ✔️ Anti Ban Tcp Src ✔️ Info APi Src ✔️ Visit Api Src ✔️ Like Api Src ✔️ Level Up Bot Src ✔️ Guild Glory Website Src ✔️ Like Block TG Bot Src ✔️ Chat Gpt TG Bot Src ✔️ TG Reaction Api Src ✔️ TG File Store Bot Src ✔️ Hosting Website Src ✔️ 8lv 30 BD Server Account 💀 Bot By : @jubayer_codex 💰 All Price Files Are Buy In Low Price With Coins 😅 Refer Your Friend

1

21 Jul 2026, 04:22 UTC≈1,150 views1 reactionsread 8 August 2026
Photo

💀 TELEGRAM ANONYMOUS CHAT BOT SOURCE LEAK 💀 A clean and lightweight Telegram Anonymous Chat Bot source is now available! 🔥 ✨ Features: ✔️ User → Admin Message Forward ✔️ Admin → Reply → User ✔️ Owner/Admin Identity & Privacy Protected 🔒 ✔️ Users Can't See Owner's Username or Personal Information ✔️ Supports Text, Photo, Video, Voice, Sticker & Documents ✔️ No Database Required 📦 Just add your BOT_TOKEN & ADMIN_ID

1

17 Jul 2026, 09:28 UTC≈1,410 views2 reactionsread 8 August 2026

🚨 TELEGRAM AI AGENT SOURCE LEAK 🚨 The source is 100% fully prepared — just add your Bot Token and you're ready to launch! 🚀 ✨ Features: • 🤖 Advanced AI Agent • 💬 Human-like Conversations • 🧠 Smart Context Memory • ⚡️ Fast Response Speed • 🔧 Clean & Well-Organized Source • 📂 Full Source Code Included • 🛠 No Extra Setup Required • ✅ Just Add Your Bot Token & Run 💀 Made By : @jubayer_codex

2

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

Citation-graph rank

Citation-graph rank — 265,514 of 1,340,412entries 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.

Forward network

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.

Mentions

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

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Jᴜʙᴀʏᴇʀ Aʀᴍʏ” (@Jubayer_Army), 1,135 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Jubayer_Army.

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.