ВС России сегодня бьют по Северному мосту в Киеве. ⚡️Два майора ⭐️Два майора в МАХ
🔥475👍148👎36🤬27❤22😁12🤔6😱2

Channel
@dva_majors
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
1,160,870subscribers
-4,953 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001513431778 |
|---|---|
| Type | Channel |
| Username | @dva_majors |
| Description | @major_adv - Реклама @dvamajorsbot - майоры РАЗБАН @TA57_Razban_bot Гумка @front_narod_bot Побег из 404: @Evacfrom404bot Цели: @dva_majors_ND2_bot https://knd.gov.ru/license?id=67514612c577eb7c524f17fa®istryType=bloggersPermission |
| Created | 26 June 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/dva_majors |
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 the other topics.
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.
Posts published here appear in near-verbatim form on 12 other registered channels. This entry also sits inside a group of 42 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @rybar/7960418 Apr 2026, 20:02 UTC | @dva_majors/91578 · this entry19 Apr 2026, 06:09 UTC | 1.00 | 10 hours |
| @rybar/7985028 Apr 2026, 06:20 UTC | @dva_majors/92140 · this entry28 Apr 2026, 14:34 UTC | 1.00 | 8.2 hours |
| @dva_majors/92577 · this entry7 May 2026, 03:22 UTC | @rybar/800717 May 2026, 05:29 UTC | 1.00 | 2.1 hours |
| @rybar/809148 Jun 2026, 20:34 UTC | @dva_majors/94271 · this entry9 Jun 2026, 06:01 UTC | 1.00 | 9.5 hours |
| @dva_majors/95608 · this entry4 Jul 2026, 04:13 UTC | @rybar/815064 Jul 2026, 06:08 UTC | 1.00 | 1.9 hours |
| @dva_majors/91759 · this entry22 Apr 2026, 10:27 UTC | @arx_spn/2926522 Apr 2026, 10:45 UTC | 1.00 | 17 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @rybar | 390 (8/8 hand-verifiable sample passed) | 1.00 | 2.9 hours | @rybar (248–142) |
| @arx_spn | 95 (8/8 hand-verifiable sample passed) | 1.00 | 2.7 hours | @arx_spn (52–43) |
| @swodki | 34 (8/8 hand-verifiable sample passed) | 0.98 | 2.1 hours | this entry (34–0) |
| @designersmil | 28 (8/8 hand-verifiable sample passed) | 0.99 | 56 minutes | @designersmil (26–2) |
| @SIL0VIKI | 58 (8/8 hand-verifiable sample passed) | 1.00 | 23 minutes | this entry (38–20) |
| @chvkmedia | 42 (8/8 hand-verifiable sample passed) | 1.00 | 23 minutes | this entry (28–14) |
| @front_narod | 66 (8/8 hand-verifiable sample passed) | 1.00 | 15 minutes | this entry (54–12) |
| @SVOhronika | 18 (8/8 hand-verifiable sample passed) | 1.00 | 28 minutes | this entry (16–2) |
| @natoptishh | 9 (8/8 hand-verifiable sample passed) | 1.00 | 15 minutes | @natoptishh (9–0) |
| @voenkor23 | 9 (8/8 hand-verifiable sample passed) | 1.00 | 5.0 hours | @voenkor23 (7–2) |
| @rvvoenkor | 13 (8/8 hand-verifiable sample passed) | 1.00 | 7.6 hours | @rvvoenkor (7–6) |
| @solovievlive | 14 (8/8 hand-verifiable sample passed) | 1.00 | 19 minutes | this entry (8–6) |
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. 38 of the 233 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 5,712 comparable posts for this entry, running 14 April 2026 to 15 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.
Of the group of 42 channels, the one whose matching posts we hold earliest is @rybar. That is a statement about our reading window, not a claim of authorship.
On 23 of the 919 posts we watched over 30 days, 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.0126 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /10131330 Oct 2026, 20:16 UTC | 30 minutes | 41,900 → 48,500at least +6,500 | 340 → 356at most +17 | +81.8 |
| /10131330 Oct 2026, 20:16 UTC | 55 minutes | 48,500 → 59,400at least +10,800 | 356 → 379at most +24 | +135.9 |
| /1015124 Nov 2026, 07:31 UTC | 34 minutes | 41,700 → 51,900at least +10,100 | 506 → 532at most +27 | +127.1 |
| /1015124 Nov 2026, 07:31 UTC | 30 minutes | 51,900 → 59,800at least +7,800 | 532 → 552at most +21 | +98.1 |
| /1016136 Nov 2026, 07:31 UTC | 34 minutes | 36,300 → 46,600at least +10,200 | 350 → 374at most +25 | +128.3 |
| /1016136 Nov 2026, 07:31 UTC | 35 minutes | 46,600 → 54,800at least +8,100 | 374 → 393at most +20 | +101.9 |
| /10183511 Nov 2026, 07:29 UTC | 35 minutes | 37,200 → 45,500at least +8,200 | 368 → 384at most +17 | +103.2 |
| /10183511 Nov 2026, 07:29 UTC | 35 minutes | 45,500 → 52,900at least +7,300 | 384 → 399at most +16 | +91.8 |
| /10194513 Nov 2026, 07:29 UTC | 35 minutes | 37,300 → 44,600at least +7,200 | 392 → 406at most +15 | +90.6 |
| /10194513 Nov 2026, 07:29 UTC | 1.7 hours | 44,600 → 64,300at least +19,600 | 406 → 446at most +41 | +246.6 |
| /10071420 Oct 2026, 06:35 UTC | 26 hours | 78,700 → 125,000at least +45,300 | 1,229 → 1,327at most +108 | +570.0 |
| /10098725 Oct 2026, 12:58 UTC | 51 minutes | 67,800 → 85,400at least +17,500 | 868 → 917at most +50 | +220.2 |
| /10102226 Oct 2026, 04:19 UTC | 34 minutes | 69,600 → 110,000at least +39,400 | 489 → 567at most +79 | +495.7 |
| /10121729 Oct 2026, 12:12 UTC | 60 minutes | 82,100 → 152,000at least +68,900 | 641 → 752at most +112 | +866.9 |
| /10132731 Oct 2026, 07:30 UTC | 2.8 hours | 50,600 → 139,000at least +87,400 | 764 → 840at most +77 | +1099.7 |
Expected is 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 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.
This channel is in a group of 42 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 15:16 | 1,160,870 | -632 |
| 13 Nov 2026, 01:20 | 1,161,502 | -452 |
| 10 Nov 2026, 16:16 | 1,161,954 | -357 |
| 9 Nov 2026, 02:55 | 1,162,311 | -158 |
| 7 Nov 2026, 20:09 | 1,162,469 | -244 |
| 6 Nov 2026, 20:20 | 1,162,713 | -195 |
| 5 Nov 2026, 18:40 | 1,162,908 | -137 |
| 4 Nov 2026, 15:17 | 1,163,045 | -33 |
| 3 Nov 2026, 15:27 | 1,163,078 | -113 |
| 2 Nov 2026, 17:00 | 1,163,191 | -139 |
| 1 Nov 2026, 15:00 | 1,163,330 | -159 |
| 31 Oct 2026, 11:49 | 1,163,489 | -169 |
| 30 Oct 2026, 09:47 | 1,163,658 | -113 |
| 29 Oct 2026, 09:20 | 1,163,771 | -319 |
| 28 Oct 2026, 05:00 | 1,164,090 | -216 |
| 27 Oct 2026, 06:26 | 1,164,306 | -147 |
| 26 Oct 2026, 07:20 | 1,164,453 | -248 |
| 25 Oct 2026, 05:38 | 1,164,701 | -84 |
| 24 Oct 2026, 04:18 | 1,164,785 | -115 |
| 23 Oct 2026, 05:18 | 1,164,900 | first reading |
6,505 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 489 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 6,505 (14 April 2026 – 16 November 2026) |
| Views total | 78,026,000 |
| Reactions total | 920,622 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 03:00 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.
Lifetime counters from Telegram’s own channel header, read 16 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.
Measured directly from 368 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.
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 919 of this channel’s own posts over the last 30 days (2 of the 24-hour readings behind this are interpolated, not measured directly): across 883 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.0 hours of being posted; a typical post has already reached 29.8% of its 24-hour view count within the first hour, and 71.2% within the first six; the median 24-hour reach across those posts is 67,900 views — 5.85% of this channel’s own subscriber count (90th percentile 85,280).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /10212816 Nov 2026, 23:33 UTC | 627 minutes – 3.5 hours old | 26,800 views ~731 reactions | 60 minutes: 10,376 interp. → 3.0 hours: 22,200still climbing at last reading | not yet at 24h | 89 minutesprovisional — final view count still climbing |
| /10212716 Nov 2026, 23:15 UTC | 710 minutes – 3.8 hours old | 26,700 views ~636 reactions | 60 minutes: 10,671 interp. → 3.0 hours: 21,036 interp.still climbing at last reading | not yet at 24h | 1.5 hoursprovisional — final view count still climbing |
| /10212616 Nov 2026, 20:02 UTC | 1128 minutes – 7.0 hours old | 50,200 views ~648 reactions | 60 minutes: 16,945 interp. → 3.0 hours: 29,416 interp. → 6.0 hours: 44,100still climbing at last reading | not yet at 24h | 2.2 hoursprovisional — final view count still climbing |
| /10212516 Nov 2026, 19:51 UTC | 124 minutes – 7.1 hours old | 49,300 views ~274 reactions | 60 minutes: 17,928 interp. → 3.0 hours: 30,000 → 6.0 hours: 43,600still climbing at last reading | not yet at 24h | 1.9 hoursprovisional — final view count still climbing |
| /10212116 Nov 2026, 19:03 UTC | 1323 minutes – 8.0 hours old | 50,700 views ~794 reactions | 60 minutes: 22,200 interp. → 3.0 hours: 35,891 interp. → 6.0 hours: 44,700still climbing at last reading | not yet at 24h | 76 minutesprovisional — final view count still climbing |
| /10212016 Nov 2026, 18:45 UTC | 1340 minutes – 8.3 hours old | 53,100 views ~433 reactions | 60 minutes: 23,306 interp. → 3.0 hours: 37,927 interp. → 6.0 hours: 47,100still climbing at last reading | not yet at 24h | 74 minutesprovisional — final view count still climbing |
| /10211916 Nov 2026, 16:31 UTC | 174 minutes – 10 hours old | 86,200 views ~1,318 reactions | 60 minutes: 36,794 interp. → 3.0 hours: 63,100 → 6.0 hours: 77,200still climbing at last reading | not yet at 24h | 80 minutesprovisional — final view count still climbing |
| /10211816 Nov 2026, 16:25 UTC | 1710 minutes – 11 hours old | 51,000 views ~965 reactions | 60 minutes: 19,450 interp. → 3.0 hours: 35,900 → 6.0 hours: 45,000still climbing at last reading | not yet at 24h | 1.6 hoursprovisional — 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 views is 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.
1,010,980 reactions across 998 posts, in 14 distinct kinds. The most used accounts for 17.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 176,130 | 17.4% | |
| 🤬 | 165,502 | 16.4% | |
| 🙏 | 153,647 | 15.2% | |
| 💯 | 127,098 | 12.6% | |
| ❤ | 102,263 | 10.1% | |
| 😁 | 100,813 | 9.97% | |
| 🔥 | 99,080 | 9.80% | |
| 👎 | 41,159 | 4.07% | |
| 🤔 | 22,330 | 2.21% | |
| ❤🔥 | 7,645 | 0.756% | |
| 😢 | 5,940 | 0.588% | |
| 😱 | 4,246 | 0.42% | |
| 🫡 | 2,898 | 0.287% | |
| 🕊 | 2,229 | 0.22% |
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 998 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,010,980 reactions 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 15 October 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.
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 15 October 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.
Telegram’s own ‘edited’ marker: 149 of 921 posts held from the last 30 days (16.2%) 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).
ВС России сегодня бьют по Северному мосту в Киеве. ⚡️Два майора ⭐️Два майора в МАХ
🔥475👍148👎36🤬27❤22😁12🤔6😱2
Противник вновь атаковал Крымский мост. На данный момент движение транспорта приостановлено. Просим жителей и гостей Крыма воздержаться от поездок в направлении моста и учитывать ограничения при планировании маршрутов. О развитии ситуации сообщим дополнительно. Напоминаю о необходимости доверять только официальным источникам информации.
🙏302🤬134🔥78😁70👍15😱12❤9❤🔥9
Кот дело говорит. ⚡️Два майора ⭐️Два майора в МАХ
❤412👍117👎38❤🔥35💯25😁6🙏6🕊4
✨Сбор на Запорожский фронт✨ 459 человек участвовали в сборе за сутки ⚡️ Десантникам необходима народная поддержка для дооснащения цеха БПЛА и обеспечения его бесперебойным электроснабжением. ▪️Эл.станц. -4шт- 1 000 000 ₽ ▪️Генератор -2шт- 600 000 ₽ ▪️Станки для опты -2шт- 700 000 ₽ ▪️Оборуд. FPV - 450 000 ₽ Необходимо: 2 750 000 ₽ Собрано за сутки: 105 799 ₽ Собрано всего: 1 354 785 ₽ Осталось собрать: 1 395 215 ₽…
🙏185👎45❤19👍10😁9🕊4🤬1😱1
🇧🇬🚢Напротив Болгарии затонул сухогруз В Чёрном море в 74 км юго-восточнее болгарского мыса Калиакра опрокинулся сухогруз BETUL 8 под флагом Сомали. Он вёз по документам 3000 тыс тонн пшеницы из румынской 🇷🇴Тулчи в 🇪🇬Египет. По словам эвакуированных моряков, судно утром атаковали два морских дрона-камикадзе. Ранее, премьер-министр Болгарии Румен Радев заявил, что страна не готова брать на себя новые расходы на помо…
🔥443👍106💯102❤48🤔33🤬25👎20😁13
Сумское направление Наши фронтовики передают слова благодарности нашему товарищу, известному боевому медику Доктору Хилеру и его команде за переданный медицинский рюкзак. ✨ Хилер и его команда уже не первый год помогают бойцам на фронте. Помимо обучения тактической медицине, они регулярно обеспечивают подразделения индивидуальными аптечками, медицинскими рюкзаками и необходимыми расходными материалами. В зоне боев…
👍186🙏135❤48👎48😁12🕊2🤬2
✨В контексте продолжающихся последствий от ударов БПЛА на важных объектах нашей страны, в очередной раз затронем тему организации ПВО✨ Так уж случилось, что на пятый год войны выяснилось, что в стране нет единой системы ПВО (даже нет единого командования в этой сфере). Это привело к тому, что подразделения ПВО сухопутных войск и ВКС России, в первую очередь готовившихся для защиты войск на марше, военных объектов и …
💯896👍146❤123😁99🤬17👎13😢9🔥8
Движение автомобильного транспорта по Крымскому мосту запущено в реверсивном режиме, ограничений движения поездов нет. Вместе с Заместителем Председателя Правительства Российской Федерации Маратом Шакирзяновичем Хуснуллиным, представителями профильных структур выезжал на место. В ходе совещания обсудили вопросы, связанные с устранением последствий вражеской атаки. Что и как нужно делать, понятно, необходимые ресурс…
🙏647😁144❤58👍48🤔26👎23🤬7🔥6
Видео из Украины начали поступать Чтобы сохранить конфиденциальность отправителей, мы показываем не оригиналы, а 3 видео, сгенерированных ИИ. За настоящие записи люди уже получили реальные деньги. Увидите что-то подобное, присылайте! @Content_bpla_bot
👍321👎87😁42❤23🔥9🤬4😱4🤔3
«Молния-ПВО» защищает ночное небо над Калугой Расчеты российских дронов-перехватчиков «Молния-ПВО» отработали сегодня ночью по вражеским БВС. Защита калужского неба велась в режиме автоматического распознавания и захвата воздушных целей. ⚡️Два майора ⭐️Два майора в МАХ
🙏543🔥103👍59👎50😁26❤24🤔6🕊1
💬О молодых некрепких умах💬 Вот мальчик Слава, захотел вступить в ГУР, но к нему и его родителям пришел товарищ майор. Большинство нашей аудитории — 30+ и почти у всех уже есть дети: Славики, Маринки, Ваньки, Петьки и все остальные. Разговаривайте с ними чаще. Следите, чем они интересуются в интернете, что смотрят, на кого подписаны, кто их кумиры и прочее. Потому что вот такие «Славики» смотрят красиво упакованн…
💯792😁96❤44👍30👎27😱27🤬16🤔14
✨ Запорожское направление✨ Разведчики с Запорожского направоения благодарят подписчиков тг канала Два Майора и БФ Два Майора за переданную еду для выходов в реторт пакетах, а так же наше движение за переданный им перехватчик видеосигнала Диспетчер 835+. Мясо для изготовления еды для выходов приобретается БФ "Два Майора" при активном участии уважаемых читателей тг канала Два Майора. Фронтовой Снабженец БФ "Два Майо…
🙏308👎44❤35😁15👍11🕊2🤬2😱1
Showing the 12 most recent of 6,505 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.
@dva_majors edited 59 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.
We recorded 1 post on @dva_majors 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 349 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
Republishes
Channels on the register whose posts this channel has forwarded.
Republishes 89 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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.
Named by 619 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@dva_majors named 3 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 24 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 350 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.
43 domains this 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“Два майора” (@dva_majors), 1,160,870 subscribers as measured 16 November 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.