Channel

Черновик гострайтера

@ghostwriterliza

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

178subscribers

+1 since we began measuring on 13 August 2026

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

Register entry

Telegram ID	-1001773611515
Type	Channel
Username	@ghostwriterliza
Created	Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	13 August 2026
Last confirmed live	13 August 2026
Measurements held	2
Confirmed unchanged	1 time, most recently 13 August 2026
On Telegram	t.me/ghostwriterliza

Growth

2 measurements taken within a single day, net +1. 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 177–178 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
13 Aug 2026, 23:16	178	+1
13 Aug 2026, 12:03	177	first reading

Engagement

5 posts held, back to 4 April 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 19 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime: 1m 37s
Average length: 1m 37s

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

109 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 65.1% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
❤	71	65.1%
custom 5404337067721236500	19	17.4%
custom 5255982373262074102	10	9.17%
custom 5334882760735598374	9	8.26%

Custom emoji. 3 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 areTelegram’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 5 of the 5 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 109reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 4 April 2026 to 19 May 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.

Recent posts

19 May 2026, 07:22 UTC179 views10 reactionsread 13 August 2026

Forwarded from @lesrukmediaPhoto

Давайте все дружно пойдем слушать мой подкаст? Вон и погода хорошая, как раз для того, чтобы несколько часов гулять по парку и наслаждаться тем, как мы с Лизой спорим. О том, получился ли у Нади Алексеевой «Белград». О том, почему всем нравится «Граф Аверин»? Насколько сильно переоценен «Медвежий угол» Бакмана? И почему всем нам нужна «Сценаристка» Павловой? Сходите и послушайте. Подкаст «Испитый сюжет» — мое любим…

❤8custom 54043370677212365002

10 May 2026, 18:19 UTC193 views20 reactionsread 13 August 2026

Photo

Донцова и Ставангер не могли быть в одном предложении, но они были! Ездили в роуд-трип по Норвегии и заезжали на денек в прекрасный город Ставангер. Это значимый город для страны, раньше здесь были крупнейшие сардиновые заводы, а потом норвежцы обнаружили здесь нефть и стали очень богатыми. Город мне понравился: частный сектор органично вписывается в городскую инфраструктуру, а еще он оказался неожиданно космополитн…

❤14custom 53348827607355983745custom 52559823732620741021

4 May 2026, 12:11 UTC181 views28 reactionsread 13 August 2026

🟡Апдейты по карьере: За март-апрель я сходила примерно на 30 собесов. Это оказалось очень интенсивно и стрессово. И вот как бы я описала рынок труда на 2026 год 😱: IT бизнесы очень требовательные и амбициозно заряженные, но при этом у них мало прозрачности, они юлят, недоговаривают, и ставят кандидатов в неудобное положение, оценивая не только их профессиональные навыки, но и жизнь целиком (это я про планы на рождени…

❤16custom 54043370677212365008custom 53348827607355983744

4 May 2026, 12:10 UTC132 views15 reactionsread 13 August 2026

Photo

Наманифестировала себе прайм эру в этом году Клянусь начало работать, как только стали появляться мысли в голове, что можно жить классную жизнь. Потом уже стали происходить события, по которым с уверенностью могу сказать, что прайм эра здесь, она с нами в одной комнате, и это не дурной знак!! 🟡Апдейты по жизни: Мы прожили чудесный месяц в Гданьске, я даже сходила к двум врачам, сдала анализы, насладилась дешевыми ц…

❤10custom 54043370677212365005

4 Apr 2026, 19:23 UTC206 views36 reactionsread 13 August 2026

Photo

Диверсифицируем риски Здравствуйте привет всем! Давно не появлялась в этом чате, пришла рассказать как продвигаются дела в жизни и карьере. 1️⃣Во-первых, мы с мужем наконец-то приняли статус кочевников и начали наслаждаться частой сменой локации. Аж гора с плеч. Ничего специально для этого не делали. Я в какой-то день проснулась и поняла, что мне надоело тревожится о будущем, хочу сужать картинку до максимально воз…

❤23custom 52559823732620741029custom 54043370677212365004

Showing the 5 most recent of 5 posts we hold for @ghostwriterliza. 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,408,774 of 1,480,944entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Лес рук!
@lesrukmedia · 1,8711 post

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.

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.

Реклама «Лес рук!»
@lesruk_pr · 21 post

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

“Черновик гострайтера” (@ghostwriterliza), 178 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ghostwriterliza.

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.