#pink_steam_sound@levandovskiwrites треки к главе 6 :) As You Wish скорее к концовке. Было странно её писать. Если вы думаете, что у меня нет вопросов к происходящему, вы, конечно, ошибаетесь. Мне самой интересно, что будет в конце...
❤1

Channel
@levandovskiwrites
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
37subscribers
+27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004294448371 |
|---|---|
| Type | Channel |
| Username | @levandovskiwrites |
| Created | Between 1 May 2026 and 6 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/levandovskiwrites |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 10:20 | 37 | +8 |
| 7 Sept 2026, 13:58 | 29 | +2 |
| 29 Aug 2026, 21:36 | 27 | +1 |
| 23 Aug 2026, 03:53 | 26 | +5 |
| 14 Aug 2026, 21:52 | 21 | +11 |
| 12 Aug 2026, 08:31 | 10 | no change |
| 7 Aug 2026, 10:32 | 10 | first reading |
8 posts held, back to 6 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 8 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
25 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 60.0% | |
| custom 5190683945351535076 | 7 | 28.0% | |
| custom 5213447602732813642 | 2 | 8.00% | |
| 🔥 | 1 | 4.00% |
Custom emoji. 2 of the rows above are 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 8 of the 8 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 6 July 2026 to 11 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.
#pink_steam_sound@levandovskiwrites треки к главе 6 :) As You Wish скорее к концовке. Было странно её писать. Если вы думаете, что у меня нет вопросов к происходящему, вы, конечно, ошибаетесь. Мне самой интересно, что будет в конце...
❤1
🤧🤧🤧
❤1
Часть VI. Clootie Trees уже на сайте 🦋
custom 51906839453515350761
V. Love, Rosie уже тут
custom 51906839453515350763
вам открытки из шестой главы. раз я никак ниче не выложу, так хоть покажу, что сегодня генерировала видосики в клинге. сцена с грустной гермионой это я зря, конечно, не ясно, что происходит, ну и бог с ним. она была у меня в голове, когда я только задумывала написать эту историю, так что... поклон этому образу за то, что у нас есть пинк стим) пропала еще потому что почитываю венец для офелии, меня просто разрывает о…
custom 51906839453515350763❤2custom 52134476027328136421
начинаю главу и думаю... где мне взять столько слов, чтобы дотянуть хотя бы до 10 страниц спустя неделю бьюсь головой о клавиатуру
❤3custom 52134476027328136421
я, как самый настоящий чёрт, сломила ногу в собственном сюжете, но перелом сросся, и всё поехало. даты не могу обещать, ставлю на август... видит бог, я скоро лопну - жду дропа love, rosie и clootie trees, мои от чего-то любимые... даже больше, чем третья. я уже поняла, что каким-то чудом главы бьются на триптихи - это не запланированная история, бессознательная игра: первые три - о треске швов окклюменции, следующи…
❤3
очень хорошие новости: я нашла гамму. или гамма нашел меня... чистая случайность, но этот человек имеет алмазные глаза, чувство юмора и чувство границ, обширные познания и начитанность - я дурею с этой прикормки и хочу, если честно, платить ему деньги (ваш автор в капкане пульпита, бог знает, сколько я отдала за эти полтора месяца денег, питаюсь святым духом). мы вычитываем сейчас первые главы, и я не могу не хихикат…
❤5🔥1
Showing the 8 most recent of 8 posts we hold for @levandovskiwrites. 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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“rather ripped writing • pink steam” (@levandovskiwrites), 37 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/levandovskiwrites.
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.