Telegram RegisterThe public register of Telegram
Telegram profile photo for JAMAIKA GROUP

Channel

JAMAIKA GROUP

@bespilotnik156

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

326subscribers

+10 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003436269857
TypeChannel
Username@bespilotnik156
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/bespilotnik156

Growth

3163263216 August 2026 — 316 subscribers6 August 2026 — 318 subscribers6 August 2026 — 318 subscribers14 August 2026 — 320 subscribers21 August 2026 — 326 subscribers28 August 2026 — 325 subscribers12 September 2026 — 326 subscribers6 August 202612 September 2026
7 measurements spanning 37 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 315–328 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 05:38326+1
28 Aug 2026, 14:07325-1
21 Aug 2026, 04:34326+6
14 Aug 2026, 12:18320+2
6 Aug 2026, 22:16318no change
6 Aug 2026, 16:23318+2
6 Aug 2026, 02:34316first reading

Engagement

19 posts held, back to 20 June 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 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

262 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 20.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5420.6%
🫡4416.8%
❤‍🔥4216.0%
3212.2%
👍3111.8%
🙏259.54%
custom 529646426538798658193.44%
custom 533950796806699807993.44%
custom 523582860429782555172.67%
custom 533686232834220176651.91%
custom 527603046885099324731.15%
😡10.382%

Custom emoji. 5 of the rows above are 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 counts beside them are 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 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 262 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 20 June 2026 to 6 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

6 Aug 2026, 20:26 UTC29 views5 reactionsread 6 August 2026
Video

🌟🇷🇺

🔥3custom 52358286042978255512

6 Aug 2026, 20:24 UTC30 views3 reactionsread 6 August 2026
Video

Большое спасибо вам Сергей 🤝🇷🇺

❤‍🔥2👍1

5 Aug 2026, 07:13 UTC143 views9 reactionsread 6 August 2026
Video

ВСУшник перепутал окоп и случайно забежал к нашим

custom 52358286042978255515🔥21🫡1

28 Jul 2026, 21:13 UTC303 views16 reactionsread 6 August 2026
Video

💣💀💣 Поддержка наших штурмовых подразделений ведется сбросами с дронов, которыми активно уничтожаются засевшие на позициях украинские боевики а так тяжелые дроны Вампиры. Подержать расчёт БПЛА✈️ 2200 1551 8164 4994(Альфа Банк) Любой помощи будем рады❤️ Враг будет разбит, победа будет за нами 🇷🇺

8custom 53395079680669980794custom 52760304688509932473👍1

28 Jul 2026, 13:21 UTC293 views12 reactionsread 6 August 2026
Video

Действия бойца из Российского Африканского корпуса во время РПД Кадры 18+

👍8🫡2custom 53395079680669980792

27 Jul 2026, 05:40 UTC325 views5 reactionsread 6 August 2026

Камрады, прошу проголосовать за группу это поможет добавлять больше истории и реакции ❤️ https://t.me/boost/bespilotnik156

5

26 Jul 2026, 07:32 UTC≈2,680 views18 reactionsread 6 August 2026
Video

Раз, два, три, четыре, пять... Мы идем искать На архивных кадрах — работа расчётов БпЛА по живой силе противника. Боевики ВСУ пытались спрятаться среди деревьев и высокой растительности, думая, что их не найдут. Просчитались. У них был шанс сложить оружие и сохранить жизнь — но они им не воспользовались. Результаты - на видео.

👍7🫡5custom 52964642653879865814custom 53395079680669980792

19 Jul 2026, 19:40 UTC449 views17 reactionsread 6 August 2026
Photo

Так убей же немца, чтоб он, А не ты на земле лежал, Не в твоем дому чтобы стон, А в его по мертвым стоял.Так хотел он, его вина,— Пусть горит его дом, а не твой, И пускай не твоя жена, А его пусть будет вдовой. Пусть исплачется не твоя, А его родившая мать, Не твоя, а его семья, Понапрасну пусть будет ждать.Так убей же хоть одного! Так убей же его скорей! Сколько раз увидишь его, Столько раз его и убей!

❤‍🔥8🙏5🔥2🫡2

19 Jul 2026, 04:37 UTC392 views14 reactionsread 6 August 2026
Video

Сочная нарезка ликвидации свинопехоты🐷🙂

👍7🫡4❤‍🔥3

15 Jul 2026, 07:21 UTC421 views8 reactionsread 6 August 2026
Photo

ТРАГИЧЕСКИЕ КАДРЫ ГИБЕЛИ РУССКОГО ГЕРОЯ. Артёмовское направление. Кадры с коптера врага. Осень 2022 года. Тяжелораненый в бою командир группы ЧВК с позывным «Чердаш», чтобы не попасть в плен к ВСУ, оставаясь верным Родине, направляет автомат в своё сердце... Хотя это и трудновыполнимо из-за ранения. Видео неполное, но, вероятно, уйти из жизни «Чердашу» всё-таки удалось. После этого его добивает противник с воздуха. П

🙏8

10 Jul 2026, 09:30 UTC403 views2 reactionsread 6 August 2026

Камрады, прошу проголосовать за группу это поможет добавлять больше истории и реакции ❤️ https://t.me/boost/bespilotnik156

custom 53368623283422017662

10 Jul 2026, 09:29 UTC359 views10 reactionsread 6 August 2026
Video

🇷🇺💥🇺🇦Наш штурмовик подкрался к норе, в которой засел xoxол, и почти в упор ликвидировал его.

5🫡3👍2

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

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

“JAMAIKA GROUP” (@bespilotnik156), 326 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/bespilotnik156.

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.