это полный эксклюзив вы нигде такое не увидите
🦄49custom 541146632688556702923❤🔥8💘2

Channel
@lizokpomazokomg
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
7,026subscribers
+507 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002324949960 |
|---|---|
| Type | Channel |
| Username | @lizokpomazokomg |
| Description | реклама https://t.me/lalablissa канал с вещами https://t.me/blissacounter сотрудничество/реклама - @nodi_zabivnaya : @atragica @OTKAZ_N3T @heiLyeah3 @meowssmanage @emiicml @diao_PR |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/lizokpomazokomg |
Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 08:59 | 7,026 | -38 |
| 12 Nov 2026, 09:17 | 7,064 | -36 |
| 8 Nov 2026, 04:20 | 7,100 | +30 |
| 5 Nov 2026, 09:59 | 7,070 | -10 |
| 2 Nov 2026, 14:21 | 7,080 | +10 |
| 30 Oct 2026, 06:39 | 7,070 | -7 |
| 27 Oct 2026, 05:30 | 7,077 | -35 |
| 23 Oct 2026, 19:05 | 7,112 | -18 |
| 20 Oct 2026, 09:15 | 7,130 | +4 |
| 17 Oct 2026, 03:11 | 7,126 | +16 |
| 14 Oct 2026, 08:08 | 7,110 | +25 |
| 10 Oct 2026, 22:38 | 7,085 | -42 |
| 4 Oct 2026, 23:18 | 7,127 | +117 |
| 25 Sept 2026, 09:41 | 7,010 | -79 |
| 15 Sept 2026, 06:19 | 7,089 | +3 |
| 11 Sept 2026, 10:01 | 7,086 | -41 |
| 6 Sept 2026, 21:17 | 7,127 | +191 |
| 2 Sept 2026, 08:54 | 6,936 | +10 |
| 30 Aug 2026, 14:25 | 6,926 | +187 |
| 27 Aug 2026, 05:39 | 6,739 | first reading |
58 posts held, back to 30 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 29 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 58 (30 July 2026 – 16 November 2026) |
| Views total | 55,640 |
| Reactions total | 3,536 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 03:07 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 6 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.
10,436 reactions across 58 posts, in 6 distinct kinds. The most used accounts for 55.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5411466326885567029 | 5,837 | 55.9% | |
| 🦄 | 1,444 | 13.8% | |
| custom 5454226188060880624 | 1,230 | 11.8% | |
| 💘 | 893 | 8.56% | |
| 💋 | 540 | 5.17% | |
| ❤🔥 | 492 | 4.71% |
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 58 of the 58 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 10,436 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 58 most recent posts we hold, published 30 July 2026 to 16 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lizokpomazokomg. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 58 most recent posts we hold for this entry, published 30 July 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 1 of 19 posts held from the last 30 days (5.26%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
это полный эксклюзив вы нигде такое не увидите
🦄49custom 541146632688556702923❤🔥8💘2
Video, posted without a caption
custom 541146632688556702943💋14🦄13
Video, posted without a caption
custom 541146632688556702934💋10🦄10
моя дофаминовая покупка в магните 29р!! ещё и пегас попался татушка
🦄107custom 541146632688556702949💋27💘11
ВЛОГ ИЗ СЕКОНДА ТУТ 🍮
custom 541146632688556702934🦄19
я в секондах закупалась на тыщу оч много всего
💘182custom 541146632688556702950🦄37❤🔥4💋2
а почему тут коменты нельзя вдруг кто-то хочет
custom 541146632688556702967💘17❤🔥11🦄6
я больше суток не сплю уже всооо я спать хочу я за печать 2800+- отдала, и у меня прям скучный и корявый получился мне не нравится, хотя мне сказали что хорошо, но мне прям хотелось что-то поинтереснее придумать ну лан ну если бы я изначально знала что делаю брендбук я бы красивее делала и старалась, а нам это уже в конце сказали, когда я все задания на отвалитииии сделала, поэтому брендбук тоже отвали
custom 541146632688556702975❤🔥16💘16🦄3
и так, мой рейтинг кого бы я купила: 1) Клодин, потому что я с детства решила что она моя любимка и мне тут нравится ее неоновый образ 2) Френки. С детства это мой нелюбимый персонаж, НО в этой коллекции мне она очень нравится, необъяснимое чувство какое-то 3) Дракулаура и Лагуна. Как-то на равных, Лагуна хоть и тоже моя любимка, мне не очень нравится ее прическа тут. Дракулаура невероятно красиво выглядит, не могу е…
💋51🦄24custom 541146632688556702921💘4
ребята вы профессионалы, которые все знают, правда ведь
🦄39custom 541146632688556702917💘12
я хочу сейчас распаковать репро рассвет танца, а не делать брендбук бл🤬 учобный а так ваще брендинг и брендбук это интересно и прикольно, но нам как попало его задали и только в конце мы узнали что ОГО нам его делать оказывается а как его печатать кто знает мне завтра нужно распечатьь желательно дёшево 🦄
custom 541146632688556702955💘14🦄14
по некоторым причинам мне пришлось переделать и теперь это ещё абсурднее и невозможнее зато вы точно туда хотите
💘110custom 541146632688556702939❤🔥23🦄5
Showing the 12 most recent of 58 posts we hold for @lizokpomazokomg. 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.
We recorded 3 posts on @lizokpomazokomg as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 3 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“лалаблисса” (@lizokpomazokomg), 7,026 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/lizokpomazokomg.
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.