коконутая
custom 532826489473732792899custom 533719778676288061327custom 534595469679844955416custom 53527727726972562863custom 52986204291649191912
Signed storm

Channel
@stormcloudiary
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry
29,822subscribers
+961 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001534170817 |
|---|---|
| Type | Channel |
| Username | @stormcloudiary |
| 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 | 18 October 2026 |
| Measurements held | 41 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/stormcloudiary |
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 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Oct 2026, 23:56 | 29,822 | +55 |
| 17 Oct 2026, 23:16 | 29,767 | +74 |
| 16 Oct 2026, 23:58 | 29,693 | +20 |
| 15 Oct 2026, 21:21 | 29,673 | -27 |
| 14 Oct 2026, 21:54 | 29,700 | -32 |
| 13 Oct 2026, 12:46 | 29,732 | +88 |
| 9 Oct 2026, 10:40 | 29,644 | -122 |
| 4 Oct 2026, 22:00 | 29,766 | +387 |
| 27 Sept 2026, 14:39 | 29,379 | +82 |
| 17 Sept 2026, 17:17 | 29,297 | -12 |
| 15 Sept 2026, 11:36 | 29,309 | +30 |
| 13 Sept 2026, 23:20 | 29,279 | +172 |
| 12 Sept 2026, 06:39 | 29,107 | -38 |
| 10 Sept 2026, 00:16 | 29,145 | -69 |
| 6 Sept 2026, 13:58 | 29,214 | -33 |
| 4 Sept 2026, 05:55 | 29,247 | +72 |
| 2 Sept 2026, 21:19 | 29,175 | -37 |
| 1 Sept 2026, 17:38 | 29,212 | -43 |
| 31 Aug 2026, 20:06 | 29,255 | -64 |
| 30 Aug 2026, 21:54 | 29,319 | first reading |
248 posts held, back to 5 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 138 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 18 October 2026 |
|---|---|
| Posts held | 248 (5 August 2026 – 18 October 2026) |
| Views total | 445,480 |
| Reactions total | 32,956 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Oct 2026, 15:46 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.
Measured directly from 8 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.
73,410 reactions across 247 posts, in 30 distinct kinds. The most used accounts for 12.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5406989072587598480 | 9,084 | 12.4% | |
| custom 5298620429164919191 | 6,465 | 8.81% | |
| custom 5384459714262250001 | 5,894 | 8.03% | |
| custom 5195370549240441487 | 4,913 | 6.69% | |
| custom 5418104804431930059 | 4,566 | 6.22% | |
| custom 5433625596468961806 | 3,460 | 4.71% | |
| custom 5328264894737327928 | 3,361 | 4.58% | |
| custom 5447106811616337053 | 3,209 | 4.37% | |
| custom 5222273275194813560 | 3,162 | 4.31% | |
| custom 5337197786762880613 | 3,099 | 4.22% | |
| custom 5345954696798449554 | 2,666 | 3.63% | |
| custom 5321132830959380132 | 2,647 | 3.61% | |
| custom 5258373171102395671 | 2,583 | 3.52% | |
| custom 5298932437064131793 | 2,506 | 3.41% | |
| custom 5458385485929947059 | 2,175 | 2.96% | |
| custom 5296564565759273939 | 1,846 | 2.51% | |
| custom 5195374595099628856 | 1,811 | 2.47% | |
| custom 5352772772697256286 | 1,743 | 2.37% | |
| custom 5224367814780952359 | 1,633 | 2.22% | |
| custom 5321032955789885847 | 1,472 | 2.01% | |
| 10 further kinds | 5,115 | 6.97% |
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 247 of the 248 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 73,410 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 248 most recent posts we hold, published 5 August 2026 to 18 October 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 @stormcloudiary. 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 248 most recent posts we hold for this entry, published 5 August 2026 to 18 October 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 248 most recent posts we hold, published 5 August 2026 to 18 October 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
коконутая
custom 532826489473732792899custom 533719778676288061327custom 534595469679844955416custom 53527727726972562863custom 52986204291649191912
Signed storm
☠️
custom 5337197786762880613146custom 534595469679844955449custom 532826489473732792837custom 52986204291649191916custom 53527727726972562862
Signed storm
#eat - отправляйте свой ужин в комм.
custom 5298620429164919191134custom 532826489473732792855custom 534595469679844955432custom 53371977867628806135custom 53527727726972562862
Signed storm
🤩
custom 5352772772697256286200custom 533719778676288061363custom 532826489473732792851custom 534595469679844955411custom 529862042916491919110
Signed storm
Video message, posted without a caption
custom 5352772772697256286100custom 534595469679844955447custom 532826489473732792826custom 529862042916491919113custom 53371977867628806133
Signed storm
#eat 🫐 отправляйте свой завтрак в комм.
custom 5337197786762880613171custom 535277277269725628655custom 529862042916491919140custom 534595469679844955414custom 53282648947373279288
Signed storm
🤩
custom 5345954696798449554168custom 535277277269725628641custom 532826489473732792840custom 52986204291649191919custom 53371977867628806136
Signed storm
комфортно сделали ресницы 🌸 сейчас будем заполнять документы для школы 📓
custom 5298620429164919191198custom 533719778676288061361custom 532826489473732792851custom 534595469679844955413custom 53527727726972562866
Signed storm
#eat 🥥 отправляйте свое.
custom 5337197786762880613177custom 532826489473732792856custom 535277277269725628635custom 529862042916491919110custom 534595469679844955410
Signed storm
первая покраска корней, без каких либо приборов, совершена. руками в перчатках, а миска из под творога. в салоне стоит 10 тыс. я могу за 250₽. завтра записалась на ресницы. переживаю.. здесь мне никто тру крайм не включит 😅 маленький лайфхак. когда я лежала в первый раз и ловила панические атаки под музыку, мастерица предложила включить тру крайм, я отказалась, думала, что станет еще хуже, если буду слушать про расч…
custom 5328264894737327928201custom 535277277269725628649custom 533719778676288061335custom 534595469679844955410custom 52986204291649191918
Signed storm
#eat 🤩 отправляйте свое в комм.
custom 5352772772697256286191custom 532826489473732792873custom 529862042916491919148custom 534595469679844955411custom 53371977867628806138
Signed storm
гипнотически
custom 5298620429164919191248custom 534595469679844955480custom 535277277269725628643custom 532826489473732792810custom 53371977867628806137
Signed storm
Showing the 12 most recent of 248 posts we hold for @stormcloudiary. 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.
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.
@stormcloudiary named 1 handle 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.
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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“☾ ·⋆ stormcloudiary ♱ ❆” (@stormcloudiary), 29,822 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/stormcloudiary.
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.