3 measurements spanning 7 days, net +9. 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 452–463 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
17 Aug 2026, 12:44
462
+9
10 Aug 2026, 15:15
453
no change
10 Aug 2026, 15:02
453
first reading
Engagement
19 posts held, back to 16 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
38.5%
avg views ÷ 462 subscribers
Avg views / post
178
12 posts measured
Reaction rate
8.58%
reactions ÷ views · ER floor
Posts in window
12
of 19 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 10 August 2026
Posts held
19 (16 July 2026 – 10 August 2026)
Views total
2,133
Reactions total
183
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Aug 2026, 15:15 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
Video runtime
12s
Average length
12s
Measured directly from 1 video 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.
Reaction mix
346 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 76.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🕊
266
76.9%
👍
80
23.1%
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 19 of the 19 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 346reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 16 July 2026 to 10 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.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @solintrm. 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 19 most recent posts we hold for this entry, published 16 July 2026 to 10 August 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.
я ни разу
тут
не была.
но я сразу
всё
поняла.
где обман, где ложь, где неправда
— оказалось, тут много оттенков.
есть любовь, есть счастье, есть свет
— непонятно лишь то,
в чём нет.
но понять меня, правда, заставили.
«посмотри, — говорят, — их глазами»
на колени отца поставили.
и под крики мои обезглавили.
да засунь
те глаза
себе в зад!
ВЕРНИ МНЕ НАЗАД
ЧИСТЫЙ ВЗГЛЯД.
засунь меня в стиральную машину.
эко-режим. градус не меньше ста.
отжим: на тыщу двести оборотов.
и детского две чаши порошка.
надеюсь, что она меня отмоет.
от грязи, что слоями на душе.
а если нет, хотя бы даст покоя
тому, что не моё.
и мне.
твой внутренний ребёнок
видел слишком много.
и много понял он
совсем не так.
плоды семян,
что бросили небрежно
срывая,
вдавливаешь ты в кулак.
деревья умирают.
обесплодили.
не хочешь ли ты прошлое
срубить?
зачем так важно, что росло
— уроды ли?
если красивое
собралась посадить?
короткая история про фобию —
не стать очередной дешёвой копией
с уродским и обоссанным надгробием.
...
однажды меня обозвали
белой вороной.
и с тех пор я пытаюсь понять:
а что в этом плохого?
что ужасного в том,
чтобы быть особенной?
быть ангелом в чёрной
перьевой массе.
строить своё будущее,
а не пристраиваться к чужому.
где жизнь серая и цикличная,
как лента на кассе.
смеяться не от счастья,
а от злорадства;
любит…
может правда
всё дело во мне?
может я правда
не умею жить?
и держать это нужно
в себе
— всё то, чему поклялась
служить?
но бог, смотря на меня, говорит:
« отбрось всё это, это не твоё.
твоя задача на земле
— любить.
твоя задача просто быть
собой.
твоя задача на земле
— светить...
всей тьме и злу —
назло. »
и несмотря назад,
идти вперёд.
и встречным пулям
открывать живот.
•••
я пыталась посмотреть эгрегор супермаркета, каждую категорию товаров отдельно, чтобы понять какие продукты энергетически чище...
но не смогла этого сделать.
кровь из мясного отдела затапливала магазин.
внезапный интуитивный арт мышкой в обычном пеинте.
кстати, видела у одного автора всяких записулек простенькие рисунки-иллюстрации к своим словам... а я тоже немного художник. сначала хотела сказать "бывший", но бывших не бывает. в общем возможно словлю мотивацию рисовать по своим мотивам.
(уже чую как тикток пачками блочет мои посты 😂 вы представьте что я там накалякать могу...)
вы замечали глаза у деревьев?
может быть, они более живые,
чем обычно принято считать?
может, мы живём в слишком
разных мерностях, чтобы друг друга полноценно осознать?
а может они смотрят на нас,
прямо сейчас
и в полтона друг другу говорят:
«хм... ты замечал глаза у людей?»
понимаешь, вот в чём дело...
прости, если мир твой разрушу.
я не могу дать тебе своё тело,
но могу отдать свою душу.
любовь — она ведь вне плоти?
любовь — это ведь не про секс?
я уверена, люди,
вы врёте.
я не самка, не зверь
— ЧЕЛОВЕК.
любовь — это ведь не про секс?
любовь ведь от солнца, правда?
твоё молчанье похоже на «нет»
но ответа не ты — автор.
понимаешь, в чём дело, вот...
у души на меня есть планы
это тело…
🕊16👍9
Showing the 12 most recent of 19 posts we hold for @solintrm. 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 — 1,143,546 of 1,549,376entries 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.
Mentions
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.
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 August 2026 — this
entry's latest reading, not the date you are reading this.
“s☼lin trame” (@solintrm), 462 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/solintrm.
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.