6 measurements spanning 33 days, net +5. 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 158–166 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Sept 2026, 11:37
164
-1
1 Sept 2026, 23:17
165
+1
25 Aug 2026, 01:48
164
+1
17 Aug 2026, 09:27
163
+4
10 Aug 2026, 17:31
159
no change
9 Aug 2026, 20:16
159
first reading
Engagement
6 posts held, back to 19 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 6 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
121 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 37.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
45
37.2%
💋
30
24.8%
💘
18
14.9%
😍
18
14.9%
🍓
9
7.44%
❤🔥
1
0.826%
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 6 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 121 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 19 July 2026 to 29 July 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.
Я сейчас нахожусь в отъезде, поэтому мне нужно время чтобы наладить постинг, сорри за тишину 🐌
В вк постараюсь в ближайшее время закинуть посты в отложку, тг возможно так и простоит до осени, пока я снова не буду дома с возможностью рисования
#инфо@loneshiy
Ну-с, наша летняя гача прошла на этой неделе! Продублирую пост с ребятами и сюда 💥💥💥
Мой столбец был под номером 1, итого: А1 - золотой призрак капитана пиратов; Б1 - русалочка, основанная на спиральной ракушке; В1 - кельпи по мотивам коктейля "Цитрусовый бриз"; Г1 - морская овечка; Д1 - понификация репейника; Е1 - фруктовая пони кивано!
Это было безумно интересно придумывать персонажей на темы, которые мы выбрали п…
Редизайн и перевод, довольно масштабный ихих
В вк в альбомах я сразу заливаю все работы, поэтому если Вам интересно, можете время от времени проверять там и смотреть комментари: я стараюсь всегда прикреплять версии до!
#кмм@loneshiy #база@loneshiy #кастом@loneshiy
Большая пачка заказов: переводы, редизайны! Оч довольна всеми работками, ищу силы продолжить работу над заказами после практики
Пьеро с нуля :з
#кмм@loneshiy #база@loneshiy #база@loneshiy #кастом@loneshi
Трейдец 1/3 с Varla Gimler
Пока просто полнорост ихих
#трейд@loneshiy #база@loneshiy #кастом@loneshiy
😍9❤7💘3🍓1💋1
Showing the 6 most recent of 6 posts we hold for @loneshiy. 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.
Mentions
Named by 2 registered channels — 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 11 September 2026 — this
entry's latest reading, not the date you are reading this.
“loneshiy” (@loneshiy), 164 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/loneshiy.
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.