Telegram RegisterThe public register of Telegram
Telegram profile photo for 42 ОМБр

Channel

42 ОМБр

@ua_42nd_ombr

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

5,687subscribers

+60 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001921900399
TypeChannel
Username@ua_42nd_ombr
Created11 July 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held13
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/ua_42nd_ombr

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 68% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

5,6275,6995,6636 August 2026 — 5,627 subscribers6 August 2026 — 5,627 subscribers9 August 2026 — 5,631 subscribers12 August 2026 — 5,633 subscribers16 August 2026 — 5,645 subscribers19 August 2026 — 5,652 subscribers22 August 2026 — 5,677 subscribers25 August 2026 — 5,688 subscribers28 August 2026 — 5,698 subscribers31 August 2026 — 5,696 subscribers4 September 2026 — 5,699 subscribers9 September 2026 — 5,695 subscribers13 September 2026 — 5,687 subscribers5,6876 August 202613 September 2026
13 measurements spanning 38 days, net +60. 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 5,616–5,710 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 00:205,687-8
9 Sept 2026, 06:025,695-4
4 Sept 2026, 04:595,699+3
31 Aug 2026, 11:025,696-2
28 Aug 2026, 18:345,698+10
25 Aug 2026, 12:115,688+11
22 Aug 2026, 03:065,677+25
19 Aug 2026, 05:375,652+7
16 Aug 2026, 07:045,645+12
12 Aug 2026, 11:295,633+2
9 Aug 2026, 15:335,631+4
6 Aug 2026, 03:345,627no change
6 Aug 2026, 00:525,627first reading

Engagement

26 posts held, back to 1 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 8 pages 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 26 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1h 03m
Average length
2m 39s

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

2,838 reactions across 24 posts, in 17 distinct kinds. The most used accounts for 54.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,54254.3%
50017.6%
👍42014.8%
🫡2077.29%
👏1013.56%
😁180.634%
🎉100.352%
🙏90.317%
🖕80.282%
🍾70.247%
👻50.176%
👌40.141%
30.106%
🍌10.035%
💋10.035%
🤨10.035%
🥰10.035%

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

Measured over the 26 most recent posts we hold, published 1 July 2026 to 11 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

11 Aug 2026, 10:52 UTC860 views93 reactionsread 12 August 2026
Video

Файно палає! Ми підпалили! 🐷🐶 чомусь вирішили, що ми не знайдемо їхній склад речей. Що ж! Дронарі МПБ 42 ОМБр показали загарбникам, як ті помилялися

🔥66👍18🫡72

10 Aug 2026, 15:13 UTC≈1,250 views117 reactionsread 12 August 2026
Video

Якщо довго сидіти на березі річки, то рано чи пізно повз тебе пропливе труп твого ворога (східна мудрість). А якщо ти пілот дрона в засідці, то рано чи пізно повз тебе спробує просковзнути москаль. І тоді бійці МПБ 42 ОМБр влаштують кацапчику просмажку

🔥72👍2714👏2🫡1😁1

9 Aug 2026, 10:35 UTC≈1,390 views126 reactionsread 12 August 2026
Video

Цілі, що можуть завдати багато шкоди. Точніше - могли би, якби їх не позбивали підрозділи 42 ОМБр. Пишаємось роботою наших побратимів

🔥89👍25🫡8👏4

7 Aug 2026, 20:23 UTC≈1,910 views70 reactionsread 12 August 2026
Video

Показовий урок росіянам на їхній «день ВДВ» від воїнів 42 ОМБр! 💥 Спроба ворога «прощупати» нашу оборону завершилася для них тотальною катастрофою. Окупанти намагалися штурмувати позиції за допомогою квадроциклів, мотоциклів та малих піхотних груп. Результат? Їхні втрати за один день у 3-4 рази перевищили звичайні щоденні показники! Детальніше про ситуацію на фронті, відбиті штурми та роботу наших екіпажів БПЛА в е

🔥49👍17🫡4

