Telegram RegisterThe public register of Telegram
Telegram profile photo for Чёрные гусары

Channel

Чёрные гусары

@blackhussars

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

27,737subscribers

-48 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001909866341
TypeChannel
Username@blackhussars
DescriptionВсё о гвардейской Александрийской ордена Суворова бригаде. ПРАВИЛА КАНАЛА ЧИТАТЬ ОБЯЗАТЕЛЬНО: https://t.me/blackhussars/4777 Мы в Максе - https://max.ru/blackhussars Если ссылка работает некорректно, вставьте адрес в поисковую строчку в Максе.
Created31 March 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/blackhussars

Topic

Religion — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 4 other registered channels. 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@blackhussars/8264 · this entry17 Oct 2026, 14:47 UTC@btr80/4215518 Oct 2026, 19:02 UTC1.0028 hours
@blackhussars/8405 · this entry11 Nov 2026, 10:14 UTC@stepnoi_veter/2953312 Nov 2026, 05:29 UTC1.0019 hours
@maximgrigoryev/129939 Nov 2026, 07:10 UTC@blackhussars/8388 · this entry9 Nov 2026, 09:44 UTC0.972.6 hours
@MedvedevVesti/2786425 Sept 2026, 17:37 UTC@blackhussars/8129 · this entry25 Sept 2026, 18:23 UTC1.0046 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
@btr8016 (8/8 hand-verifiable sample passed)1.006.8 hoursthis entry (11–5)
@stepnoi_veter6 (6/6 hand-verifiable sample passed)1.003.1 hourseven
@maximgrigoryev5 (5/5 hand-verifiable sample passed)0.983.0 hours@maximgrigoryev (5–0)
@MedvedevVesti6 (6/6 hand-verifiable sample passed)1.003 daysthis entry (4–2)

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. 2 of the 2 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 275 comparable posts for this entry, running 2 August 2026 to 14 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 keys clone_copy · clone_mutual · clone_source, last confirmed 15 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

27,64527,80727,72627,7375 August 202612 November 2026
63 measurements spanning 99 days, net -48. 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 27,621–27,831 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
12 Nov 2026, 16:1427,737-14
10 Nov 2026, 15:3827,751-11
8 Nov 2026, 23:5627,762-17
7 Nov 2026, 13:2827,779-12
6 Nov 2026, 16:0727,791-1
5 Nov 2026, 14:0627,792+2
4 Nov 2026, 13:1927,790+2
3 Nov 2026, 13:4027,788-6
2 Nov 2026, 16:3027,794+2
1 Nov 2026, 14:3527,792+3
31 Oct 2026, 17:0027,789-8
29 Oct 2026, 19:1827,797-6
28 Oct 2026, 21:1727,803+10
27 Oct 2026, 19:0027,793-6
26 Oct 2026, 16:4027,799+3
25 Oct 2026, 17:3027,796-1
23 Oct 2026, 20:3127,797-10
22 Oct 2026, 22:5027,807+6
21 Oct 2026, 21:0627,801-1
20 Oct 2026, 16:4127,802first reading

Engagement

409 posts held, back to 2 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 161 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.51%
avg views ÷ 27,737 subscribers
Avg views / post
2,360
128 posts measured
Reaction rate
1.91%
reactions ÷ views · ER floor
Posts in window
128
of 409 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 held409 (2 August 2026 – 14 November 2026)
Views total301,970
Reactions total5,763
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 03:03 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
≈5,190
Videos
≈2,510
Links
≈1,630

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
7h 24m
Average length
2m 52s

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

18,057 reactions across 402 posts, in 33 distinct kinds. The most used accounts for 28.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5,20028.8%
❤4,25623.6%
🙏3,13217.3%
🔥2,35413.0%
🫡1,0425.77%
❤‍🔥6473.58%
💯3131.73%
😁2641.46%
😢1390.77%
👏1380.764%
😭780.432%
🥰740.41%
😱610.338%
🎉530.294%
🤝470.26%
🤗320.177%
😍310.172%
👎250.138%
🤔230.127%
🤷‍♂210.116%
13 further kinds1270.703%

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

Measured over the 409 most recent posts we hold, published 2 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: 13 of 128 posts held from the last 30 days (10.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).

14 Nov 2026, 09:05 UTC≈1,330 views25 reactionsread 15 November 2026

Posted without readable text

👍10❤‍🔥8❤2🥰2⚡1😎1🙏1

14 Nov 2026, 08:10 UTC≈1,410 views35 reactionsread 15 November 2026
Photo

Они долго готовились: курс молодого бойца, уставы, стрельбы, первые тревоги и построения. И вот настал этот день — присяга. В Рощинском на плацу звучат клятвы, и в глазах новобранцев — волнение и гордость. Поздравляем новобранцев с этим важным рубежом! Пусть служба будет достойной, а рядом всегда будут верные товарищи.

