Channel
@excc1se
On this record: Growth · Engagement · Posts · Citations · Cite this entry
744subscribers
+386 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003981866562 |
|---|---|
| Type | Channel |
| Username | @excc1se |
| Created | Between 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/excc1se |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 10:59 | 744 | -42 |
| 26 Aug 2026, 19:43 | 786 | +6 |
| 20 Aug 2026, 12:44 | 780 | +96 |
| 13 Aug 2026, 16:07 | 684 | +249 |
| 6 Aug 2026, 22:51 | 435 | +77 |
| 6 Aug 2026, 21:03 | 358 | no change |
| 6 Aug 2026, 12:03 | 358 | first reading |
20 posts held, back to 6 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.
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 6 August 2026 |
|---|---|
| Posts held | 20 (6 August 2026 – 6 August 2026) |
| Views total | 219 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 21:03 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.
согласно древней легенде, Цветы и Листья ликориса обречены никогда не встречаться — они приходят в разное время, один за другим исчезая, но всё равно вечно скучая друг по другу. такова плата за близкий союз.
согласно древней легенде, Цветы и Листья ликориса обречены никогда не встречаться — они приходят в разное время, один за другим исчезая, но всё равно вечно скучая друг по другу. такова плата за близкий союз.
согласно древней легенде, Цветы и Листья ликориса обречены никогда не встречаться — они приходят в разное время, один за другим исчезая, но всё равно вечно скучая друг по другу. такова плата за близкий союз.
✞ Когда свет угасает — остается лишь то, что связано тьмой. «Omnia in tenebris ligantur.» ✞ @MA1ESTE × @excc1se
согласно древней легенде, Цветы и Листья ликориса обречены никогда не встречаться — они приходят в разное время, один за другим исчезая, но всё равно вечно скучая друг по другу. такова плата за близкий союз. @Vinskynobility & @excc1se
Ⲥ ⲅⲟⲣⲇⲟⲥⲧью υ ⲣⲁⲇⲟⲥⲧью ⲃⲥⲧⲣⲉⳡⲁⲉⲙ ⲏⲁ Ⲟⲗυⲙⲡⲉ @excc1se
согласно древней легенде, Цветы и Листья ликориса обречены никогда не встречаться — они приходят в разное время, один за другим исчезая, но всё равно вечно скучая друг по другу. такова плата за близкий союз.
согласно древней легенде, Цветы и Листья ликориса обречены никогда не встречаться — они приходят в разное время, один за другим исчезая, но всё равно вечно скучая друг по другу. такова плата за близкий союз.
Союзов мне 30+ 1:1-4:4 Рп/вз Правила #рп
ОТКРЫТ НАБОР В АДМИНИСТРАЦИЮ ⚫️ наша конференция активно ищет: ⚫админов по интерактивам/активу/чату/союзам/видео/нью ждем каждого в нашу дружную команду) по всем вопросам писать @jeff_sing01🌟 #рп
➖➖➖➖➖➖ в чаты🎤 ➖аша кф 16+ ищет активных участников и админов. мы гарантируем уютную атмосферу, интересные разговоры, поддержку и заботу о каждом участнике! ➖➖➖➖➖➖➖ для вступления в основной чат нужно будет подтвердить свой возраст(фото паспорта или скрин с госуслуг, нам нужна только дата) можно исчезающим фото по всем вопросам писать - @jeff_sing01
согласно древней легенде, Цветы и Листья ликориса обречены никогда не встречаться — они приходят в разное время, один за другим исчезая, но всё равно вечно скучая друг по другу. такова плата за близкий союз.
Showing the 12 most recent of 20 posts we hold for @excc1se. 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.
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 19 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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“AROV1AN EXS” (@excc1se), 744 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/excc1se.
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.