6 Aug 2026, 19:37 UTC≈1,830 views113 reactionsread 12 August 2026
Video

Ще мінус дві гармати у під@рів. Лише оцініть, яка філігранна робота підрозділів 42 ОМБр

🔥77👍1514🫡6👻1

6 Aug 2026, 14:51 UTC≈1,870 views88 reactionsread 12 August 2026
Video

42-га ОМБр нищить ворога на Новопавлівському напрямку ⚔️ Ситуація на фронті постійно змінюється, але наші захисники завжди готові до нових викликів. Командир роти ударних БпЛА 42-ї окремої механізованої бригади Андрій зазначає, що ворог відмовився від масованих бронештурмів і намагається просуватися малими піхотними групами. Проте наші оператори виявляють та ліквідовують окупантів ще на підходах — за 20-25 кілометр

🔥52👍199🫡7👏1

5 Aug 2026, 14:57 UTC≈1,690 views126 reactionsread 12 August 2026
Video

Мінус дві рашистські гаубиці від наших хлопців!

🔥81👍30🫡7👌4👏31

1 Aug 2026, 19:56 UTC≈2,960 views61 reactionsread 12 August 2026
Video

Помилки можна виправити, а військовий досвід та цивільний фах — це те, що справді має значення. Це відео — реальний приклад того, що повернутися з СЗЧ можливо, і не просто повернутися, а продовжити службу на посаді, яка повністю відповідає вашим навичкам, знанням та професії. У 42 окремій механізованій бригаді ми цінуємо кожного фахівця. Якщо ви опинилися в такій ситуації, але прагнете повернутися до лав Сил оборон

👍4317🫡1

29 Jul 2026, 19:42 UTC≈3,210 views63 reactionsread 12 August 2026
Video

«Спартак» про оперативну обстановку у зоні відповідальності 42 ОМБр на Новопавлівському напрямку в ефірі Єдиних Новин. ПС: Ви також можете долучитись до збору на пікап для танкового батальйону за QR-кодом на відео або за посиланням - https://send.monobank.ua/jar/78mWjKfLpH

43🫡15👍5

27 Jul 2026, 14:24 UTC≈3,400 views93 reactionsread 12 August 2026
Video

Бліц від кухаря 42 ОМБр «Лазара» Смачного перегляду😅

58👏16😁14🫡41

25 Jul 2026, 17:06 UTC≈3,510 views143 reactionsread 12 August 2026
Video

Чудова робота від 42 ОМБр! Далі - більше!

🔥103🫡17👍139👻1

21 Jul 2026, 18:19 UTC≈4,500 views159 reactionsread 12 August 2026
Video

Кадри, як наші «Перуни» 42 ОМБр успішно знищують ворожу гаубицю! Додаємо до списку приємних речей для перегляду на вечір! Далі більше! Сайт | ФБ | Ютуб | Донат

🔥95👍4510🫡6👻2💋1

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

Mentions

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

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.

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.

47 окрема механізована бригада «Маґура»
@brygada47 · 52,416
Telegram ranks this channel #22 of 91 here — alongside 90 others — read 25 August 2026
110 ОМБр
@ombr_110 · 32,390
Telegram ranks this channel #33 of 87 here — alongside 86 others — read 5 September 2026
SIGNUM
@umftteam · 23,250
Telegram ranks this channel #38 of 84 here — alongside 83 others — read 18 September 2026
△ 225 ОШП △
@OSHP_225 · 23,986
Telegram ranks this channel #39 of 84 here — alongside 83 others — read 17 September 2026
Десантно-штурмові війська ЗС України
@ua_dshv · 35,146
Telegram ranks this channel #40 of 93 here — alongside 92 others — read 2 September 2026
✙Гострі Картузи✙
@gostrikartuzy · 25,700
Telegram ranks this channel #64 of 82 here — alongside 81 others — read 13 September 2026

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

“42 ОМБр” (@ua_42nd_ombr), 5,687 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/ua_42nd_ombr.

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.