Other / unclassifiable — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
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 word for word on 12 other registered channels. They sit inside a group of 377 channels that share the same post bodies with each other. 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)
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 189 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 3,209 comparable posts for this entry, running 14 April 2026 to 7 August 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).
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
Views and reactions moved apart
On 5 of the 173 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0129 reactions per view.
Each interval, as we read it — views and reactions before and after
Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_copy · clone_mutual · clone_source · view_reaction_decoupling, last confirmed 12 August 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
326 more channels are in this same group but not listed individually here.
Growth
8 measurements spanning 6 days, net -2,292. 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 1,163,184–1,166,190 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 11:44
1,163,531
-287
11 Aug 2026, 11:57
1,163,818
-363
10 Aug 2026, 08:53
1,164,181
-181
9 Aug 2026, 07:11
1,164,362
-88
8 Aug 2026, 08:27
1,164,450
-569
7 Aug 2026, 06:17
1,165,019
-824
6 Aug 2026, 03:20
1,165,843
+20
6 Aug 2026, 00:41
1,165,823
first reading
Engagement
3,633 posts held, back to 14 April 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 297 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
9.19%
avg views ÷ 1,163,531 subscribers
Avg views / post
107,000
805 posts measured
Reaction rate
1.34%
reactions ÷ views · ER floor
Posts in window
809
of 3,633 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
Window
Rolling 30 days · latest post in window 12 August 2026
Posts held
3,633 (14 April 2026 – 12 August 2026)
Views total
86,067,100
Reactions total
1,153,753
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 20:21 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
≈43,700
Videos
≈26,900
Links
≈54,600
Lifetime counters from Telegram’s own channel header, read 12 August 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 37m
Average length
1m 36s
Measured directly from 61 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 175 of this channel’s own posts over the last 30 days: across 147of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.1 hours of being posted; a typical post has already reached 27.5% of its 24-hour view count within the first hour, and 70.7% within the first six; the median 24-hour reach across those posts is 86,500 views — 7.43% of this channel’s own subscriber count (90th percentile 101,000).
8 most recently posted, with a view-velocity reading
60 minutes: 19,365 interp. → 3.0 hours: 38,600still climbing at last reading
not yet at 24h
85 minutesprovisional — final view count still climbing
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Reaction mix
231,051 reactions across 184 posts, in 14 distinct kinds. The most used accounts for 20.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
46,338
20.1%
🤬
37,759
16.3%
🙏
36,419
15.8%
💯
28,132
12.2%
❤
26,396
11.4%
😁
21,781
9.43%
🔥
20,340
8.80%
👎
6,955
3.01%
🤔
3,215
1.39%
😢
1,269
0.549%
😱
860
0.372%
❤🔥
726
0.314%
🕊
538
0.233%
🫡
323
0.14%
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 994 of the 1,000 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 1,396,724reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 7 July 2026 to 12 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.
Telegram Stars
Stars received
153
across the posts below
Posts paid on
54
of 994 we hold a reading for · 5%
Most on one post
53
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dva_majors. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 7 July 2026 to 12 August 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.
Advertising
Ad load
0.5%
5 of 1,000 posts carry an ad marker
Regulatory tokens
5
posts carrying an erid · 5 distinct tokens
Median views · ads
88,800
over 5 measured posts
Median views · rest
97,600
over 989 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2VSb5xuBQCS
1
22 July 2026
22 July 2026
2VtzqxAeDoH
1
12 August 2026
12 August 2026
2W5zFGNSKSy
1
4 August 2026
4 August 2026
2W5zFHvqsYd
1
15 July 2026
15 July 2026
2W5zFK33CpZ
1
21 July 2026
21 July 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 7 July 2026 to 12 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
🇺🇸🔓США пытаются повысить защиту от дронов сухопутных войск
Пентагон приобретает у компании Vertex Modernization and Sustainment LLC (штат Индиана) 10 ЗРК ближнего радиуса действия Tempest.
Они обойдутся в 19 млн долларов (или 1,9 млн за единицу ‼️). Платформа представляет собой ю багги Can-Am Maverick X3 (лёгкий 4×4 side-by-side), на который установлены пусковые установки для двух ракет AGM-114L Longbow Hellfire (а…
✨Сбор на Фронтовую броню ✨
578 человек участвовали в сборе за сутки
Народный проект Фронтовая броня нуждается в поддержке!
Все расходные материалы закупаются только за счет народных средств.
Необходима сталь для производства бронекомплектов на военные машины!
Необходимо: 3 000 000 ₽
Собрано за сутки: 188 449 ₽
Собрано всего: 1 137 881 ₽
Осталось собрать: 1 862 119 ₽
—
Реквизиты для добровольных пожертвований:
✔️л…
Краматорское направление
Бойцы взвода БПЛА 255-го мотострелкового полка делятся кадрами из своего фронтового быта.
В перерывах между боевой работой операторы продолжают тренироваться прямо в блиндаже. На специальных компьютерных симуляторах они отрабатывают управление FPV-дронами, сложные манёвры и действия в различных условиях.
✨ За пультом — один из самых опытных и результативных операторов подразделения. Но даж…
🇺🇦 Хохлы раскрыли название своего шахедопободного дрона.
Беспилотник ранее опознанный как Batyar-S имеет название MICH 2000 и был создан на базе китайского дрона ZTK-150. Об этом рассказывает украинский ресурс, публицист которого побывал на заводе производителя.
Сообщается, что в конце 2023 году хохлы поехали в Китай с целью купить дальнобойные дроны. На тот момент Китай уже официально ограничил экспорт дронов, но …
Славянское направление
Операторы БПЛА Южного военного округа делятся кадрами боевой работы в пригороде Славянска.
✨ На кадрах наш FPV-дрон на оптоволокне преследует квадроцикл, на котором передвигались трое военнослужащих противника. Скорость и попытки уйти от погони им не помогли: оператор настиг цель и нанёс огневое поражение.
Два майора ✨ Два майора в МАХ
Рубрика «Будни солдата».
—
Фронтовики, можете присылать нам фотографии/видео вашего быта: @media_front_bot, и мы их опубликуем (и отредактируем).
Два майора ✨ Два майора в МАХ
Благодаря поддержке читателей канала из резервных средств нашего фонда удалось помочь бойцам 35 ОА в приобретении пикапа на Запорожское направление.
Спасибо всем, кто не остается в стороне и помогает фронту!
Всё для Победы! 🇷🇺
⭐️ Ссылка на актуальный сбор:
https://t.me/dva_majors/97006
—
БФ Два майора
🇷🇴☢️Румыния из-за падения уровня Дуная остановила АЭС
В связи с невозможностью обеспечить водное охлаждение в четверг будет остановлен второй реактор Чернаводской АЭС. В результате Румыния останется без 20% собственной энергогенерации.
Не помог подрыв скал и затопление барж с камнями для перераспределения течения в сторону станции. Ситуация может затянуться минимум на несколько недель.
Теперь придётся закупать эле…
Великобурлукское направление
Операторы БПЛА 2-го батальона 1-го мотострелкового полка РВСН вновь делятся кадрами своей боевой работы.
В ходе ведения воздушной разведки бойцы выявили бронетехнику противника. После подтверждения цели по ней было нанесено огневое поражение.
⭐️ Ссылка на актуальный сбор для этих бойцов:
https://t.me/dva_majors/97374
Два майора ✨ Два майора в МАХ
Яндекс не нашелся
Приложение Ozon Банка исчезло из Google Play. Уже установленные версии продолжают работать. Банк подтвердил, что операции внутри России не затронуты, средства клиентов в безопасности. Скачать приложение заново через Google Play невозможно, только файлом АПК или с Русторе
А еще ночью из российского сегмента App Store удалили «Яндекс Пэй». Ранее приложение уже было убрано из зарубежных версий магази…
👍329💯253😁134❤65🤔57🙏8👎7🕊7
Showing the 12 most recent of 3,633 posts we hold for @dva_majors. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@dva_majors edited 5 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
8 August 2026
Most recent edit
12 August 2026
Citation-graph rank
Citation-graph rank — 149 of 1,084,084entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 378 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.
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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@dva_majors named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@church_peter_and_paul_in_ovsorok named in 1 post, 8 August 2026 – 8 August 2026
@rian_ru named in 1 post, 8 August 2026 – 8 August 2026
Domains linked from posts
43 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 August 2026 — this
entry's latest reading, not the date you are reading this.
“Два майора” (@dva_majors), 1,163,531 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dva_majors.
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.