❤‍🔥17👍15🔥3

14 Nov 2026, 04:41 UTC≈1,540 views48 reactionsread 15 November 2026
Video

Мама сказала - надеть. С бодрым утром!

❤29👍11❤‍🔥5🫡3

13 Nov 2026, 15:25 UTC≈1,710 views17 reactionsread 15 November 2026
Forwarded from @mod_russiaPhoto

Обезопась себя и научи близких! 📆 Сегодня, в День службы защиты государственной тайны, повод напомнить: информационная безопасность зависит от каждого. 📱 Лишнее фото в чате, кривая ссылка или включенный GPS в телефоне работают против нас быстрее любого оружия. Противник фиксирует и собирает каждую цифровую крошку. ▫️ Чтобы закрыть эти бреши, стране нужны те, кто умеет держать удар на информационном фронте. Именно …

👍17

13 Nov 2026, 14:38 UTC≈1,720 views37 reactionsread 15 November 2026
Photo

Поздравляем с Днём службы защиты государственной тайны всех причастных! Ваша работа — надёжный щит безопасности страны. Спасибо за профессионализм и ответственность🫡

🔥23👍10❤4

13 Nov 2026, 06:54 UTC≈1,860 views37 reactionsread 15 November 2026
Video

Помощник муфтия Татарстана и имам гвардейской Александрийской бригады Мухаммад хазрат о работе с верующими в зоне проведения СВО. #СВОиРелигии

❤18🔥8👌4👍4🤝2👎1

13 Nov 2026, 05:07 UTC≈1,960 views40 reactionsread 15 November 2026
Photo

Поздравляем всех причастных с Днём войск РХБЗ! Горе тем, кто стал вашей целью!

❤26🫡10👍4

13 Nov 2026, 04:32 UTC≈1,950 views47 reactionsread 15 November 2026
Photo

Работаем. Бодрого утра!

❤28🙏10🫡7👍2

12 Nov 2026, 09:04 UTC≈2,150 views38 reactionsread 15 November 2026
Photo

ПОСТ ОТ АДМИНОВ. Обязателен к прочтению. Здравствуйте все! Считаем важным напомнить правила канала. Они не меняются уже несколько лет и одинаковы как для канала в ТГ, так и в Максе. Главное правило - соблюдение информационной безопасности. 1️⃣ Не пишите в комментариях никаких личных данных - номера подразделений и должности, имена и фамилии, позывные, направление работы. Такие сообщения будут удаляться. На вопрос…

👍28🙏9❤1

12 Nov 2026, 06:07 UTC≈2,000 views39 reactionsread 15 November 2026
Forwarded from @red_army1Video

⭐️🔥🔡🔡🔡 Репортаж о военных разведчиках 15 гвардейской бригады "Чёрные Гусары" группировки Центр. Отдельного внимания заслуживает воин 1981 года рождения с позывным Никипел. В ходе боёв за Котлино и Удачное он находился на переднем крае. И восемь месяцев в одиночку сдерживал атаки боевиков ВСУ. Помогли навыки. Опытный охотник с Алтая можно сказать вырос в тайге вместе с ружьём. #разведка #разведчики #сво #Черные…

🔥24❤9👍5🤔1

12 Nov 2026, 04:33 UTC≈2,020 views40 reactionsread 15 November 2026
Video

Бодрого утра, империя!

🔥28❤‍🔥8💯4

11 Nov 2026, 11:25 UTC≈2,330 views27 reactionsread 15 November 2026
Video

Первая мировая война. Фрагмент кинохроники "Русский экспедиционный корпус во Франции". Второй особый пехотный полк, сформированный в Самаре, разместили в секторе Оберив. Фронт здесь давно стабилизировался и противник даже в страшном сне не помышлял о каких-то действиях. Но тут пришли русские и всё изменилось. Начались бесконечные "кудемены" - вылазки на разведку. Днём и ночью самарцы уходили в сторону германских поз…

👍14🫡7❤3🙏3

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

@blackhussars edited 6 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
2 September 2026
Most recent edit
6 November 2026

Forward network

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

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.

Channels Telegram recommends alongside this 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.

