Telegram RegisterThe public register of Telegram

Channel

<<🍰𝚑𝚘𝚞𝚜𝚎 𝚕𝚒𝚌𝚑𝚒𝚒🍓!>>

@lichiimi34

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

34subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003034601762
TypeChannel
Username@lichiimi34
Description᥈ᥴ ᥲⲃⲧ𐔖ρᥲ ⲕᥲⲏᥲ᥈ᥲ: @lichii34
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/lichiimi34

Growth

349 August 2026 — 34 subscribers11 August 2026 — 34 subscribers9 August 202611 August 2026
2 measurements spanning 2 days. 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 33–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 00:0134no change
9 Aug 2026, 09:1534first reading

Engagement

20 posts held, back to 15 July 2026the 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.

ERR · 30 days
280.2%
avg views ÷ 34 subscribers
Avg views / post
95.3
19 posts measured
Reaction rate
4.09%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

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. It is computed over the 18 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (15 July 20266 August 2026)
Views total1,810
Reactions total71
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 00:01 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.

What this channel posts

Photos
11
Videos
14
Links
10

Lifetime counters from Telegram’s own channel header, read 11 August 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.

Reaction mix

71 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 12.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5274207079140173279912.7%
custom 5330351845116246700912.7%
❤‍🔥912.7%
custom 538189189504987954968.45%
custom 538225888712041980468.45%
🔥68.45%
57.04%
💋57.04%
custom 543363349491381555245.63%
🍓45.63%
custom 538873715379668191334.23%
custom 527634840380507275722.82%
💘22.82%
custom 540017223793430982511.41%

Custom emoji. 8 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 18 of the 20 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 71reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 15 July 2026 to 6 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 19 we hold a reading for · 11%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lichiimi34. 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 20 most recent posts we hold for this entry, published 15 July 2026 to 6 August 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.

Recent posts

6 Aug 2026, 16:57 UTC44 views2 reactionsread 11 August 2026

кто подпишется, получит потом мини презент

❤‍🔥2

6 Aug 2026, 16:50 UTC44 views1 reactionsread 11 August 2026

друзья, в ходе с очередной проблемой с тт, опять новый акк: lichiime34. всех ждууу

❤‍🔥1

2 Aug 2026, 17:54 UTC44 views2 reactionsread 11 August 2026
Forwarded from @lunamoonshade

👽🧦™️🦄🛼🥑🐈™️🪀🍷 Представь, что мы делаем с тобой парный косплей. Кого будем делать и почему? 👁 Или кем ты меня видишь в пару к уже своему сделанному образу? 😇

💋2

31 Jul 2026, 15:56 UTC542 views5 reactionsread 11 August 2026
Photo

