Channel
@anlai_yu
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
381subscribers
+10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001942400113 |
|---|---|
| Type | Channel |
| Username | @anlai_yu |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/anlai_yu |
Gaming — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 05:18 | 381 | +3 |
| 4 Sept 2026, 04:20 | 378 | +3 |
| 28 Aug 2026, 17:52 | 375 | +2 |
| 20 Aug 2026, 19:58 | 373 | +1 |
| 13 Aug 2026, 01:24 | 372 | +1 |
| 6 Aug 2026, 20:33 | 371 | no change |
| 6 Aug 2026, 19:30 | 371 | first reading |
11 posts held, back to 2 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 11 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
248 reactions across 11 posts, in 12 distinct kinds. The most used accounts for 22.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5409218444082031890 | 56 | 22.6% | |
| custom 5328233232238393210 | 36 | 14.5% | |
| 🥰 | 32 | 12.9% | |
| ❤🔥 | 23 | 9.27% | |
| 🔥 | 22 | 8.87% | |
| custom 5289897500910571157 | 20 | 8.06% | |
| custom 5368524397751574842 | 17 | 6.85% | |
| ❤ | 17 | 6.85% | |
| custom 5350381180287983117 | 14 | 5.65% | |
| 🍓 | 6 | 2.42% | |
| 🦄 | 4 | 1.61% | |
| custom 5244540988407441162 | 1 | 0.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 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 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 248 reactions 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.
Когда что-то в костюме не даёт покоя, надо просто это убрать. Не для того я для древнего китайца два исторических лука купила, колчан из кожи заказала и подол ручными швами обошла, чтобы туника на молнию застёгивалась.
❤🔥4
Фотощки с Мэджика! Эш сейчас находится на стадии небольшой реставрации, мне захотелось улучшить в ней несколько моментов (добавить подклад к крафту, обновить кожзам и крепления, а лук нуждается в починке). Но я ещё в ней планирую хотя бы раз выступить. И пофоткаться, конечно! (Возможно, не единожды, у меня внезапно огромное желание отснять её и с заменой фона и на улице и вообще костюм заслуживает быть на кадрах со …
custom 52898975009105711578custom 53282332322383932108custom 54092184440820318906custom 53685243977515748422❤1
Стопка мягких подушек чехлов для элементов костюма. Бусинам свойственно царапаться друг от друга, поэтому заспидранила наволочки из хлопка с утеплителем на шёлковом подкладе. А для поручей сделала из евы валики, чтобы они не теряли форму. #какпродвигаютсяделавпошиве
🥰8🦄4custom 53282332322383932102custom 52445409884074411621custom 52898975009105711571custom 53685243977515748421custom 54092184440820318901
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
Ребята!!!! (Я отнесу его подрезать... а может, и нет, он прекрасен)
🔥19🍓4custom 54092184440820318904custom 53282332322383932101custom 53685243977515748421
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 И долго, долго лежала Белоснежка в гробу и не изменялась, и казалась как бы спящею, и была по-прежнему бела, как снег, румяна, как кровь, чернява, как черное дерево. Но залетела в лес чёрная птица, клюнула руку Белоснежки и вспорхнула. Тотчас открыла она вновь глаза, и сначала понемногу, затем и совсем ожила. Ph: @morpheevaphotography Edit: Masky Inspired by @irenhorrorsart #белоснежка@anlai_yu #cospla
🥰12custom 528989750091057115711custom 53503811802879831177🔥3custom 53282332322383932101custom 54092184440820318901
🔠🔠🔠🔠🔠 🔠🔠 🔠🔠🔠🔠🔠 — Аврора, что значит принцесса? — Дочь королевы. — Интересно! Ph: @lust_ik #childoflight@anlai_yu #aurora@anlai_yu #cosplay@anlai_yu
❤🔥19custom 540921844408203189016🥰8custom 53282332322383932101custom 53685243977515748421
На Индикон мою Аврору не взяли, восприму это как повод выложить ещё одну фоточку с фотосета :3
❤7custom 53282332322383932103custom 54092184440820318903custom 53685243977515748421
Я в любви к этому сочетанию текстур
custom 532823323223839321012custom 54092184440820318906custom 53685243977515748423
С этим костюмом я наконец полюбила натуральные ткани. Оказалось, что бязь шикарна в роли подклада, дорогие хлопковые косые бейки не уступают синтетическим, а дико сыпучий край это не так страшно. Рубаху на Невесту Полоза я тоже шила из крапивы, но её спидранила на энтузиазме и не успела прочувствовать весь кайф. А раньше я старательно избегала всего сыпучего и либо брала трикотаж либо страдала.
custom 54092184440820318908custom 53685243977515748425custom 53282332322383932103
Парогенератор сломался, потому я не могу пока декатировать следующий отрез ткани и разрешила себе посидеть подольше с воротником. Нашила вручную узкий воротник, сделала красивую изнанку, подшила полупотайным швом рукава. Верхняя часть туники готова, но у неё ещё будет отрезная юбка. Молния здесь по очень простой причине: я не нашла застёжки лучше. В оригинале нет ни пуговиц, ни нахлёста ни других застёжек. Так что п…
❤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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Anlai Yu | косплейная жабка” (@anlai_yu), 381 subscribers as measured 12 September 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.