Telegram RegisterThe public register of Telegram
Telegram profile photo for Угруповання військ (сил) "Південь"

Channel

Угруповання військ (сил) "Південь"

@SJTF_Odes

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cross-platform identity · Referenced elsewhere · Cite this entry

8,704subscribers

-233 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001609147612
TypeChannel
Username@SJTF_Odes
Created4 August 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/SJTF_Odes

Topic

National news — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ministry_of_defense_ua/1605419 Aug 2026, 13:36 UTC@SJTF_Odes/14902 · this entry19 Aug 2026, 16:35 UTC1.003.0 hours
@ministry_of_defense_ua/1607021 Aug 2026, 11:25 UTC@SJTF_Odes/14929 · this entry21 Aug 2026, 15:42 UTC1.004.3 hours
@ministry_of_defense_ua/1607322 Aug 2026, 08:00 UTC@SJTF_Odes/14935 · this entry24 Aug 2026, 09:47 UTC1.002 days
@ministry_of_defense_ua/1609025 Aug 2026, 14:05 UTC@SJTF_Odes/14949 · this entry25 Aug 2026, 19:16 UTC1.005.2 hours
@ministry_of_defense_ua/1604317 Aug 2026, 11:17 UTC@SJTF_Odes/14911 · this entry20 Aug 2026, 05:29 UTC0.933 days
@ministry_of_defense_ua/159926 Aug 2026, 09:07 UTC@SJTF_Odes/14724 · this entry6 Aug 2026, 14:14 UTC0.925.1 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@ministry_of_defense_ua6 (6/6 hand-verifiable sample passed)0.985.2 hours@ministry_of_defense_ua (6–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 6 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 129 comparable posts for this entry, running 4 August 2026 to 13 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_copy, last confirmed 14 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

8,6478,9378,7925 August 2026 — 8,937 subscribers6 August 2026 — 8,937 subscribers6 August 2026 — 8,936 subscribers9 August 2026 — 8,926 subscribers12 August 2026 — 8,915 subscribers16 August 2026 — 8,912 subscribers19 August 2026 — 8,911 subscribers23 August 2026 — 8,896 subscribers25 August 2026 — 8,883 subscribers29 August 2026 — 8,868 subscribers1 September 2026 — 8,855 subscribers5 September 2026 — 8,842 subscribers10 September 2026 — 8,825 subscribers14 September 2026 — 8,824 subscribers18 September 2026 — 8,796 subscribers28 September 2026 — 8,774 subscribers5 October 2026 — 8,747 subscribers12 October 2026 — 8,686 subscribers15 October 2026 — 8,684 subscribers18 October 2026 — 8,674 subscribers21 October 2026 — 8,668 subscribers24 October 2026 — 8,687 subscribers27 October 2026 — 8,681 subscribers30 October 2026 — 8,672 subscribers2 November 2026 — 8,669 subscribers5 November 2026 — 8,664 subscribers9 November 2026 — 8,647 subscribers13 November 2026 — 8,704 subscribers8,7045 August 202613 November 2026
28 measurements spanning 99 days, net -233. 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 8,604–8,981 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
13 Nov 2026, 04:108,704+57
9 Nov 2026, 04:108,647-17
5 Nov 2026, 15:008,664-5
2 Nov 2026, 13:168,669-3
30 Oct 2026, 10:068,672-9
27 Oct 2026, 13:568,681-6
24 Oct 2026, 15:558,687+19
21 Oct 2026, 19:418,668-6
18 Oct 2026, 15:268,674-10
15 Oct 2026, 09:098,684-2
12 Oct 2026, 13:578,686-61
5 Oct 2026, 19:198,747-27
28 Sept 2026, 04:568,774-22
18 Sept 2026, 18:188,796-28
14 Sept 2026, 11:428,824-1
10 Sept 2026, 13:588,825-17
5 Sept 2026, 03:208,842-13
1 Sept 2026, 13:478,855-13
29 Aug 2026, 03:578,868-15
25 Aug 2026, 22:138,883first reading

Engagement

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

ERR · 30 days
46.7%
avg views ÷ 8,704 subscribers
Avg views / post
4,060
55 posts measured
Reaction rate
0.733%
reactions ÷ views · ER floor
Posts in window
55
of 139 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 14 November 2026
Posts held139 (4 August 2026 – 14 November 2026)
Views total223,411
Reactions total1,637
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 01:33 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

Photos
≈9,110
Videos
≈1,520
Links
≈1,080

Lifetime counters from Telegram’s own channel header, read 15 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1h 14m
Average length
1m 12s

Measured directly from 62 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,047 reactions across 133 posts, in 30 distinct kinds. The most used accounts for 32.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,30632.3%
🔥1,05426.0%
🙏69417.1%
👍60514.9%
🫡992.45%
❤‍🔥761.88%
😢481.19%
💔260.642%
🥰180.445%
👏170.42%
🤝170.42%
🤬170.42%
🆒120.297%
💯110.272%
🤡100.247%
🍌50.124%
🎃50.124%
🤣50.124%
🎉40.099%
😘40.099%
10 further kinds140.346%

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

Measured over the 139 most recent posts we hold, published 4 August 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 14 of 55 posts held from the last 30 days (25.5%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 19:08 UTC431 views30 reactionsread 15 November 2026
Video

❗️Заяви росіян про нібито захоплення Воскресенки Запорізької області не відповідають дійсності. Населений пункт залишається під контролем Сил оборони України. ▫️ В Угрупованні військ «Південь» повідомили Центру, що Воскресенка перебуває більш ніж за 20 кілометрів від лінії бойового зіткнення. На підтвердження цього військовослужбовці 142-ї окремої механізованої бригади записали відео безпосередньо в населеному пункт…

🙏23👍6❤1

14 Nov 2026, 11:34 UTC582 views23 reactionsread 15 November 2026
Photo

Ми не бачимо позиції. Ми бачимо те, що з неї повертається. Пікап із пробоїнами. Двигун, який треба перебрати. Захист, який треба зварити й поставити на авто. Наземний роботизований комплекс на обслуговуванні. Болгарка, зварка — і машина знову на ходу. Ті, хто на позиції, цього боксу не бачать. Вони бачать машину, яка довезла БК туди й поранених звідти. Це моя робота в ремонтно-відновлювальному батальйоні. Матеріал…

❤19🫡3👍1

14 Nov 2026, 08:29 UTC510 views26 reactionsread 15 November 2026
Photo

Оперативна інформація на 8.00 14.11.2026 За минулу добу зафіксовано 23 бойових зіткнення. На Олександрівському напрямку ворог тричі штурмував у бік Новомиколаївки. На Гуляйпільському - окупанти 12 разів атакували позиції наших захисників. Ворог намагався просунутися біля Верхньої Терси, Малої Токмачки, Білогір’я та у бік н/п Єгорівка, Копані, Гірке. На Оріхівському - окупанти провели 8 атак у бік Новоандріївки, Ю…

❤12🙏7🔥5🤝1🫡1

14 Nov 2026, 08:29 UTC449 views16 reactionsread 15 November 2026
Photo

Оперативна інформація на 8.00 14.11.2026 За минулу добу зафіксовано 23 бойових зіткнення. На Олександрівському напрямку ворог тричі штурмував у бік Новомиколаївки. На Гуляйпільському - окупанти 12 разів атакували позиції наших захисників. Ворог намагався просунутися біля Верхньої Терси, Малої Токмачки, Білогір’я та у бік населених пунктів Єгорівка, Копані, Гірке. На Оріхівському - окупанти провели 8 атак у бік Но…

🙏11🔥5

13 Nov 2026, 16:17 UTC675 views38 reactionsread 15 November 2026
Photo

ТРАГЕДІЯ У КОМИШУВАСІ ЖАХАЄ СВОЇМ МАСШТАБОМ😥 Кількість загиблих внаслідок завданого 2-го листопада російського авіаудару по селищу Комишуваха Запорізького району зросла до 55 людей – інформує Державна служба з надзвичайних ситуацій. За даними Запорiзької ОВА, війська РФ атакували Комишуваху 2-го листопада саме в той час, коли місцеві мешканці отримували гуманітарну підтримку, спочатку скинувши керовані авіабомби ФА…

😢28💯5🙏3❤1🤬1

13 Nov 2026, 14:13 UTC510 views14 reactionsread 14 November 2026
Video

Як живуть іноземці, які служать у 141 окрумій механізованій бригаді 🇺🇦 Facebook | YouTube ✍

👍10❤4

13 Nov 2026, 10:32 UTC532 views16 reactionsread 14 November 2026
Video

Хочеш у мінометники? Чи більше до душі дрони? «Професор» — командир мінометної батареї механізованого батальйону 23 окремої механізованої бригади. Його підрозділу потрібні номери обслуг, навідники мінометів і пілоти розвідувальних дронів. Майбутні пілоти проходять навчання, а після підготовки працюють на позиціях і допомагають коригувати мінометний вогонь. Facebook | YouTube ✍

❤13🔥2👍1

13 Nov 2026, 08:10 UTC538 views21 reactionsread 14 November 2026
Photo

Оперативна інформація на 8.00 13.11.2026 За минулу добу зафіксовано 9 бойових зіткнень. На Гуляйпільському - відбито дев'ять атак загарбників у районах Тернуватого, Долинки та Білогір'я. На Оріхівському, Олександрівському та Придніпровському напрямках бойових дій не було. В операційній зоні УВ(с) "Південь" протягом доби окупанти завдали 14 авіаційних ударів із застосуванням 92 коригованих авіабомб по прифронтових…

🙏13🔥8

12 Nov 2026, 10:53 UTC658 views22 reactionsread 14 November 2026
Video

ЩОБ КОЛЕСА НЕ ПІДВЕЛИ! Для цього у 110 окремій механізованій бригаді працює власний шиномонтаж. Тут наші військові можуть безкоштовно перевзути свої автівки. У майстерні працюють досвідчені фахівці, через руки яких за день проходить по кілька машин. Заміна шин, балансування коліс, ремонт проколів — роботи вистачає! А головне, що нашим бійцям не потрібно шукати приватні шиномонтажі. Усе можна зробити на місці. Це е…

👍12🔥7🤝2🆒1

12 Nov 2026, 07:26 UTC≈2,460 views29 reactionsread 14 November 2026
Photo

Оперативна інформація на 8.00 12.11.26 За минулу добу зафіксовано 6 бойових зіткнень. На Гуляйпільському - 5 разів намагались атакувати позиції наших захисників. Ворог намагався просунутися біля Воздвижівки, Верхньої Терси, Білогір’я, Малої Токмачки та у бік Рівного. На Оріхівському - пробували один раз штурмувати наші позиції. На Олександрівському та Придніпровському - штурмових дій не було. В операційній зоні …

🙏11❤9🔥5🍌1👍1🤝1🫡1

11 Nov 2026, 16:09 UTC731 views32 reactionsread 14 November 2026
Video

Ремонт, технічне обслуговування та підготовка безпілотників - щоденна робота майстерні першого механізованого батальйону 61 окрема механізована Степова бригада 🐈 Facebook | YouTube ✍

❤22👍7💅1🤝1🆒1

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

Posts edited after publishing

@SJTF_Odes edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
6 November 2026
Most recent edit
6 November 2026

Posts recorded as deleted after publishing

We recorded 1 post on @SJTF_Odes as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
22 August 2026
Most recent seen missing
22 August 2026
Median time before seen missing
36 hours
Seen missing in the last 30 days
0

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Геннадій Труханов
@truonline · 101,479
Telegram ranks this channel #10 of 83 here — alongside 82 others — read 18 August 2026
Ігор Клименко
@KlymenkoUA_Official · 30,304
Telegram ranks this channel #17 of 91 here — alongside 90 others — read 5 September 2026
🇺🇦Олег Кіпер/Одеська ОДА (ОВА)
@odeskaODA · 38,009
Telegram ranks this channel #19 of 86 here — alongside 85 others — read 31 August 2026
🇺🇦Херcонська ОДА (ОВА)
@khersonskaODA · 20,146
Telegram ranks this channel #21 of 92 here — alongside 91 others — read 28 September 2026
Сповіщення | Новини. Одеса
@odesa_daily · 53,002
Telegram ranks this channel #29 of 79 here — alongside 78 others — read 27 August 2026
Сухопутні війська | UA Land Forces
@landforcesofukraine · 45,309
Telegram ranks this channel #33 of 94 here — alongside 93 others — read 28 August 2026
🇺🇦 Андрій Райкович/ Кіровоградська ОДА (ОВА)
@kirovogradskaODA · 64,589
Telegram ranks this channel #34 of 82 here — alongside 81 others — read 21 August 2026
🇺🇦Сергій Тюрін, голова Хмельницької ОДА (ОВА)
@khmelnytskaODA · 19,072
Telegram ranks this channel #35 of 86 here — alongside 85 others — read 4 October 2026
Пульс Одессы
@Odessaonduty1 · 52,949
Telegram ranks this channel #36 of 84 here — alongside 83 others — read 14 September 2026
ДПСУ | Держприкордонслужба
@DPSUkr · 57,646
Telegram ranks this channel #39 of 94 here — alongside 93 others — read 22 August 2026
Одеса. Офіційно
@odesacityofficial · 81,469
Telegram ranks this channel #44 of 84 here — alongside 83 others — read 18 August 2026
Координаційний штаб з питань поводження з військовополоненими
@Koord_shtab · 41,207
Telegram ranks this channel #46 of 85 here — alongside 84 others — read 29 August 2026
Командування Повітряних Сил
@ComAFUA · 20,678
Telegram ranks this channel #52 of 85 here — alongside 84 others — read 25 September 2026
СтратКом ЗСУ / AFU StratCom
@AFUStratCom · 52,393
Telegram ranks this channel #52 of 92 here — alongside 91 others — read 24 August 2026
Полтава ⚡️Новини
@poltava_insider · 21,902
Telegram ranks this channel #61 of 84 here — alongside 83 others — read 20 September 2026
Очаків Online
@ochakivonline · 28,484
Telegram ranks this channel #62 of 73 here — alongside 72 others — read 10 September 2026
Суспільне Одеса
@suspilneodesa · 46,713
Telegram ranks this channel #63 of 88 here — alongside 87 others — read 26 August 2026
Чернігів ⚡️Новини
@chernihiv_insider · 23,185
Telegram ranks this channel #64 of 85 here — alongside 84 others — read 18 September 2026
Сєнкевич Online
@senkevichonline · 67,166
Telegram ranks this channel #64 of 91 here — alongside 90 others — read 21 August 2026
🇺🇦Онищук Світлана / Івано-Франківська ОДА (ОВА)
@onyshchuksvitlana · 21,376
Telegram ranks this channel #65 of 93 here — alongside 92 others — read 30 September 2026
Михайло Семікін - Запорізька ОВА
@zoda_gov_ua · 33,202
Telegram ranks this channel #65 of 87 here — alongside 86 others — read 7 September 2026
Десантно-штурмові війська ЗС України
@ua_dshv · 35,158
Telegram ranks this channel #65 of 93 here — alongside 92 others — read 2 September 2026
🇺🇦 Іван Федоров | Рада Оборони Запорізької обл.
@ivan_fedorov_zp · 52,316
Telegram ranks this channel #66 of 91 here — alongside 90 others — read 22 August 2026
МОСТ: ХЕРСОН
@mostks · 22,518
Telegram ranks this channel #67 of 88 here — alongside 87 others — read 21 September 2026

This channel appears in 35 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q130375 on Wikidata, read 8 November 2026
LabelOperational Command South
Descriptionformation of the Ukrainian Ground Forces in the southern part of Ukraine

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Оперативно-тактичне угруповання «Запоріжжя» (uk.wikipedia.org)
“…[[Привільне (Комарська сільська громада)|Привільне]].{{Cite web |url=https://t.me/SJTF_Odes/12255 |title=Карта ОУв «Таврія» |website=Telegram |access-date=2025-03-25}}…”
read 1 November 2026

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

“Угруповання військ (сил) "Південь"” (@SJTF_Odes), 8,704 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/SJTF_Odes.

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.