22.09.2026 Мы муж и жена ❤️
👍144,000💩7,190

Channel
@exilemusic13
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cross-platform identity · Cite this entry
1,445,701subscribers
+22,472 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001411855586 |
|---|---|
| Type | Channel |
| Username | @exilemusic13 |
| Created | 25 May 2020 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/exilemusic13 |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 39% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
966,000 average views per post against 1,445,976 subscribers — an engagement rate of 66.8%. Across the 399 registered channels in the same cohort — 1,001,501–14,360,001 subscribers — the middle half sit between 0.876% and 7.71%, with a median of 2.77%.
| Window | 30 days (26 August 2026 – 25 September 2026) |
|---|---|
| Posts measured | 19 of 19 published in the window (0 exact, 19 rounded by Telegram) |
| Views totalled | 18,347,000 |
| Mature posts only | 66.8% over 19 posts read at least 24h after publication |
| Subscribers | 1,445,976 measured 19 September 2026 |
| Cohort | b1000000 · 399 channels · p10 0.149% · p25 0.876% · p50 2.77% · p75 7.71% · p90 15.0% |
| Position in cohort | 100.000th percentile · 24.1× the cohort median |
| Uncertainty | ±0.204% of the figure, from Telegram’s rounding |
| Post language | Russian · 100.0% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 25 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 11:42 | 1,445,701 | -275 |
| 19 Sept 2026, 03:21 | 1,445,976 | -289 |
| 16 Sept 2026, 17:55 | 1,446,265 | -653 |
| 14 Sept 2026, 19:02 | 1,446,918 | +641 |
| 13 Sept 2026, 02:21 | 1,446,277 | +16,340 |
| 11 Sept 2026, 05:58 | 1,429,937 | +6,027 |
| 8 Sept 2026, 07:14 | 1,423,910 | -359 |
| 5 Sept 2026, 01:00 | 1,424,269 | -312 |
| 3 Sept 2026, 09:48 | 1,424,581 | -387 |
| 2 Sept 2026, 01:44 | 1,424,968 | -540 |
| 1 Sept 2026, 00:44 | 1,425,508 | -449 |
| 30 Aug 2026, 22:08 | 1,425,957 | -157 |
| 30 Aug 2026, 00:46 | 1,426,114 | -157 |
| 28 Aug 2026, 23:14 | 1,426,271 | -92 |
| 28 Aug 2026, 00:24 | 1,426,363 | +136 |
| 26 Aug 2026, 22:23 | 1,426,227 | -117 |
| 25 Aug 2026, 22:08 | 1,426,344 | +463 |
| 24 Aug 2026, 23:12 | 1,425,881 | +1,169 |
| 23 Aug 2026, 11:04 | 1,424,712 | +174 |
| 21 Aug 2026, 20:38 | 1,424,538 | first reading |
2,225 posts held, back to 25 May 2020 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 263 pages of 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 22 September 2026 |
|---|---|
| Posts held | 2,225 (25 May 2020 – 22 September 2026) |
| Views total | 17,326,000 |
| Reactions total | 1,068,190 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Sept 2026, 15:05 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 4 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 15 of this channel’s own posts over the last 30 days (2 of the 24-hour readings behind this are interpolated, not measured directly): across 15 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 19 hours of being posted; a typical post has already reached 42.8% of its 24-hour view count within the first hour, and 75.8% within the first six; the median 24-hour reach across those posts is 459,000 views — 31.7% of this channel’s own subscriber count (90th percentile 540,600).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /289019 Sept 2026, 15:31 UTC | 2518 minutes – 6 days old | 761,000 views ~36,050 reactions | 60 minutes: 169,690 interp. → 3.0 hours: 220,231 interp. → 6.0 hours: 245,476 interp. → 12 hours: 295,968 interp. → 24 hours: 444,902 interp. → 2 days: 555,000still climbing at last reading | 444,902interpolated | 19 hours |
| /288919 Sept 2026, 13:41 UTC | 279 minutes – 6 days old | 747,000 views ~80,930 reactions | 60 minutes: 209,175 interp. → 3.0 hours: 338,000 → 6.0 hours: 370,092 interp. → 12 hours: 403,258 interp. → 24 hours: 488,194 interp. → 2 days: 569,693 interp.views have flattened out | 488,194interpolated | 6.6 hours |
| /288816 Sept 2026, 15:25 UTC | 9160 minutes – 8 days old | 902,000 views ~27,050 reactions | 60 minutes: 226,000 → 3.0 hours: 311,759 interp. → 6.0 hours: 355,000 → 12 hours: 379,000 → 24 hours: 439,000 → 2 days: 479,000 → 7 days: 889,000still climbing at last reading | 439,000measured | 28 hours |
| /288516 Sept 2026, 10:46 UTC | 944 minutes – 8 days old | 917,000 views ~45,110 reactions | 60 minutes: 219,549 interp. → 3.0 hours: 318,000 → 6.0 hours: 444,000 → 12 hours: 493,000 → 24 hours: 525,000 → 2 days: 561,000 → 7 days: 892,000still climbing at last reading | 525,000measured | 7.1 hours |
| /288415 Sept 2026, 14:18 UTC | 10937 minutes – 9 days old | 941,000 views ~82,800 reactions | 60 minutes: 229,107 interp. → 3.0 hours: 322,000 → 6.0 hours: 382,000 → 12 hours: 407,000 → 24 hours: 551,000 → 2 days: 643,000 → 7 days: 908,000still climbing at last reading | 551,000measured | 21 hours |
| /288311 Sept 2026, 12:35 UTC | 1379 minutes – 7 days old | 1,360,000 views ~156,200 reactions | 60 minutes: 305,000 → 3.0 hours: 462,000 → 6.0 hours: 563,000 → 12 hours: 646,000 → 24 hours: 707,000 → 2 days: 761,000 → 7 days: 1,360,000still climbing at last reading | 707,000measured | 19 hours |
| /28829 Sept 2026, 11:11 UTC | 16354 minutes – 7 days old | 1,060,000 views ~28,800 reactions | 60 minutes: 171,713 interp. → 3.0 hours: 254,000 → 6.0 hours: 300,000 → 12 hours: 335,000 → 24 hours: 365,000 → 2 days: 453,000 → 7 days: 1,060,000still climbing at last reading | 365,000measured | 2 days |
| /28818 Sept 2026, 05:34 UTC | 15562 minutes – 7 days old | 938,000 views ~131,900 reactions | 60 minutes: 196,000 → 3.0 hours: 307,000 → 6.0 hours: 383,000 → 12 hours: 458,000 → 24 hours: 494,000 → 2 days: 580,000 → 7 days: 938,000still climbing at last reading | 494,000measured | 14 hours |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
1,889,270 reactions across 36 posts, in 2 distinct kinds. The most used accounts for 80.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,517,620 | 80.3% | |
| 💩 | 371,650 | 19.7% |
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 991 of the 1,000 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 36,352,453 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 11 June 2023 to 22 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @exilemusic13. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 11 June 2023 to 22 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2SDnjda9CRx | 1 | 10 July 2024 | 10 July 2024 |
| 2SDnjexEDHV | 1 | 30 October 2024 | 30 October 2024 |
| 2Vtzqv8LjLd | 1 | 24 June 2026 | 24 June 2026 |
| 2VtzqwFsHbu | 1 | 6 November 2023 | 6 November 2023 |
| 2Vtzqx4x9eC | 1 | 19 August 2024 | 19 August 2024 |
| 2W5zFGnWZ8t | 1 | 18 March 2025 | 18 March 2025 |
| 2W5zFH3NVtU | 1 | 6 August 2025 | 6 August 2025 |
| 2W5zFH8qCGZ | 1 | 30 April 2026 | 30 April 2026 |
| 2W5zFH8qX9A | 1 | 4 March 2025 | 4 March 2025 |
| 2W5zFHDJrSC | 1 | 14 May 2025 | 14 May 2025 |
| 2W5zFHDinGY | 1 | 24 November 2025 | 24 November 2025 |
| 2W5zFHT9dzh | 1 | 26 June 2026 | 26 June 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it. 16 further tokens are held for this entry and not listed here.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 11 June 2023 to 22 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
22.09.2026 Мы муж и жена ❤️
👍144,000💩7,190
Вы не представляете с какими костылями я каждый раз пополнял кошелек в эпсторе А менять регион принципиально не хочу - исчезает дофига нужных мне приложений, что совсем неудобно + теряются уже текущие покупки и подписки. И переходя на другую страну, меняется стоимость самих подписок, далеко не всегда в лучшую сторону Все эти танцы с бубнами были до того, как я узнал про пополнение через приложение Альфа-Банка: 🔴 Зах…
👍9,820💩1,320
Мне Марвел прислал не вошедший момент с человека паука
👍41,200💩3,030
Прятки в парке развлечений! Всем смотреть! https://youtu.be/YqMRXdZBD_I
👍33,500💩2,550
Сегодня выходят прятки! 👍 - очень жду
👍75,900💩5,030
НАКОНЕЦ-ТО! Вышел ролик на игровом канале, попробую сохранить тенденцию выкладки там! Думаю вам очень понравится, легендарные гоночки! Смотреть: https://www.youtube.com/watch?v=BeAJRo_Aw2A
👍22,800💩4,250
На случай важных переговоров…
👍40,200💩4,920
Video message, posted without a caption
👍55,300💩27,600
Все таки решился… https://youtu.be/yotWaAT4jrg?is=QIV7HOlYWi4vyv_B
💩86,600👍71,400
Вышла вторая часть КУБОВ со зрителями ! С небольшим запозданием…. Спасибо за ваше ожидание ❤️ Финал Сражения За 1 000 000 ! Битва Кубов ! (feat. ФрамеТамер + SECRET GUEST) Кстати, участниками этого видео были абоненты ДОБРОСВЯЗЬ , именно благодаря этому они попали в видео, подключайся и имей возможность попасть в одну из легендарных рубрик! https://youtu.be/33G7m_gwpIw
👍23,300💩6,370
Я всегда придерживался правила, что выяснять личные отношения в интернете нельзя, но раз уж столько неоправданных слов летит в адреса всех сторон, дам свой комментарий касательно всего этого Уж простите, что вы стали затянуты в эту всю историю и испытываете не самые лучшие эмоции Безусловно Саша - это часть канала, его никто не стирал из истории и делать этого не будет. Он мой близкий друг, которого я очень ценю и …
👍121,000💩12,400
Раз, два, три, четыре, пять - экзамены идут тебя искать ! 🫣 Прятаться бессмысленно, а вот готовиться в ЕГЭLAND - самое умное решение 😎 Уже не первый раз советую подготовку с этими ребятами, ведь они сделают всё для вашего результата. Смотрите сами: 74.000 выпускников этой школы уже сдали ЕГЭ на 80+ баллов. А еще они бесплатно помогают набрать до 10 доп. баллов при поступлении в ВУЗ, помимо ЕГЭ. Уже 1.000 их выпуск…
👍10,400💩5,020
Showing the 12 most recent of 2,225 posts we hold for @exilemusic13. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@exilemusic13 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.
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 37 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@exilemusic13 named 30 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1,061 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
23 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | Exile |
|---|---|
| Description | Russian content creator |
| YouTube | UC6JRrn_7Qe1CZBcQDMieadw |
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Exile” (@exilemusic13), 1,445,701 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/exilemusic13.
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.