Telegram RegisterThe public register of Telegram
Telegram profile photo for 1 Окремий центр БпС

Channel

1 Окремий центр БпС

@army_1usc

Not marked by Telegram, checked 4 September 2026

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

14,756subscribers

+34 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002249761859
TypeChannel
Username@army_1usc
Description1 Окремий центр БпС СБС ЗСУ Контакт для співпраці: @media_1usc Наші єдині офіційні мережі: https://1usc.army facebook.com/1USC.ARMY instagram.com/1usc.army x.com/1usc_army
Created19 July 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/army_1usc

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 15 August 2026 and assigned it the closest of 31 fixed categories, at 36% 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. This entry also forms a group of 2 channels linked by matching posts. 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@army_1usc/1497 · this entry13 Nov 2026, 13:01 UTC@vanek_nikolaev_ukr/2691313 Nov 2026, 13:09 UTC1.008 minutes
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
@vanek_nikolaev_ukr5 (5/5 hand-verifiable sample passed)1.0016 minutesthis entry (4–1)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 62 comparable posts for this entry, running 29 July 2026 to 16 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @usf_army. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 17 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

14,72014,99514,857.514,7566 August 202615 November 2026
64 measurements spanning 101 days, net +34. 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 14,679–15,036 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
15 Nov 2026, 07:4514,756+5
12 Nov 2026, 01:5914,751-18
10 Nov 2026, 01:0014,769-13
8 Nov 2026, 16:4014,782-10
7 Nov 2026, 08:4014,792-16
6 Nov 2026, 11:4714,808-10
5 Nov 2026, 12:1014,818-5
4 Nov 2026, 10:3614,823-17
3 Nov 2026, 07:0814,840-8
2 Nov 2026, 06:0614,848-6
1 Nov 2026, 04:2014,854-15
31 Oct 2026, 01:5714,869-7
29 Oct 2026, 23:4914,876-22
29 Oct 2026, 01:0114,898-1
28 Oct 2026, 00:4814,899-14
27 Oct 2026, 02:0714,913-5
25 Oct 2026, 23:3014,918+2
24 Oct 2026, 21:1014,916+58
23 Oct 2026, 21:5814,858-5
22 Oct 2026, 21:5014,863first reading

Engagement

68 posts held, back to 29 July 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 82 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
60.7%
avg views ÷ 14,756 subscribers
Avg views / post
8,950
19 posts measured
Reaction rate
1.75%
reactions ÷ views · ER floor
Posts in window
19
of 68 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 16 November 2026
Posts held68 (29 July 2026 – 16 November 2026)
Views total170,070
Reactions total2,976
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 07:59 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
916
Videos
407
Links
656

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
37m 08s
Average length
1m 12s

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

12,804 reactions across 67 posts, in 13 distinct kinds. The most used accounts for 53.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6,87453.7%
❤3,85830.1%
🫡8967.00%
👍8666.76%
😢1331.04%
👏800.625%
🎉300.234%
🤝200.156%
😎150.117%
🤣120.094%
💯90.07%
🤬80.062%
😁30.023%

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

Measured over the 68 most recent posts we hold, published 29 July 2026 to 16 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 68 we hold a reading for · 4%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @army_1usc. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 68 most recent posts we hold for this entry, published 29 July 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 19 posts held from the last 30 days (15.8%) 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).

16 Nov 2026, 17:00 UTC≈2,230 views153 reactionsread 17 November 2026
Video

100% готовності. 100% результату😎 😎Facebook 🕊Instagram 📹YouTube 👥X.com 🔗Вакансії в 1 ОЦ БпС СБС

❤94🔥47👏7🫡4🤬1

16 Nov 2026, 12:31 UTC≈2,310 views153 reactionsread 17 November 2026
Forwarded from @usf_armyPhoto

🔥 СБС знову уразили Ільський НПЗ У ніч з 15 на 16 листопада оператори 1-го окремого центру БпС та 412-ї окремої бригади Nemesis у взаємодії з ГУР МОУ та іншими складовими Сил оборони Українив уразили Ільський нафтопереробний завод у Краснодарському краї рф. Ільський НПЗ — одне з найбільших нафтопереробних підприємств півдня росії. Потужність заводу становить близько 6,6 млн тонн нафти на рік. Підприємство виробляє …

🔥129❤16👍7🎉1

15 Nov 2026, 12:47 UTC≈2,530 views186 reactionsread 17 November 2026
Forwarded from @usf_armyVideo

🔥 СБС уразили два стратегічні об’єкти в Нижньокамську У ніч на 15 листопада оператори 1-го окремого центру безпілотних систем та 414-ї окремої бригади безпілотних систем «Птахи Мадяра» у взаємодії з ССО, ГУР МО України, СБУ та іншими складовими Сил оборони України уразили нафтопереробний завод «ТАИФ-НК» у Нижньокамську, Республіка Татарстан, рф. Підприємство є важливою частиною російської нафтопереробної інфраструк…

🔥151❤26👍8🤝1

13 Nov 2026, 15:03 UTC≈3,650 views228 reactionsread 17 November 2026
Video

Волгоградський НПЗ: ми повернулися 😎 У ніч на 13 листопада 1 Окремий центр безпілотних систем разом із побратимами з 414-ї окремої бригади безпілотних систем «Птахи Мадяра», ССО, ГУР МОУ, ДПСУ та іншими складовими Сил оборони знову уразили НПЗ «Лукойл-Волгограднефтепереработка». Це вже не перше ураження цього об’єкта. Ми продовжуємо системно вибивати паливну інфраструктуру ворога, на якій тримається війна проти Укр…