Операция Z: Военкоры Русской Весны
@rvvoenkor · 1,451,986
#1
АРХАНГЕЛ СПЕЦНАЗА
@arx_spn · 1,022,538
#2
Работайте, братья!
@btr80 · 148,666
#3
Повёрнутые на войне 🇷🇺
@voenacher · 657,808
#4
Кирилл Фёдоров / Война История Оружие
@warhistoryalconafter · 477,766
#5
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,661,091
#6
Говорит ТопаZ 🪖
@Love_Russia_Beauty · 114,573
#7
Северный Ветер
@warriorofnorth · 118,385
#8
WarGonzo
@wargonzo · 737,693
#9
Крылатые
@russian_airborne · 49,647
#10
Крупнокалиберный Переполох
@bolshiepushki · 322,416
#11
Воин DV
@voin_dv · 144,935
#12
Kotsnews
@sashakots · 469,228
#13
Мир | Перезагрузка
@mir_perezagruzka · 5,311
#14
Сладков+
@sladkov_plus · 692,174
#15
Поддубный |Z|О|V| edition
@epoddubny · 567,310
#16
Сибирское объединение
@Sib_army · 13,371
#17
Уголок Ситха
@Ugolok_Sitha · 49,103
#18
ОРБ Спарта 18+🔥
@orbSparta_Officially · 7,828
#19
Дайджест Z
@digest1744 · 2,964
#20
ВДВ Псков ZOV
@vdvpskovz · 25,068
#21
98 гвардейская ВДД
@vdd98 · 23,792
#22
МИГ России
@mig41 · 476,345
#23
Канал специального назначения
@okspn · 130,373
#24
Бешеные псы
@urga_74 · 31,619
#25
ИЗНАНКА
@The_Wrong_Side · 133,535
#26
Z ParaBellum MD
@ZParaBellumMD · 4,782
#27
ЗАПОРОЖСКИЙ ФРОНТ
@ZA_FROHT · 82,230
#28
Апти Алаудинов «АХМАТ»
@AptiAlaudinovAKHMAT · 199,502
#29
Фронтовая птичка
@frontbird · 115,753
#30
Портфель Генштаба
@genshtab24 · 83,063
#31
CREW RUSSIA
@crewruss1a · 60,655
#32
Репортёр Руденко V
@RtrDonetsk · 153,097
#33
U_G_M
@Ukr_G_M · 76,667
#34
Оперативные сводки
@opersvodki · 403,037
#35
verumreactor
@verumreactor · 4,422
#36
Дневник Десантника🇷🇺
@DnevnikDesantnika · 74,979
#37
Позывной《OSETIN》
@osetin21 · 65,313
#38
Охотники за головами
@heads_hunters · 29,986
#39
Позывной Брюс
@brussinf · 106,869
#40
Южный фронт
@yuzhny_front_ZOV · 20,061
#41
Белорусский силовик
@belarusian_silovik · 449,733
#42
Colonelcassad
@boris_rozhin · 750,033
#43
Fighterbomber
@bomber_fighter · 526,231
#44
Readovka
@readovkanews · 2,011,824
#45
Старше Эдды
@vysokygovorit · 484,806
#46
Тринадцатый.
@Z13_Separ · 208,366
#47
Воевода Вещает
@ZOV_Voevoda · 167,036
#48
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 273,485
#49
Минобороны России
@mod_russia · 649,285
#50
ТРОЙКА 🏴‍☠️
@rustroyka1945 · 188,562
#51
Военный Осведомитель
@milinfolive · 614,555
#52
ПТСР TEAM Community
@ptsr_team · 37,936
#53
🇷🇺 DONTSTOPWAR
@dontstopwar · 249,119
#54
СОЛДАТ УДАЧИ
@Soldieroffortune777 · 118,203
#55
Месть доброй воли
@Mestb_Dobroj_Voli · 100,008
#56
СОЛОВЬЁВ
@solovievlive · 1,113,285
#57
НгП раZVедка
@NgP_raZVedka · 94,042
#58
Военкор Котенок
@voenkorKotenok · 308,376
#59
Неофициальный Безсонов
@NeoficialniyBeZsonoV · 241,767
#60
Репортер Filatov
@filatovcorr · 167,209
#61
Милитарист
@infantmilitario · 275,733
#62
ANNA NEWS
@anna_news · 228,509
#63
Осведомитель
@infomil_live · 95,364
#64
DIVGEN 🚩 Карта СВО
@divgen · 75,937
#65
Aviahub
@Aviahub34 · 94,023
#66
Белые дяди в Африке🌴
@wagner_group2022 · 124,212
#67
ZERGULIO
@SergeyKolyasnikov · 443,771
#68
LOSTARMOUR | Carthago delenda est!
@lost_armour · 88,584
#69
Украина.ру
@ukr_2025_ru · 493,820
#70
Сводки и Аналитика СВО (Резерв)
@rezervsvo · 203,453
#71
ХИЛЕР l HEALER
@HealerTacMed · 130,267
#72
Военный обозреватель
@new_militarycolumnist · 204,551
#73

Read from Telegram’s recommendation API, most recently 13 September 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.

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.

98 гвардейская ВДД
@vdd98 · 23,792
Telegram ranks this channel #43 of 75 here — alongside 74 others — read 17 September 2026
ВДВ Псков ZOV
@vdvpskovz · 25,068
Telegram ranks this channel #48 of 73 here — alongside 72 others — read 13 September 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 November 2026 — this entry's latest reading, not the date you are reading this.

“Чёрные гусары” (@blackhussars), 27,737 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/blackhussars.

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.