у меня тут есть кто из тотьмы? нужна ваша помощь
custom 542041486118200472632custom 537783534138846952011

Channel
@sserovaal
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
6,384subscribers
-431 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002359910330 |
|---|---|
| Type | Channel |
| Username | @sserovaal |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/sserovaal |
Ecommerce storefront — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 03:21 | 6,384 | -26 |
| 10 Nov 2026, 14:51 | 6,410 | -17 |
| 7 Nov 2026, 00:06 | 6,427 | -8 |
| 3 Nov 2026, 22:20 | 6,435 | -19 |
| 31 Oct 2026, 20:08 | 6,454 | -8 |
| 29 Oct 2026, 06:01 | 6,462 | -9 |
| 26 Oct 2026, 08:30 | 6,471 | -12 |
| 23 Oct 2026, 11:10 | 6,483 | -14 |
| 20 Oct 2026, 15:04 | 6,497 | -8 |
| 17 Oct 2026, 20:27 | 6,505 | -11 |
| 14 Oct 2026, 22:35 | 6,516 | -6 |
| 11 Oct 2026, 19:41 | 6,522 | -33 |
| 4 Oct 2026, 22:37 | 6,555 | -39 |
| 26 Sept 2026, 00:41 | 6,594 | -51 |
| 17 Sept 2026, 00:21 | 6,645 | -35 |
| 12 Sept 2026, 16:58 | 6,680 | -13 |
| 8 Sept 2026, 15:59 | 6,693 | -22 |
| 2 Sept 2026, 22:57 | 6,715 | -10 |
| 30 Aug 2026, 16:36 | 6,725 | -11 |
| 28 Aug 2026, 00:24 | 6,736 | first reading |
18 posts held, back to 1 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 14 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 7 November 2026 |
|---|---|
| Posts held | 18 (1 July 2026 – 7 November 2026) |
| Views total | 7,890 |
| Reactions total | 82 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 18:34 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.
1,552 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 27.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5364122752057896446 | 424 | 27.3% | |
| custom 5363994345420646575 | 364 | 23.5% | |
| custom 5377835341388469520 | 337 | 21.7% | |
| custom 5415671357566374541 | 221 | 14.2% | |
| custom 5420414861182004726 | 143 | 9.21% | |
| custom 5366471708326784464 | 57 | 3.67% | |
| custom 5233403833266223046 | 6 | 0.387% |
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 18 of the 18 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,552 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 1 July 2026 to 7 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sserovaal. 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 18 most recent posts we hold for this entry, published 1 July 2026 to 7 November 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.
Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) 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).
у меня тут есть кто из тотьмы? нужна ваша помощь
custom 542041486118200472632custom 537783534138846952011
продаю свои вещи сегодня тут: https://t.me/shmotsserova
custom 541567135756637454121custom 53778353413884695209custom 54204148611820047267custom 52334038332662230462
полезная реклама для Тарноги как-то я из Тарноги в Вологду ехала на маршрутке и мой путь занял 6ч😭 на этой вы доедете за 3-3,5ч👍🏻
custom 537783534138846952057custom 536399434542064657510custom 54204148611820047265custom 54156713575663745414
мини-обучение смм подойдёт новичкам или тем, кто только хочет начать работать в смм! видео-уроки, обратная связь от меня, домашние задания, полезные материалы, сертификат в конце. длительность: неделя старт: 31 августа после прохождения этого обучения, если решите идти учиться дальше — будет скидка 10.000₽ на обучение в моей школе! оплатить можно тут после обучения вы получите профессию «контент-менеджер»
custom 542041486118200472612custom 53778353413884695208custom 53639943454206465753custom 52334038332662230462custom 53641227520578964461
я хотела прибраться получилось чето другое😭🤣
custom 536412275205789644673custom 537783534138846952022custom 536399434542064657520custom 53664717083267844642
вот смысл покупать стоник на авито?)) 90% паль по цене оригинала, а те 10% оригинала нужно ещё найти, легит чек сделать, смысл себе эти запары устраивать? у моих друзей отличный прайс на оригинальные вещи SI и быстрая доставка⚡️
custom 537783534138846952025custom 54204148611820047266custom 53641227520578964463
сплетня!!!
custom 537783534138846952072custom 541567135756637454123custom 536412275205789644613custom 53639943454206465754custom 52334038332662230462
с одного ножа бургеры едим сегодня
custom 537783534138846952033custom 541567135756637454111custom 53639943454206465759
Бустер пришел
custom 537783534138846952040custom 541567135756637454113custom 536399434542064657510
Video message, posted without a caption
custom 541567135756637454129custom 536412275205789644620custom 53778353413884695209custom 53639943454206465753
Video message, posted without a caption
custom 536412275205789644626custom 536399434542064657514custom 537783534138846952012
Video message, posted without a caption
custom 536412275205789644624custom 541567135756637454114custom 53639943454206465756
Showing the 12 most recent of 18 posts we hold for @sserovaal. 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.
We recorded 1 post on @sserovaal as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“ссероваал” (@sserovaal), 6,384 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/sserovaal.
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.