Channel
@history_skills
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,037subscribers
+50 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001592948085 |
|---|---|
| Type | Channel |
| Username | @history_skills |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/history_skills |
Education — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 09:21 | 2,037 | -4 |
| 13 Sept 2026, 03:58 | 2,041 | -10 |
| 9 Sept 2026, 13:56 | 2,051 | +187 |
| 4 Sept 2026, 08:59 | 1,864 | -15 |
| 1 Sept 2026, 00:34 | 1,879 | -13 |
| 28 Aug 2026, 19:54 | 1,892 | -16 |
| 26 Aug 2026, 04:54 | 1,908 | +3 |
| 23 Aug 2026, 15:35 | 1,905 | -18 |
| 20 Aug 2026, 02:37 | 1,923 | -13 |
| 17 Aug 2026, 10:34 | 1,936 | -19 |
| 13 Aug 2026, 22:38 | 1,955 | -11 |
| 11 Aug 2026, 02:01 | 1,966 | -12 |
| 8 Aug 2026, 09:04 | 1,978 | -9 |
| 7 Aug 2026, 20:33 | 1,987 | no change |
| 7 Aug 2026, 18:30 | 1,987 | first reading |
13 posts held, back to 21 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
294 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 26.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5447158334044020852 | 77 | 26.2% | |
| custom 5447569147665884309 | 58 | 19.7% | |
| custom 5449631114220051157 | 40 | 13.6% | |
| custom 5449459100779846721 | 37 | 12.6% | |
| custom 5447613553332756433 | 26 | 8.84% | |
| custom 5447488788827772901 | 21 | 7.14% | |
| custom 5447451512806615159 | 19 | 6.46% | |
| custom 5449427000194278559 | 16 | 5.44% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 13 of the 13 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 294 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 21 July 2026 to 7 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.
✈️ Виктор Талалихин герой, совершивший ночной таран. Для ЕГЭ по истории важно запомнить: сам подвиг, 1941 год и битву за Москву. Талалихин может встретиться в заданиях № 5 и № 8
custom 54471583340440208525custom 54494591007798467215custom 54475691476658843094
Video message, posted without a caption
custom 54474887888277729017custom 54475691476658843096custom 54494591007798467215custom 54496311142200511571
🤠Мы активно ищем людей, которые хотят создавать сильный образовательный продукт и развивать историческое образование вместе с нами 🥰Обязательное условие: проживание в Санкт-Петербурге Если вы готовы стать частью нашей команды или знаете человека, который идеально подходит на одну из этих вакансий, свяжитесь с нами. Аккаунт для связи: @historyskills
custom 544715833404402085211custom 54475691476658843095custom 54494270001942785595
Video message, posted without a caption
custom 54475691476658843099custom 54471583340440208527custom 54496311142200511577
👀1 августа – День памяти российских воинов, погибших в Первой мировой войне В этот день в 1914 году Германия объявила войну Российской империи. Наша страна была втянута в глобальный военный конфликт🥰
custom 544756914766588430919custom 544715833404402085210custom 54496311142200511576custom 54494270001942785591
Posted without readable text
custom 544761355333275643311custom 54471583340440208527custom 54494591007798467216
Video message, posted without a caption
custom 544963111422005115710custom 54474515128066151597custom 54474887888277729015
⭐️⭐️⭐️⭐️⭐️ ⭐️⭐️ ⭐️⭐️⭐️ ⭐️ ⭐️ ⭐️⭐️⭐️ Умрем, но не 🙂🙂 ⭐️⭐️⭐️⭐️ не отступим 🙂🙂 ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ «Ни шагу назад!» - знаменитый приказ № 227, изданный И.В. Сталиным 28 июля 1942 года в ходе Великой Отечественной войны. Издан в критический момент, когда враг рвался к Волге, а ситуация на фронте была крайне тяжелой. 🔥Для ЕГЭ запоминайте месяц и год.
custom 544745151280661515912custom 54471583340440208526custom 54474887888277729014
Video message, posted without a caption
custom 54475691476658843098custom 54476135533327564335custom 54494270001942785594
Posted without readable text
custom 54471583340440208527custom 54494270001942785596custom 54494591007798467216
Video message, posted without a caption
custom 54476135533327564337custom 54494591007798467216custom 54496311142200511576
Posted without readable text
custom 54471583340440208527custom 54475691476658843097custom 54474887888277729015custom 54476135533327564333
Showing the 12 most recent of 13 posts we hold for @history_skills. 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.
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.
Named by 1 registered channel — 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.
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.
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 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Дмитрий из History Skills” (@history_skills), 2,037 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/history_skills.
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.