Telegram RegisterThe public register of Telegram
Telegram profile photo for NabrezhnyeIntel

Channel

NabrezhnyeIntel

@NabrezhnyeIntel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,883subscribers

-44 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001666040029
TypeChannel
Username@NabrezhnyeIntel
Created6 July 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live28 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/NabrezhnyeIntel

Growth

2,8832,9272,9056 August 2026 — 2,927 subscribers6 August 2026 — 2,927 subscribers7 August 2026 — 2,922 subscribers9 August 2026 — 2,915 subscribers12 August 2026 — 2,909 subscribers16 August 2026 — 2,902 subscribers19 August 2026 — 2,895 subscribers23 August 2026 — 2,891 subscribers25 August 2026 — 2,885 subscribers28 August 2026 — 2,883 subscribers6 August 202628 August 2026
10 measurements spanning 22 days, net -44. 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 2,876–2,934 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 21:162,883-2
25 Aug 2026, 20:282,885-6
23 Aug 2026, 00:142,891-4
19 Aug 2026, 17:132,895-7
16 Aug 2026, 15:372,902-7
12 Aug 2026, 18:152,909-6
9 Aug 2026, 19:332,915-7
7 Aug 2026, 05:222,922-5
6 Aug 2026, 11:032,927no change
6 Aug 2026, 10:002,927first reading

Engagement

19 posts held, back to 2 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 28 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
59s
Average length
59s

Measured directly from 1 video 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

517 reactions across 19 posts, in 17 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
17834.4%
👍13025.1%
6011.6%
🔥316.00%
🙏265.03%
🤩265.03%
😎244.64%
👏203.87%
🫡122.32%
🎉20.387%
🤣20.387%
👎10.193%
👨‍💻10.193%
😁10.193%
😘10.193%
🤓10.193%
🤔10.193%

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 19 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 517reactions 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 2 June 2025 to 28 October 2025, 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 Oct 2025, 11:37 UTC≈2,630 views19 reactionsread 7 August 2026
Forwarded from @Novichok_Rossiya_2Photo

Destruction of a T-72EA tank (incorrectly identified as a T-80) of the Armed Forces of Ukraine by FPV drone crews of the "Somali" separate assault battalion "Somali" between Krasnoarmeysk and Dimitrov. The graveyard of Ukrainian armored vehicles on the key supply artery of the Armed Forces of Ukraine continues to expand. Loss card and reference: https://lostarmour.info/armour/62574

14👍5

25 Oct 2025, 02:08 UTC≈3,780 views17 reactionsread 7 August 2026
Photo

📌#Kostyantynovka ⚠️ The Russian Armed Forces began assault operations against the city of Kostyantynovka. 🔻 With the capture of half of Predtechnye, the RF Armed Forces continue on this front along the T0504 road, however, with strong pushback. 🔻 Nearby the settlement of Oleksandro-Shutlynoye, the RF Armed Forces managed to take control of this settlement and thereby, enter the first streets of Kostyantynovka. ✅

👍15👎1🙏1

13 Sept 2025, 12:27 UTC≈2,830 views28 reactionsread 7 August 2026

📌 The RF Armed Forces entered the regional city of Kostyantinovka in Donetsk Oblast. Report soon.

21🙏5👍2

13 Sept 2025, 09:24 UTC≈2,740 views22 reactionsread 7 August 2026
Forwarded from @Novichok_Rossiya_2Photo

The Ukrainians have started whining a lot about the situation in Kupyansk. They even claim that our forces supposedly already control most of the city. For now, this is an obvious exaggeration, but we'll see. We can talk about MOST of the city only when we cross the railway in the western part of the city along its entire length and secure our position.

👍201🙏1

12 Sept 2025, 23:40 UTC≈2,120 views28 reactionsread 7 August 2026
Photo

📌#Lyman ⚠️ The RF Armed Forces are less then 7km away from Lyman. 🔻 They entered into the settlements of Shandryholovye, Derylovoye, Seredjne, and Karpovka. Fighting continues here, with some of these settlements being under at-least 75% Russian control. 🔻 To the west, the settlements of Zarochnoye and Torskoye seem to be confidently under Russian control. And there are some major advances continuing in the Serebr

