Telegram RegisterThe public register of Telegram
Telegram profile photo for BharatIntel360

Channel

BharatIntel360

@BharatIntel360

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

7,906subscribers

+240 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002541322343
TypeChannel
Username@BharatIntel360
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/BharatIntel360

Growth

7,6667,9067,7867 August 2026 — 7,666 subscribers8 August 2026 — 7,667 subscribers10 August 2026 — 7,695 subscribers14 August 2026 — 7,719 subscribers17 August 2026 — 7,723 subscribers20 August 2026 — 7,733 subscribers23 August 2026 — 7,802 subscribers27 August 2026 — 7,819 subscribers30 August 2026 — 7,851 subscribers2 September 2026 — 7,880 subscribers7 September 2026 — 7,906 subscribers7 August 20267 September 2026
11 measurements spanning 31 days, net +240. 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 7,630–7,942 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 09:007,906+26
2 Sept 2026, 04:027,880+29
30 Aug 2026, 05:287,851+32
27 Aug 2026, 02:357,819+17
23 Aug 2026, 23:547,802+69
20 Aug 2026, 16:587,733+10
17 Aug 2026, 20:547,723+4
14 Aug 2026, 17:577,719+24
10 Aug 2026, 22:467,695+28
8 Aug 2026, 03:207,667+1
7 Aug 2026, 16:177,666first reading

Engagement

193 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.37%
avg views ÷ 7,906 subscribers
Avg views / post
662
133 posts measured
Reaction rate
3.22%
reactions ÷ views · ER floor
Posts in window
137
of 193 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 28 August 2026
Posts held193 (6 August 202628 August 2026)
Views total87,987
Reactions total2,830
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 20:26 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.

What this channel posts

Video runtime
15m 58s
Average length
34s

Measured directly from 28 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

4,111 reactions across 185 posts, in 24 distinct kinds. The most used accounts for 21.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥88421.5%
78719.1%
👍55013.4%
😁42110.2%
🤡3187.74%
🤣2285.55%
💯2095.08%
👀1774.31%
👎721.75%
🤬701.70%
🙏691.68%
😭481.17%
😡410.997%
🗿390.949%
💔310.754%
😱300.73%
❤‍🔥280.681%
🥴280.681%
240.584%
180.438%
4 further kinds390.949%

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 186 of the 193 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 4,111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 193 most recent posts we hold, published 6 August 2026 to 28 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

28 Aug 2026, 17:20 UTC238 views9 reactionsread 28 August 2026

🇮🇳⚡PM Modi to Visit Uzbekistan & Kyrgyz Republic 🇺🇿 Uzbekistan: August 29–30 PM Modi will visit Tashkent and hold talks with President Shavkat Mirziyoyev to strengthen bilateral ties. 🇰🇬 Kyrgyz Republic: August 31–September 1 He will travel to Bishkek to attend the 26th SCO Summit, focusing on security, connectivity and economic opportunities. He is also expected to hold bilateral meetings with leaders of SCO membe

🔥9

28 Aug 2026, 12:51 UTC568 views18 reactionsread 28 August 2026
Photo

Nepal has informed that 98 Indian citizens are still missing.

😢15🙏3

Signed Axis_Mike

28 Aug 2026, 12:32 UTC563 views22 reactionsread 28 August 2026
Photo

India issues a notification for a likely long range missile test in the Indian Ocean Region, range is near 2,995 km Date | 02-03 September 2026

🔥19❤‍🔥2💯1

Signed Axis_Mike

28 Aug 2026, 09:37 UTC615 views18 reactionsread 28 August 2026

🚨 Infiltration Attempt Foiled in Rajouri Indian Army troops foiled an infiltration attempt along the Line of Control in the Nowshera sector of Rajouri. Troops detected the movement of an infiltrator and challenged the suspected terrorist, who opened fire at the troops. @BharatIntel360

🔥18

Signed Axis_Mike

28 Aug 2026, 09:03 UTC599 views25 reactionsread 28 August 2026

India to send a third military aircraft carrying 12 tonnes of relief supplies to Nepal later today. 🇮🇳🇳🇵 @BharatIntel360

19👍6

Signed Axis_Mike

28 Aug 2026, 07:57 UTC632 views31 reactionsread 28 August 2026
Photo

India has signed a deal with the US for Javelin anti-tank missiles.

👍20🔥92

Signed Axis_Mike

28 Aug 2026, 07:45 UTC596 views29 reactionsread 28 August 2026
Photo

USA Ambassador to India Sergio Gor has said that India is planning to buy Javelin anti-tank missiles. @BharatIntel360

🤡19👍62🔥2

Signed Axis_Mike

28 Aug 2026, 06:40 UTC579 views16 reactionsread 28 August 2026
Photo

Nepal authorities issue an alert, saying a dam on the Tibetan side has burst again. Security personnel, rescue teams and residents have been urged to move immediately to higher ground. @BharatIntel360

👀16

Signed Axis_Mike

28 Aug 2026, 06:37 UTC570 views13 reactionsread 28 August 2026
Photo

🇵🇰⚡ According to local sources, a powerful blast was reported at 9 Number Market in Makin, Upper South Waziristan District, Khyber Pakhtunkhwa. Unconfirmed reports indicate that casualties may have occurred. Further details are awaited. @BharatIntel360

😁13

Signed Axis_Mike

28 Aug 2026, 05:49 UTC592 views21 reactionsread 28 August 2026

🇮🇳⚡🇵🇰 According to initial reports, an alert was sounded along the Line of Control (LoC) after troops spotted suspicious movement near a forward post. Multiple gunshots were reportedly heard, and security forces cordoned off the area ahead of a search operation scheduled for early Thursday morning. Further details are awaited. @BharatIntel360

15🔥6

Signed BharatIntel360_PR

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

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 2 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.

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

“BharatIntel360” (@BharatIntel360), 7,906 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/BharatIntel360.

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.