🔥176🫡25❤21👍5🎉1

13 Nov 2026, 13:01 UTC≈2,590 views163 reactionsread 17 November 2026
Forwarded from @usf_armyVideo

💥 СБС знову уразили один із найбільших НПЗ росії У ніч на 13 листопада оператори 1-го окремого центру безпілотних систем та 414-ї окремої бригади безпілотних систем «Птахи Мадяра» у взаємодії з ССО, ГУР МОУ, ДПСУ та іншими складовими Сил оборони України уразили нафтопереробний завод «Лукойл-Волгограднефтепереработка» у Волгограді. Це один із десяти найбільших НПЗ росії та найбільший виробник нафтопродуктів на півдн…

🔥135❤22👏5🫡1

12 Nov 2026, 17:03 UTC≈3,820 views125 reactionsread 17 November 2026
Photo

⁨⁨Мали честь провести спільний захід із представниками молодіжної спільноти. Для нас це важливий крок в системній взаємодії із молоддю. Ми зацікавлені в тому, щоб розповідати про те, як працюють сучасні технології на війні, та залучати до цієї теми тих, хто прагне розвиватися у сфері технологій і оборони України. Служба в 1 Окремому центрі безпілотних систем – це не лише твій внесок у виснаження ворога. Це можливіст…

❤82🔥25👍15😁2🤣1

11 Nov 2026, 09:01 UTC≈3,490 views113 reactionsread 17 November 2026
Photo

Подобається, як палають ворожі об’єкти? Підкинь жару – ставай амбасадором палкого удару! Відкривай дружню банку на підтримку мегазбору «Лінія горизонту» на 15 млн грн і перетворюй свій вплив на реальний результат. Умови та подарунки: • Від 10 000 грн – постер А3 з особистим підписом командира Чарлі. • Від 30 000 грн – великий постер А2 з підписом командира Чарлі. • Від 50 000 грн – сертифікат на «привітання» ворогу…

❤85👍24🔥4

10 Nov 2026, 17:00 UTC≈3,780 views136 reactionsread 17 November 2026

Як наші далекобійні удари вглиб території росії впливають на лінію фронту Систематичні глибинні удари 1 Окремого центру безпілотних систем по об'єктах ВПК змушують вороже командування розтягувати сили. Щоб прикрити НПЗ чи танкери, росіяни знімають з передової елітні дронові підрозділи та системи ППО. Елітні екіпажі БпЛА (зокрема «Рубікон»), фахівці ППО та РЕБ залишають важливі напрямки, щоб охороняти кораблі в морі…

👍81🔥39❤12👏4

9 Nov 2026, 10:38 UTC≈3,980 views233 reactionsread 17 November 2026
Forwarded from @usf_armyPhoto

🔥 СБС уразили виробництво палива для «Іскандерів» У ніч на 9 листопада оператори 1-го окремого центру безпілотних систем СБС у взаємодії з іншими складовими Сил оборони України уразили завод імені Морозова в Ленінградській області рф. Це не просто завод вибухових речовин – підприємство є однією з ланок виробничого ланцюга російських «Іскандерів». Тут виготовляють твердопаливні заряди для двигунів балістичних ракет …

🔥184👍26❤23

8 Nov 2026, 11:24 UTC≈4,110 views200 reactionsread 17 November 2026
Photo

З Днем Десантно-штурмових військ ЗСУ! Завжди перші. На найгарячіших напрямках, у найважчих боях, там, де вирішується доля лінії фронту. 1 Окремий центр безпілотних систем вітає воїнів ДШВ із професійним святом! Дякуємо за силу, мужність та невиправний драйв у знищенні ворога. Честь бути пліч-о-пліч у цій боротьбі🫡 😎Facebook 🕊Instagram 📹YouTube 👥X.com 🔗Вакансії в 1 ОЦ БпС СБС

❤144🔥37🫡19

6 Nov 2026, 17:02 UTC≈4,610 views165 reactionsread 17 November 2026
Video

Наша рутина, про яку не розкажеш у двох словах😎 😎Facebook 🕊Instagram 📹YouTube 👥X.com 🔗Вакансії в 1 ОЦ БпС СБС

❤118🫡31🔥16

4 Nov 2026, 17:01 UTC≈107,000 views192 reactionsread 17 November 2026
Video

Кожен вибух у глибокому тилу ворога ‒ це результат системної роботи наших бійців. Яскраві кадри уражень ‒ лише вершина айсберга.Кожна Deep Strike місія вимагає планування, аналізу даних, розвідки, складної логістики та злагоджених дій десятків фахівців різних підрозділів. Ми ‒ 1 Окремий центр безпілотних систем. Наша головна сила ‒ це вивірена система, де кожен спеціаліст досконало виконує свою роль. Разом із підро…

🔥148❤27👍12🫡5

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

@army_1usc edited 2 posts 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
24 August 2026
Most recent edit
5 November 2026

Forward network

Republished by

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

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 49 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Сили безпілотних систем ЗС України
@usf_army · 33,415
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“1 Окремий центр БпС” (@army_1usc), 14,756 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/army_1usc.

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.