22🔥3👍2😘1

2 Aug 2025, 02:09 UTC≈3,080 views45 reactionsread 7 August 2026
Photo

📌#ChasovYar ⚠️ The city of Chasov Yar came under Russian control. 🔻 After nearly 16 months of consistent fighting through this challenging city, the RF Armed Forces managed to capture Chasov Yar. The town was relatively well defended. 🔻 The town was defended by nearly 6 brigades. The slow yet steady grind forward from Russian 'Ivanovo' paratroopers after the capture of Artemovsk, and now Chasov Yar, demonstrates a

22🤩10🫡92😎2

31 Jul 2025, 05:58 UTC≈2,410 views35 reactionsread 7 August 2026

📌 The remaining part of Chasov Yar came under Russian control. Report soon.

😎207🤩4👏31

27 Jul 2025, 12:58 UTC≈2,750 views26 reactionsread 7 August 2026
Photo

📌#Lugansk ⚠️ More then 99.5% of Lugansk Oblast is in Russian control. Only an area of 22.9km2 remains. 🔻 The final settlement of Lugansk Oblast under Ukrainian control, Gregovka, fell under Russian control some weeks ago. Since then, incremental Russian advances see the RF Armed Forces edge closer to the remaining Ukrainian part of Lugansk. 🔻 For now, the complete capture of Lugansk Oblast only serves a symbolic m

🔥126👍51👏1🤩1

27 Jul 2025, 01:52 UTC≈2,280 views26 reactionsread 7 August 2026
Photo

📌#Kupyansk ⚠️ The situation in Kupyansk continues to evolve; and a-lot of speculation has begun about the situation in the city. 🔻 Most of the critical fighting takes place near the outskirts of Kupyansk, Moskovka, and Palamarovka. On the outskirts of Kupyansk, the RF Armed Forces managed to (finally) secure Golubovka and enter Kupyansk. 🔻 Near Moskovka, Russian forward elements managed to enter the settlement, wh

👍1473👏1🤩1

26 Jul 2025, 03:26 UTC≈1,340 views29 reactionsread 7 August 2026

📌 This weeks reports are to be published soon. We apologise for the inactivity.

👍23🎉2🤣2👏1😁1

12 Jul 2025, 05:38 UTC≈2,170 views28 reactionsread 7 August 2026
Photo

📌 #Kharkov ⚠️ The RF Armed Forces are making tactical offensives along the Kharkov - Vovchansk frontline. 🔻 The RF Armed Forces made significant advances from the border area, and are advancing in the direction of the Vovchansk highway. This is the primary MSR for the Ukrainian garrison in Vovchansk. 🔻 Although the situation in Vovchansk remains somewhat stagnant - in an offensive scenario, the RF Armed Forces wou

19👏42🙏2🤩1

12 Jul 2025, 03:24 UTC≈1,800 views26 reactionsread 7 August 2026

📌 The city of Chasovoy Yar is 96% under the control of the Russian Armed Forces.

🔥16👏4🤩3🙏21

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Suriyakmaps
@Suriyak_maps · 46,631
Telegram ranks this channel #6 of 80 here — alongside 79 others — read 27 August 2026
AMK Mapping
@AMK_Mapping · 57,227
Telegram ranks this channel #13 of 78 here — alongside 77 others — read 23 August 2026
Military Summary
@militarysummary · 77,457
Telegram ranks this channel #16 of 77 here — alongside 76 others — read 19 August 2026
World Pravda
@worldpravda · 54,123
Telegram ranks this channel #43 of 82 here — alongside 81 others — read 24 August 2026
War Leaks 18+ (Channel)
@warleaks11 · 69,006
Telegram ranks this channel #46 of 74 here — alongside 73 others — read 27 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“NabrezhnyeIntel” (@NabrezhnyeIntel), 2,883 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/NabrezhnyeIntel.

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.