@zarisovki_lix вы как.. вы тоже как миленький котик, который спит.
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.

Channel
@zarisovki_lix
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
292subscribers
-8 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003734528176 |
|---|---|
| Type | Channel |
| Username | @zarisovki_lix |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/zarisovki_lix |
Art & design — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 15:19 | 292 | -10 |
| 24 Aug 2026, 14:16 | 302 | -4 |
| 16 Aug 2026, 21:35 | 306 | +4 |
| 8 Aug 2026, 13:16 | 302 | +2 |
| 8 Aug 2026, 09:04 | 300 | first reading |
17 posts held, back to 6 August 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 17 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
116 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 29.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5222458113407351284 | 34 | 29.3% | |
| custom 5345981085077512309 | 33 | 28.4% | |
| custom 5215363871111420968 | 24 | 20.7% | |
| custom 5305398617702415951 | 15 | 12.9% | |
| custom 5845731874638402913 | 10 | 8.62% |
Custom emoji. Every row above is a 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 14 of the 17 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 6 August 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.
@zarisovki_lix вы как.. вы тоже как миленький котик, который спит.
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
выложу завтра. я очень устал, простите пожалуйста. но чуть больше половины зарисовки я все же написал..
custom 52153638711114209682custom 53459810850775123091
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
давайте типо кучу реакций и коммов, так я пойму что вы прям ждете и напишу ее быстрее..
custom 52224581134073512846
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
🗝️//—spoiler.
custom 534598108507751230917custom 52153638711114209686custom 58457318746384029133custom 52224581134073512841
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
напишу вам хорни хенли седня.
custom 58457318746384029134custom 52153638711114209683custom 53053986177024159511
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
МЕНЯ НЕ ЖДИТЕ ЗАВТРА.
custom 53459810850775123095custom 58457318746384029131
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
альбом прослушал, 143 раза умер.
custom 53459810850775123099
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
ЕБЕН БОБЕН. ВЫ ЧО СДЕЛАЛИ. Я ТЕПЕРЬ В ГРОБУ БЕЗ ГЛОТКИ.
custom 530539861770241595114
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
а ну да, ебите меня сколько хотите, но я не хочу вставать завтра в 7 утра чтобы послушать новый альбом. честно, я лучше «высплюсь» и послушаю альбом в кайфе, чем встану ранним утром и буду с ватной, нихуя непонимающей бошкой пытаться чето послушать…
custom 52153638711114209689custom 52224581134073512842custom 53459810850775123091
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
годы идут, а я все еще в песне double life слышу голос феликса.
custom 52224581134073512842custom 58457318746384029132
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
погодите. я сплю? вас 300…?
custom 52224581134073512843custom 52153638711114209682
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
пупупу… чет я ничего не писал еще.. попробую завтра написать шо нибудь👉🏻👈🏻
Signed 𝙪𝙣𝙘𝙡𝙚 𝙡𝙞𝙭/𝙧𝙪𝙣 𝙞𝙩 #𝙖𝙪𝙩𝙝𝙤𝙧.
Showing the 12 most recent of 17 posts we hold for @zarisovki_lix. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“ушел/ѡɼɩʈϱѕ ƒɼσɱ υɳϲɭϱ ɭɩχ.” (@zarisovki_lix), 292 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/zarisovki_lix.
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.