🤩🤩🤩 🤩🤩🤩🌸🌸🌸🌸🌸 🤩🤩. 🌟 🤍𐔖ⳝρыύ ⲇᥱⲏь, ⲇᥲⲙы υ 𐔏𐔖ᥴᥒ𐔖ⲇᥲ. ⲃᥲᥴ ᥒρυⲃᥱⲧᥴⲧⲃ𐔤ᥱⲧ ᥈υɥυ υ ⲕ᥈υ𐔖. ⲃ ⲇᥲⲏⲏ𐔖ⲙ ᥒ𐔖ᥴⲧᥱ ⲃы ⲙ𐔖ⲿᥱⲧᥱ 𐔖ⳅⲏᥲⲕ𐔖ⲙυⲧьᥴя ᥴ ᥲⲏ𐔖ⲏᥴ𐔖ⲙ ᥒυⲕⲏυⲕᥲ🤩 🤩🤍ᥲⲧᥲ ᥒρ𐔖ⲃᥱⲇᥱⲏυя - 9 ᥲⲃ𐔏𐔤ᥴⲧᥲ. ⲃρᥱⲙя ᥒρ𐔖ⲃᥱⲇᥱⲏυя υ ⲙᥱᥴⲧ𐔖? ⲙᥱᥴⲧ𐔖: υᥱρ𐔤ᥴᥲ᥈υⲙᥴⲕᥲя 𐔏𐔖ρᥲ, ⲕ𐔖ⲏⲕρᥱⲧⲏ𐔤ю ⲧ𐔖ɥⲕ𐔤 ⲕυⲏᥱⲙ ⳝ᥈υⲿᥱ ⲕ ᥴⲭ𐔖ⲇⲕᥱ!!>> ⲃρᥱⲙя: 13:30 🤩🤩 🌟🌟🤍ᥲ ⲏᥲɯᥱⲙ ᥒυⲕⲏυⲕᥱ ⲃы ⲙ𐔖ⲿᥱⲧᥱ ᥒ𐔖𐔤ɥᥲᥴⲧⲃ𐔖ⲃᥲⲧь ⲃ ρᥲⳅ᥈υɥⲏыⲭ ⲕ𐔖ⲏⲕ𐔤ρᥴᥲⲭ(ᥴ ⲙυⲏυ ᥒρυⳅᥲⲙυ, ⲏᥲ ⳝ𐔖᥈ьɯυᥱ ⲇᥱ

custom 53303518451162467003❤‍🔥1custom 53822588871204198041

29 Jul 2026, 17:25 UTC78 views1 reactionsread 11 August 2026

давайте в коммах напишете, кого вы бы хотели видеть?🤩

custom 53818918950498795491

29 Jul 2026, 09:01 UTC81 views4 reactionsread 11 August 2026
Photo

💗🌸🌸🌸🌸🌸🌸🌸🌸💘 🤩🤩 🤩ρυⲏυⲙᥲю ⲉᥴⲧᥲⲫᥱⲧ𐔤 𐔖ⲧ ᥒρᥱⲕρᥲᥴⲏ𐔖ύ υ ᥈юⳝυⲙ𐔖ύ ⲕ᥈υ𐔖! 🤩🤩🤩🤩🤩🤩🤩🤩🤩 ᥴ𐔤ⲧь ⲉᥴⲧᥲⲫᥱⲧы ᥴⲇᥱ᥈ᥲⲧь ⲉᥴⲧᥱⲧυɥⲏыύ ⲕ𐔖᥈᥈ᥲⲿ ᥴ ᥒᥱρᥴ𐔖ⲏᥲⲿᥱⲙ, ⲕ𐔖ⲧ𐔖ρ𐔖𐔏𐔖 ⲃы ᥒ𐔖ᥴ᥈ᥱⲇⲏᥱ𐔏𐔖 ⲕ𐔖ᥴᥒ᥈ᥱυ᥈υ🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩 ⲭ𐔖ɥ𐔤 ᥒᥱρᥱⲇᥲⲧь ⲉᥴⲧᥲⲫᥱⲧ𐔤 ᥒρᥱⲕρᥲᥴⲏ𐔖ύ яⲏⲧᥲρь. (˶˃ ᵕ ˂˶)

custom 52742070791401732792custom 53822588871204198041custom 53887371537966819131

29 Jul 2026, 05:17 UTC73 viewsread 11 August 2026

5 реакций есстт. ждем подписчиков. хехехе💌

28 Jul 2026, 16:25 UTC75 views10 reactionsread 11 August 2026

давайте на 35 подписчиков в тгк/15 подписчиков в тт, и 5 реакций на этот пост = я палю следующий косплей?🥹

❤‍🔥4custom 52742070791401732794🍓2

28 Jul 2026, 12:57 UTC68 views5 reactionsread 11 August 2026
Photo

🤩🌸🌸🌸🌸🌸🌸🌸🤩 🤍ᥲⲙыᥱ ⳝ᥈υⲿᥲύɯυᥱ: ⲙυⳅυ - ᥲᥣιᥱᥒ ᥲᥒᦔ z𐔖ⲙbιᥱ ᥉tᥲⳋᥱ ⲕᥲⲏᥲ - ⳅⲃᥱⳅⲇⲏ𐔖ᥱ ⲇυⲧя 🤍ᥲ᥈ьⲏυᥱ: ⲏ𐔖ɥⲏ𐔖ύ ⲇ𐔖ⳅ𐔖ρ - ιᦔᥱᥒιtι ᥎ ᥲ𐔏ᥲᥒᥱ - ᥉htᦔᥒ 🤍𐔖ⳅⲙ𐔖ⲿⲏыᥱ: ⳝυⳝυ - я ᥈юⳝ᥈ю ⲉⲙυ ⲃᥲⲏυ᥈᥈ᥲ ⲕ𐔤ⲕυ - ⲕ𐔤ⲕυ ρᥲⲏ ☕️☕️

custom 53303518451162467002❤‍🔥1custom 53818918950498795491custom 53887371537966819131

28 Jul 2026, 12:26 UTC56 views3 reactionsread 11 August 2026

нас снова 33, котята🥹🥹

custom 52742070791401732791custom 53818918950498795491custom 53887371537966819131

Showing the 12 most recent of 20 posts we hold for @lichiimi34. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

26 Jul 2026, 14:35 UTCFinal Results9 voters

аву и название оставляем с голубым или делаем розовым?

  1. голубой44%
  2. розовый78%

The shares total 122%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 15 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 315,692 of 1,160,990entries 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.

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 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.

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

“<<🍰𝚑𝚘𝚞𝚜𝚎 𝚕𝚒𝚌𝚑𝚒𝚒🍓!>>” (@lichiimi34), 34 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/lichiimi34.

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.