Channel
@Ashen_Frontline
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
139subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001771069894 |
|---|---|
| Type | Channel |
| Username | @Ashen_Frontline |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/Ashen_Frontline |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 11:16 | 139 | -2 |
| 15 Aug 2026, 04:34 | 141 | +2 |
| 8 Aug 2026, 22:46 | 139 | no change |
| 7 Aug 2026, 16:55 | 139 | first reading |
19 posts held, back to 15 March 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 pageof 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 19 posts for this entry, the most recent from 17 June 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.
30 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 63.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5465262274031659421 | 19 | 63.3% | |
| custom 5465465194056525619 | 6 | 20.0% | |
| custom 5228962845672096235 | 5 | 16.7% |
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 19 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 30reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 15 March 2026 to 17 June 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.
Всем здравствуйте дорогие подписчики, спустя такое количество времени Я- Спартан(а в прошлом менделеев) вернулся к вам и всё изза блокировок,надеюсь что вы будете рады новым спойлерам и тд которые я буду вдвойне усерднее делать для вас)
custom 52289628456720962355custom 54652622740316594213custom 54654651940565256193
Signed ᅠᅠᅠᅠᅠᅠᅠᅠ
Тест сборки от знакомого
custom 54652622740316594213
По тестам сервер станет максимально хардкорным и страшным. На данном этапе борьба даже с одиночными врагами становится крайне опасной: при плохом парировании вы можете заразиться инфекцией. Просто стоять и зажимать кнопку удара не получится. Вы замахиваетесь оружием, и если пропустите тайминг, вас укусят.
Photo, posted without a caption
custom 54652622740316594214
Server | Ashen Frontline pinned «»
Забавный факт, на втором альфа тесте люди наиграли в мире на размер в 9гб
Photo, posted without a caption
custom 54652622740316594215
Photo, posted without a caption
Photo, posted without a caption
custom 54652622740316594214
Photo, posted without a caption
Сегодня были выданы премии сотрудникам проекта Dark Haven игры сс14
Всем привет подписчики, с вами ваш админ Spartan-141 в прошлом Менделеев, хочу поздравить вас с наступающей Пасхой и сказать что работа над проектом продолжается и к лету возможно ещё 1 тестирование
custom 54654651940565256193
Signed ᅠᅠᅠᅠᅠᅠᅠᅠ
Showing the 12 most recent of 19 posts we hold for @Ashen_Frontline. 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 — 1,528,954 of 1,620,455entries 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.
Named by 1 registered channel — 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Server | Ashen Frontline” (@Ashen_Frontline), 139 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/Ashen_Frontline.
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.