Telegram RegisterThe public register of Telegram

Channel

Lycoris Wear

@lycoriswear

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

682subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002133863880
TypeChannel
Username@lycoriswear
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/lycoriswear

Growth

682683682.56 August 2026 — 682 subscribers6 August 2026 — 683 subscribers13 August 2026 — 682 subscribers6 August 202613 August 2026
3 measurements spanning 7 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 682–683 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:24682-1
6 Aug 2026, 18:25683+1
6 Aug 2026, 18:03682first reading

Engagement

6 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
109.1%
avg views ÷ 682 subscribers
Avg views / post
744
4 posts measured
Reaction rate
4.23%
reactions ÷ views · ER floor
Posts in window
4
of 6 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 July 2026
Posts held6 (15 July 202623 July 2026)
Views total2,976
Reactions total126
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:03 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.

Reaction mix

191 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53710923415179838254020.9%
custom 53707043169925934653719.4%
custom 53889685408648170703417.8%
custom 53796278030397883202412.6%
custom 54135771358078211502211.5%
custom 5409046022619965060199.95%
custom 5350406653739049264157.85%

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 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 6 of the 6 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 191reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

23 Jul 2026, 19:32 UTC555 views31 reactionsread 6 August 2026
Photo

🔫 Max Payne 🔫 "They were all dead. The final gunshot was an exclamation mark on everything that had led to this point" 🪡 Дизайн выполнен полностью вышивкой ——————————— • Футболка "Max Payne" Цена - 3290 руб • Худи "Max Payne" Цена - 4490 руб ——————————— 🕷Доступны несколько вариантов футболок (оверсайз обычные и оверсайз варенки) Футболка оверсайз, плотность: 250 г/м² Худи оверсайз, плотность: 350 г/м². Размер

custom 540904602261996506019custom 53796278030397883207custom 54135771358078211504custom 53710923415179838251

21 Jul 2026, 20:32 UTC573 views28 reactionsread 6 August 2026
Photo

🪄 Frieren 🪄 🪡 Дизайн выполнен полностью вышивкой ——————————— • Футболка "Frieren" Цена - 3290 руб • Худи "Frieren" Цена - 4490 руб. ——————————— 🕷Доступны несколько вариантов футболок (оверсайз обычные и оверсайз варенки) Футболка оверсайз, плотность: 250 г/м² Худи оверсайз, плотность: 350 г/м². Размеры в наличии: S, M, L, XL, 2XL. Срок изготовления: 4-6 дней. Доставка: • Самовывоз в Москве. • Доставка по РФ

custom 537109234151798382517custom 53796278030397883205custom 53707043169925934654custom 54135771358078211502

16 Jul 2026, 16:43 UTC958 views34 reactionsread 6 August 2026
Photo

🦋 Persona 3 🦋 “Remember. You will die” 🪡 Дизайн выполнен полностью вышивкой ——————————— • Футболка "Memento Mori" Цена - 3490 руб • Худи "Memento Mori" Цена - 4890 руб. 🕷При покупке сразу двух изделий по "Persona 3 и 5"на второе - скидка 15% ——————————— 🕷Доступны несколько вариантов футболок (оверсайз обычные и оверсайз варенки) Футболка оверсайз, плотность: 250 г/м² Худи оверсайз, плотность: 350 г/м². Разме

custom 538896854086481707015custom 53707043169925934657custom 54135771358078211507custom 53796278030397883204custom 53710923415179838251

16 Jul 2026, 16:33 UTC890 views33 reactionsread 6 August 2026
Photo

🔥 Persona 5 🔥 “It’s showtime!“ 🪡 Дизайн выполнен полностью вышивкой ——————————— • Футболка "Phantom Thieves " Цена - 3290 руб • Худи "Phantom Thieves " Цена - 4490 руб. 🕷При покупке сразу двух изделий по "Persona 3 и 5"на второе - скидка 15% ——————————— 🕷Доступны несколько вариантов футболок (оверсайз обычные и оверсайз варенки) Футболка оверсайз, плотность: 250 г/м² Худи оверсайз, плотность: 350 г/м². Разме

custom 538896854086481707019custom 53796278030397883207custom 53707043169925934655custom 53710923415179838252

15 Jul 2026, 21:27 UTC766 views32 reactionsread 6 August 2026

🕷Примерный график выхода коллекций 16.07 - Persona 3, 5 21 07 - Frieren 23.07 - Max Payne ————————————— ❗️ UPD 05.08 - Arcane 08.08 - The Last Of Us 13.08- Final Fantasy 7 16.08 - Bloodborne #Lycoriswear

custom 537070431699259346515custom 537109234151798382510custom 54135771358078211506custom 53796278030397883201

15 Jul 2026, 12:31 UTC683 views33 reactionsread 6 August 2026
Photo

🫥The Legend Of Zelda 🫥 🪡 Дизайн выполнен полностью вышивкой ——————————— • Футболка "Короки" Цена - 3290 руб • Худи " Короки " Цена — 4490 руб. 🕷При покупке сразу двух изделий по "Зельде"на второе - скидка 15% ——————————— 🕷Доступны несколько вариантов футболок (оверсайз обычные и оверсайз варенки) Футболка оверсайз, плотность: 250 г/м² Худи оверсайз, плотность: 350 г/м². Размеры в наличии: S, M, L, XL, 2XL. С

custom 535040665373904926415custom 53710923415179838259custom 53707043169925934656custom 54135771358078211503

Showing the 6 most recent of 6 posts we hold for @lycoriswear. 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.

Citation-graph rank

Citation-graph rank — 222,853 of 1,478,351entries 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.

Mentions

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

“Lycoris Wear” (@lycoriswear), 682 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/lycoriswear.

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.