Поздравляем победителей супер-розыгрыша 🙀 💜 Играть👾#Legacy #Essence #L2
custom 521566554531932175228custom 54700606845092096475custom 52179795792091250404

Channel
@Lineage2Russia
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
12,951subscribers
+52 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001314870049 |
|---|---|
| Type | Channel |
| Username | @Lineage2Russia |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/Lineage2Russia |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 21:44 | 12,951 | -4 |
| 29 Aug 2026, 00:05 | 12,955 | +1 |
| 27 Aug 2026, 23:04 | 12,954 | +2 |
| 27 Aug 2026, 01:36 | 12,952 | -2 |
| 25 Aug 2026, 23:24 | 12,954 | +86 |
| 24 Aug 2026, 22:15 | 12,868 | -1 |
| 23 Aug 2026, 06:27 | 12,869 | -5 |
| 21 Aug 2026, 18:18 | 12,874 | -2 |
| 20 Aug 2026, 13:05 | 12,876 | -7 |
| 19 Aug 2026, 12:12 | 12,883 | -4 |
| 18 Aug 2026, 11:33 | 12,887 | -5 |
| 16 Aug 2026, 03:03 | 12,892 | +5 |
| 14 Aug 2026, 16:06 | 12,887 | -5 |
| 13 Aug 2026, 03:57 | 12,892 | +6 |
| 12 Aug 2026, 06:52 | 12,886 | -5 |
| 11 Aug 2026, 05:46 | 12,891 | -9 |
| 10 Aug 2026, 08:15 | 12,900 | -5 |
| 9 Aug 2026, 05:56 | 12,905 | +6 |
| 8 Aug 2026, 04:32 | 12,899 | -2 |
| 7 Aug 2026, 05:41 | 12,901 | first reading |
61 posts held, back to 28 July 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 42 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 61 (28 July 2026 – 29 August 2026) |
| Views total | 293,230 |
| Reactions total | 1,360 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 19:53 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.
Measured directly from 8 videos 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.
1,510 reactions across 60 posts, in 6 distinct kinds. The most used accounts for 38.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5215665545319321752 | 581 | 38.5% | |
| custom 5339314398185935279 | 250 | 16.6% | |
| custom 5217979579209125040 | 247 | 16.4% | |
| custom 5470060684509209647 | 213 | 14.1% | |
| custom 5470121930742847724 | 122 | 8.08% | |
| custom 5471930352492633487 | 97 | 6.42% |
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 60 of the 61 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 1,510reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 61 most recent posts we hold, published 28 July 2026 to 29 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.
Поздравляем победителей супер-розыгрыша 🙀 💜 Играть👾#Legacy #Essence #L2
custom 521566554531932175228custom 54700606845092096475custom 52179795792091250404
😁 Кука довольна, столько гостей сегодня пришло на встречу в «Мосигра & ОраОра» Успевайте, большой розыгрыш среди покупателей пройдет в 16:00! 💜 Играть👾#Legacy #Essence #L2
custom 547006068450920964726custom 52156655453193217529custom 54719303524926334873
Иногда лучший дроп можно найти в работах подписчиков 🔥 Вот такую Тёмную эльфийку сделала Екатерина! Кукабарра посмотрела и молча поставила лайк двумя головами сразу🥰 И вы не скупитесь на реакции! 💜 Играть👾#Legacy #Essence #L2
custom 547006068450920964735custom 52156655453193217529custom 52179795792091250407
Posted without readable text
custom 521566554531932175215custom 53393143981859352796custom 52179795792091250404
🧐 Дайджест событий О самом важном на этой неделе: Акции и события Lineage 2 ▫️[Акция] Древние раскопки ▫️[Ивент] Пламенная легенда ▫️[Ивент] Календарь подарков Essence ▫️[Акция, Special] Предвестник Бури ▫️[Подарочные наборы, Special] Благодарность Баюма ▫️[Акция, Special] Сияние драгоценностей ▫️[Акция, Essence] Игра Бероа ▫️[Ивент, Все серверы] Путешествие в Сад Бытия ▫️[Ивент, Все серверы] Битва за Гиран Legac…
custom 52156655453193217529custom 52179795792091250402custom 53393143981859352792custom 54719303524926334871
В данный момент из-за высокой нагрузки на платформу наблюдается задержка при доставке товаров из магазина Фогейм и активации подписки на премиум-аккаунт. Мы уже работаем над решением сложившейся ситуации, чтобы как можно скорее вернуться к привычному ритму в Эльморадене. Приносим извинения за временные неудобства. 💜 Играть👾#L2
custom 54719303524926334879custom 52156655453193217523custom 54701219307428477243custom 52179795792091250402custom 53393143981859352792
Офлайн-встреча по Lineage 2 в ЦДМ! 📍 Где: Москва, ЦДМ, магазин «Мосигра & ОраОра», 4 этаж 🕐 Когда: 29 августа, 13:00–18:00 Что вас ждёт: ▫️ косплееры ▫️ значки, шоперы, стаканы и броские стикеры с символикой любимой игры ▫️ большой розыгрыш в 16:00 среди покупателей «Мосигры» ▫️ активности и конкурсы, где можно выиграть новый мерч Специально для подписчиков: ☀️ скажите продавцу кодовую фразу «КУКАБАРРА» и получите…
custom 521566554531932175218custom 53393143981859352799custom 52179795792091250405custom 54719303524926334871
Профилактика в Lineage 2 завершена. Игровые миры вновь доступны 🔥 💜 Играть👾#Legacy #Essence #L2
custom 52156655453193217528custom 53393143981859352793custom 52179795792091250401
Работы на серверах Legacy и Essence окончены. Эльмораден ждет! 💜 Играть👾#Legacy #Essence
custom 52156655453193217529custom 53393143981859352792custom 54700606845092096471
Завтра, 26 августа, серверы будут недоступны в связи с проведением плановых профилактических работ: ▫️10:00 – 12:00 МСК в Legacy ▫️10:00 – 12:00 МСК в Essence & Special ▫️10:00 – 13:00 МСК в Lineage 2 💜 Играть👾#Legacy #Essence #L2
custom 52179795792091250408custom 54700606845092096473custom 52156655453193217521custom 54719303524926334871
Кука пришла с новым видео от разработчиков 🗣 В нём они отвечают на отзывы игроков о последнем обновлении, а также делятся будущими изменениями ▫️ изменения системы иллюзорного снаряжения на Main; ▫️ сложность и награды новых временных зон; ▫️ ближайшие изменения; ▫️ перспективы межсерверных сражений на Essence/Special; Некоторые из них будут в игре уже завтра 🥰 Подробности чуть позже в новости про профилактику По…
custom 52156655453193217528custom 52179795792091250404custom 54701219307428477243
🎉 Результаты розыгрыша: 🏆 Победители: 1. Sergei (@Nightmen777) 2. Евгений (@Dganikus) 3. Евгений (@MostHolyTrinity) ✔️Проверить результаты В течение 7 дней Кукабарра пришлёт победителям промокоды! Спасибо всем за участие 🥰 P.s. Просим победителей открыть свой лс для сообщений
custom 547193035249263348711custom 52156655453193217524custom 53393143981859352793
Showing the 12 most recent of 61 posts we hold for @Lineage2Russia. 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.
@Lineage2Russia edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 76,809 of 1,625,954entries 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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Lineage 2 Russia” (@Lineage2Russia), 12,951 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/Lineage2Russia.
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.