Channel
@lissikkss
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
190subscribers
+5 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001544018625 |
|---|---|
| Type | Channel |
| Username | @lissikkss |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/lissikkss |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 17:56 | 190 | +1 |
| 3 Sept 2026, 09:03 | 189 | +4 |
| 27 Aug 2026, 00:12 | 185 | no change |
| 26 Aug 2026, 13:31 | 185 | first reading |
7 posts held, back to 30 June 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 7 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos 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.
130 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 23.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5370885787950784128 | 31 | 23.8% | |
| custom 5337275671699790894 | 21 | 16.2% | |
| custom 5231430446117580132 | 20 | 15.4% | |
| custom 5303230767319508834 | 18 | 13.8% | |
| custom 5359418671947075057 | 17 | 13.1% | |
| custom 5440825400471096202 | 9 | 6.92% | |
| 💘 | 9 | 6.92% | |
| 💋 | 5 | 3.85% |
Custom emoji. 6 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 7 of the 7 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 130 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 30 June 2026 to 8 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.
🙋♀️
custom 53372756716997908946custom 52314304461175801324custom 53708857879507841284custom 54408254004710962023💘2custom 53032307673195088342custom 53594186719470750572
Signed лизка
Не забывайте жить❤️
💋2💘1custom 53032307673195088341
Signed лизка
Video, posted without a caption
custom 52314304461175801326custom 53372756716997908945custom 53594186719470750575custom 53032307673195088344custom 53708857879507841284💘2custom 54408254004710962022
Signed лизка
🔍 Найти любимую песню!
Signed лизка
Photo, posted without a caption
custom 53708857879507841286custom 53032307673195088344💘2custom 52314304461175801322custom 53372756716997908942custom 53594186719470750572custom 54408254004710962022💋1
Signed лизка
🤍
custom 53372756716997908948custom 53032307673195088344custom 53708857879507841284custom 52314304461175801323custom 53594186719470750572custom 54408254004710962022
Signed лизка
теперь можно показать себя и с красивой стороны ☺️
custom 537088578795078412813custom 53594186719470750576custom 52314304461175801325custom 53032307673195088343💋2💘2
Signed лизка
Showing the 7 most recent of 7 posts we hold for @lissikkss. 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐥𝐢𝐳𝐢𝐢𝐤𝐬𝐬 🤍” (@lissikkss), 190 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/lissikkss.
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.