Telegram RegisterThe public register of Telegram
Telegram profile photo for Sotahuuto

Channel

Sotahuuto

@sotahuuto

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

204subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001899723852
TypeChannel
Username@sotahuuto
CreatedBetween 1 November 2022 and 30 June 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held6
Confirmed unchanged3 times, most recently 11 October 2026
On Telegramt.me/sotahuuto

Topic

Other / unclassifiable — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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.

Growth

2022042037 August 2026 — 204 subscribers8 August 2026 — 204 subscribers16 August 2026 — 203 subscribers24 August 2026 — 202 subscribers1 September 2026 — 203 subscribers17 September 2026 — 204 subscribers7 August 202617 September 2026
6 measurements spanning 40 days. 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 202–204 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 03:17204+1
1 Sept 2026, 03:48203+1
24 Aug 2026, 20:34202-1
16 Aug 2026, 05:22203-1
8 Aug 2026, 11:18204no change
7 Aug 2026, 23:37204first reading

Engagement

16 posts held, back to 12 July 2025 — 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 16 posts for this entry, the most recent from 15 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

77 reactions across 7 posts, in 9 distinct kinds. The most used accounts for 29.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2329.9%
❤1519.5%
❤‍🔥1215.6%
🎉1114.3%
👏911.7%
🤩33.90%
👍22.60%
🍾11.30%
🤯11.30%

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

Measured over the 16 most recent posts we hold, published 12 July 2025 to 15 July 2025, 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

15 Jul 2025, 13:32 UTC606 views2 reactionsread 8 August 2026

Tapahtumamme pistenikkari Tuure Saloheimo sai pisteet julki viime yönä. Ne löytyvät täältä ja päivittyvät lisädatalla lähitulevaisuudessa: https://drive.google.com/file/d/1vJj6d8bQdW-om4Em5XmU3RErj854mIo8/view

👍2

15 Jul 2025, 13:31 UTC596 views1 reactionsread 8 August 2026

Sotahuudon 2025 palautekysely on nyt täällä! Käy kirjaamassa risusi ja ruususi nyt, kun ne ovat vielä tuoreessa muistissa, jotta voimme järjestää ensi vuonna vieläkin paremman tapahtuman! https://forms.gle/NqemPnarYSfEWJCQ7

❤1

14 Jul 2025, 19:56 UTC555 views4 reactionsread 8 August 2026

Linkin takana tietopaketti XX-juhlista, kuten maanantaille luvattiin! https://docs.google.com/document/d/1HLZpOYtRCkH2TF2u28N_QGpzuAL8hwDHQKSrMMFCsKA/edit?usp=drivesdk

🤩3🍾1

14 Jul 2025, 09:16 UTC413 viewsread 8 August 2026

Seuraavat kuvat ovat löytötavaroita. Mikäli tunnistat omasi, otathan yhteyttä MAHDOLLISIMMAN PIAN Conaniin (discordissa conan11 ). Järjestäjätiimi ei voi täysin taata löytötavaroiden säilyvyyttä ensi Sotahuutoon asti, mutta ne voidaan MAHDOLLISESTI toimittaa ToRaan.

13 Jul 2025, 17:21 UTC373 views26 reactionsread 8 August 2026

Pellot alkavat olla tyhjät ja Sotahuuto 2025 kääntyy sunnuntai-iltaan sekä tapahtuman loppumiseen. Kiitokset järjestäjätiimiltä jokaiselle taistelijalle, vapaaehtoiselle, katsojalle, tapahtumatilan isännälle sekä kaikille muille osallisille, jotka jäävät näiden ulkopuolelle. Juhlasotahuuto 2025 todellakin oli ansaitun hohdokas - teidän ansiostanne! Ensi viikon puolella, kunhan järjestäjätiimi jäähtyy hetken viikonl…

❤‍🔥12👏9❤5

13 Jul 2025, 16:22 UTC335 views5 reactionsread 8 August 2026

XX-juhlien ennakkoilmoittautuminen julkaistaan tälle kanavalle huomenna!

🔥5

13 Jul 2025, 14:57 UTC334 views11 reactionsread 8 August 2026

Sotahuudon 2025 voitti Ajan Kaarti + Harhamainparvi Julkaisemme lopulliset tulokset ensi viikon puolella

🎉11

13 Jul 2025, 14:52 UTC340 views28 reactionsread 8 August 2026

Helle on sekoittanut myös pääjärjestäjien niin, että unohdimme jakaa pukukilpailun palkinnon. Pukukilpailun pääkriteerit ovat tunnistettavuus (yksittäisenkin joukkuelaisen tunnistaa helposti), yhtenäisyys (kuinka yhdenmukainen teema joukkueen varustuksessa on) ja tyylikkyys (kuinka hienolta joukkue näyttää). Voittajajoukkue saa kiertopalkinnon itselleen ja pääsee raatiin, joka valitsee palkinnot vuosittain. Pukukilp…

🔥18❤9🤯1

12 Jul 2025, 18:59 UTC308 viewsread 8 August 2026

Huomio, auton avaimet kadonneet! Mikäli löydät tapahtuma-alueelta toyotan avaimet, toimitathan ne infopisteelle.

12 Jul 2025, 18:17 UTC362 viewsread 8 August 2026

Huomio, aikataulumuutos! Historialliset tanssit loppuvat ja teatterimiekkailu alkaa vähän aiemmin eli kello 22:15

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

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Sotahuuto” (@sotahuuto), 204 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/sotahuuto.

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.