Telegram RegisterThe public register of Telegram

Channel

Anlai Yu | косплейная жабка

@anlai_yu

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

372subscribers

+1 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-1001942400113
TypeChannel
Username@anlai_yu
CreatedBetween 1 April 2023 and 31 October 2023— 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/anlai_yu

Growth

371372371.56 August 2026 — 371 subscribers6 August 2026 — 371 subscribers13 August 2026 — 372 subscribers6 August 202613 August 2026
3 measurements spanning 6 days, net +1. 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 371–372 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:24372+1
6 Aug 2026, 20:33371no change
6 Aug 2026, 19:30371first reading

Engagement

11 posts held, back to 2 August 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
37.3%
avg views ÷ 372 subscribers
Avg views / post
139
11 posts measured
Reaction rate
16.2%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 6 August 2026
Posts held11 (2 August 20266 August 2026)
Views total1,527
Reactions total248
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 20:33 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

248 reactions across 11 posts, in 12 distinct kinds. The most used accounts for 22.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54092184440820318905622.6%
custom 53282332322383932103614.5%
🥰3212.9%
❤‍🔥239.27%
🔥228.87%
custom 5289897500910571157208.06%
custom 5368524397751574842176.85%
176.85%
custom 5350381180287983117145.65%
🍓62.42%
🦄41.61%
custom 524454098840744116210.403%

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

Measured over the 11 most recent posts we hold, published 2 August 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.

Recent posts

6 Aug 2026, 18:44 UTC54 views4 reactionsread 6 August 2026
Photo

Когда что-то в костюме не даёт покоя, надо просто это убрать. Не для того я для древнего китайца два исторических лука купила, колчан из кожи заказала и подол ручными швами обошла, чтобы туника на молнию застёгивалась.

❤‍🔥4

6 Aug 2026, 06:40 UTC98 views25 reactionsread 6 August 2026
Photo

Фотощки с Мэджика! Эш сейчас находится на стадии небольшой реставрации, мне захотелось улучшить в ней несколько моментов (добавить подклад к крафту, обновить кожзам и крепления, а лук нуждается в починке). Но я ещё в ней планирую хотя бы раз выступить. И пофоткаться, конечно! (Возможно, не единожды, у меня внезапно огромное желание отснять её и с заменой фона и на улице и вообще костюм заслуживает быть на кадрах со

custom 52898975009105711578custom 53282332322383932108custom 54092184440820318906custom 536852439775157484221

5 Aug 2026, 18:21 UTC110 views18 reactionsread 6 August 2026
Photo

Стопка мягких подушек чехлов для элементов костюма. Бусинам свойственно царапаться друг от друга, поэтому заспидранила наволочки из хлопка с утеплителем на шёлковом подкладе. А для поручей сделала из евы валики, чтобы они не теряли форму. #какпродвигаютсяделавпошиве

🥰8🦄4custom 53282332322383932102custom 52445409884074411621custom 52898975009105711571custom 53685243977515748421custom 54092184440820318901

5 Aug 2026, 06:03 UTC128 views24 reactionsread 6 August 2026
Photo

Phantom Thief F's Scenario Выпал такой редкий шанс! В этом фантастическом письме Дерзкий намёк я нашла - От призрачного вора привет. F the Phantom Thief: @envyg_kun the Journalist: @anlai_yu Ph: @wishnya_channel Help: @badgriefcraft #vocaloid@anlai_yu #phantomthieffscenario@anlai_yu #cosplay@anlai_yu

custom 54092184440820318908custom 53503811802879831177🥰4🍓2custom 53685243977515748422custom 53282332322383932101

4 Aug 2026, 18:18 UTC140 views29 reactionsread 6 August 2026
Photo

Ребята!!!! (Я отнесу его подрезать... а может, и нет, он прекрасен)

🔥19🍓4custom 54092184440820318904custom 53282332322383932101custom 53685243977515748421

3 Aug 2026, 11:02 UTC159 views35 reactionsread 6 August 2026
Photo

🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 И долго, долго лежала Белоснежка в гробу и не изменялась, и казалась как бы спящею, и была по-прежнему бела, как снег, румяна, как кровь, чернява, как черное дерево. Но залетела в лес чёрная птица, клюнула руку Белоснежки и вспорхнула. Тотчас открыла она вновь глаза, и сначала понемногу, затем и совсем ожила. Ph: @morpheevaphotography Edit: Masky Inspired by @irenhorrorsart #белоснежка@anlai_yu #cospla

🥰12custom 528989750091057115711custom 53503811802879831177🔥3custom 53282332322383932101custom 54092184440820318901

2 Aug 2026, 16:58 UTC166 views45 reactionsread 6 August 2026
Photo

🔠🔠🔠🔠🔠 🔠🔠 🔠🔠🔠🔠🔠 — Аврора, что значит принцесса? — Дочь королевы. — Интересно! Ph: @lust_ik #childoflight@anlai_yu #aurora@anlai_yu #cosplay@anlai_yu

❤‍🔥19custom 540921844408203189016🥰8custom 53282332322383932101custom 53685243977515748421

2 Aug 2026, 16:58 UTC158 views14 reactionsread 6 August 2026

На Индикон мою Аврору не взяли, восприму это как повод выложить ещё одну фоточку с фотосета :3

7custom 53282332322383932103custom 54092184440820318903custom 53685243977515748421

2 Aug 2026, 10:52 UTC161 views21 reactionsread 6 August 2026
Photo

Я в любви к этому сочетанию текстур

custom 532823323223839321012custom 54092184440820318906custom 53685243977515748423

2 Aug 2026, 10:49 UTC171 views16 reactionsread 6 August 2026

С этим костюмом я наконец полюбила натуральные ткани. Оказалось, что бязь шикарна в роли подклада, дорогие хлопковые косые бейки не уступают синтетическим, а дико сыпучий край это не так страшно. Рубаху на Невесту Полоза я тоже шила из крапивы, но её спидранила на энтузиазме и не успела прочувствовать весь кайф. А раньше я старательно избегала всего сыпучего и либо брала трикотаж либо страдала.

custom 54092184440820318908custom 53685243977515748425custom 53282332322383932103

2 Aug 2026, 10:42 UTC182 views17 reactionsread 6 August 2026
Photo

Парогенератор сломался, потому я не могу пока декатировать следующий отрез ткани и разрешила себе посидеть подольше с воротником. Нашила вручную узкий воротник, сделала красивую изнанку, подшила полупотайным швом рукава. Верхняя часть туники готова, но у неё ещё будет отрезная юбка. Молния здесь по очень простой причине: я не нашла застёжки лучше. В оригинале нет ни пуговиц, ни нахлёста ни других застёжек. Так что п

9custom 53282332322383932104custom 54092184440820318903custom 53685243977515748421

Showing the 11 most recent of 11 posts we hold for @anlai_yu. 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 — 95,676 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.

Forward network

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

“Anlai Yu | косплейная жабка” (@anlai_yu), 372 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/anlai_yu.

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.