Channel
@lich3n
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
127subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001615852345 |
|---|---|
| Type | Channel |
| Username | @lich3n |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/lich3n |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 20:01 | 127 | -1 |
| 16 Aug 2026, 21:03 | 128 | +1 |
| 9 Aug 2026, 02:15 | 127 | no change |
| 8 Aug 2026, 04:15 | 127 | first reading |
7 posts held, back to 1 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 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 1 video 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.
52 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 26.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5341284100252639082 | 14 | 26.9% | |
| custom 5316919541056420954 | 12 | 23.1% | |
| custom 5197616619567720189 | 9 | 17.3% | |
| custom 5388587869323410644 | 6 | 11.5% | |
| ❤ | 6 | 11.5% | |
| custom 5208893885132055170 | 3 | 5.77% | |
| 👍 | 1 | 1.92% | |
| 🔥 | 1 | 1.92% |
Custom emoji. 5 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 52 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 1 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.
🌟✏️✏️✏️✏️✏️✏️✏️ 🤩🤩🤩🤩🤩🤩🤩🤩 [𝕿𝖍𝖊 𝕻𝖍𝖆𝖓𝖙𝖔𝖒 𝖔𝖋 𝖙𝖍𝖊 𝕺𝖕𝖊𝖗𝖆] 𝖒𝖞 𝖋𝖗𝖎𝖊𝖓𝖉𝖘🌟: Tsukasa ~ Sakura ~ Aoi ~ Teru ~ Hanako ~ Nene ~ Natsuhiko 𝕷𝖔𝖛𝖊 𝖞𝖔𝖚!! Рт/реакции/мью??
custom 51976166195677201892custom 53169195410564209541custom 53412841002526390821
Signed ペルデピカル 🦐
Я наконец научилась крутить кудри, не тратя на это 15 часов времени, не задыхаясь от лака и не слепляя руки пенкой с ожогами Вообще он был готов ещё давно, просто сразу упакован, но эбля, пока переделывала вспомнила что не отфоткала💖 Следущий будет Руи, и Боже, секайники неужели закончатся по крайней мере на ближайшие недели
custom 53169195410564209544custom 53412841002526390823custom 53885878693234106443
Signed ペルデピカル 🦐
Posted without readable text
custom 53412841002526390828custom 51976166195677201895custom 53169195410564209544👍1
Signed ペルデピカル 🦐
😳😍😍🙊🙈
❤1
Signed sabri🐒
Погуляли с родимой Впервые за лето практически выбралась в город, и ого, на самом деле получила комплиментов больше, чем осуждающих взглядов от бабок А еще нашла большую версию любимой летучей мыши с сумки, если найду розовую, то клянусь, потрачу все деньги🔫 Потихоньку социолизируюсь, а как у вас проходит последний месяц каникул?
❤5custom 52088938851320551703custom 53169195410564209543custom 51976166195677201892custom 53885878693234106441
Signed ペルデピカル 🦐
Делать?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
custom 53412841002526390822
Signed ペルデピカル 🦐
Меня очень тянет предстоящая коллаба ростикса и хср, что я даже задумалась над косом оттуда чисто для коллабы... Но у меня нет фулл хср коса и возможности купить. НО есть розовая абсолютно ненужная база которая теоретически подойдет Асте. Что думаете? Ебашить, не? Ещё есть желание прибежать так на работу, но мне кажется что меня пошлют лл
custom 53885878693234106442🔥1
Signed ペルデピカル 🦐
Showing the 7 most recent of 7 posts we hold for @lich3n. 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.
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.
Делать?
Shares as published. No per-option vote count is published by Telegram, so none is 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 7 most recent posts we hold, published 1 August 2026 to 8 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 4 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“𝙻𝚒𝚌𝚑𝚎𝚗” (@lich3n), 127 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/lich3n.
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.