Telegram RegisterThe public register of Telegram

Channel

Black History

@Black_History

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

94,432subscribers

-131 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001188527100
TypeChannel
Username@Black_History
DescriptionТемная сторона истории. Этого не найти в книгах. Сотрудничество: @BLACKhisto1, @PRinfo Прайс: @Prices_media, @swaymedia Купить рекламу: https://telega.in/c/Black_History 4905692288
Created29 June 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Black_History

Growth

94,43294,56394,497.56 August 2026 — 94,563 subscribers6 August 2026 — 94,562 subscribers7 August 2026 — 94,538 subscribers8 August 2026 — 94,520 subscribers9 August 2026 — 94,500 subscribers10 August 2026 — 94,490 subscribers11 August 2026 — 94,461 subscribers12 August 2026 — 94,432 subscribers6 August 202612 August 2026
8 measurements spanning 6 days, net -131. 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 94,412–94,583 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 05:2394,432-29
11 Aug 2026, 02:1594,461-29
10 Aug 2026, 01:0794,490-10
9 Aug 2026, 01:3094,500-20
8 Aug 2026, 01:2794,520-18
7 Aug 2026, 03:5394,538-24
6 Aug 2026, 03:4094,562-1
6 Aug 2026, 01:3394,563first reading

Engagement

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

ERR · 30 days
4.63%
avg views ÷ 94,432 subscribers
Avg views / post
4,370
51 posts measured
Reaction rate
0.857%
reactions ÷ views · ER floor
Posts in window
51
of 51 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. It is computed over the 47 of 51 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held51 (4 August 202612 August 2026)
Views total223,020
Reactions total1,804
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 18:38 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
8,890
Videos
43
Links
1,360

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.

Reaction mix

1,565 reactions across 42 posts, in 7 distinct kinds. The most used accounts for 36.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍57736.9%
😱26216.7%
🔥19812.7%
19012.1%
😢16510.5%
🤯1227.80%
👏513.26%

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

Measured over the 51 most recent posts we hold, published 4 August 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.

Recent posts

12 Aug 2026, 17:08 UTC≈1,350 views18 reactionsread 12 August 2026
Photo

«Если Россия одержит победу!» – американский плакат времен Холодной войны, 1953 год. Black History / Мы в МАХ

👍15🔥2🤯1

12 Aug 2026, 14:01 UTC≈2,400 views27 reactionsread 12 August 2026
Photo

Похороны Джона Ф. Кеннеди. 1963 год. Black History / Мы в МАХ

👍11😢93🔥2😱2

12 Aug 2026, 07:08 UTC≈3,430 views45 reactionsread 12 August 2026
Photo

Заточка зубов у индонезийских племен и её результат, фотографии 1938 года. Black History / Мы в МАХ

🤯38😱4🔥3

12 Aug 2026, 04:23 UTC≈3,690 views31 reactionsread 12 August 2026
Photo

Беженцы из коммунистического Китая в ожидании возвращения после того, как их поймали британские власти. Гонконг, британская коронная колония Британский Гонконг, Британская империя. Май 1962 года. Black History / Мы в МАХ

😢22😱7🔥2

11 Aug 2026, 19:19 UTC≈4,270 views32 reactionsread 12 August 2026
Photo

Убийство во время торжественного парада Анвара Садата исламскими фундаменталистами. За сближение с Израилем и отказ от дальнейшей исламизации общества (погибло 7 и ранено 28 человек), 1981 год. Black History / Мы в МАХ

😱264🔥2

11 Aug 2026, 12:49 UTC≈4,300 views31 reactionsread 12 August 2026
Photo

Офицеры достают металлический фургон, похороненный тремя похитителями, в котором какое то время до этого находился водитель школьного автобуса, который они угнали у него и дети. Июль 1976, Калифорния. Black History / Мы в МАХ

😱31

11 Aug 2026, 07:11 UTC≈4,030 views58 reactionsread 12 August 2026
Photo

Задержанные бандиты из группировки Уралмаш лежат вповалку перед допросом. 1992 год. Black History / Мы в МАХ

👍46🔥72👏2😱1

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

Citation-graph rank

Citation-graph rank — 90,649 of 1,151,006entries 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

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 7 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Nation Geographic
@NationGeographic · 327,695
Telegram ranks this channel #61 of 93 here — alongside 92 others — read 10 August 2026
История
@history_0o · 330,342
Telegram ranks this channel #67 of 89 here — alongside 88 others — read 10 August 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 August 2026 — this entry's latest reading, not the date you are reading this.

“Black History” (@Black_History), 94,432 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Black_History.

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.