Telegram RegisterThe public register of Telegram
Telegram profile photo for союз листы Асцелла

Channel

союз листы Асцелла

@unionAscell

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002214378055
TypeChannel
Username@unionAscell
CreatedBetween 1 June 2024 and 12 July 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/unionAscell

Growth

110 August 2026 — 1 subscribers15 August 2026 — 1 subscribers10 August 202615 August 2026
2 measurements spanning 4 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 08:151no change
10 Aug 2026, 22:161first reading

Engagement

20 posts held, back to 12 July 2024the 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 20 posts for this entry, the most recent from 24 July 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Jul 2024, 10:11 UTC25 viewsread 15 August 2026

вз @seppukufm след @CZENN1E допы : @Y4NGQUI @trueczennie @INV9D @iAMnotRINDOU @MAKEemWHISTLE @DOJJNG @r28re @IQQ0S @VRTMSS @FV5JQ @mortallovemy 12:12

24 Jul 2024, 05:43 UTC25 viewsread 15 August 2026

рп @ZEVSKIELV след - @tayla_e допы - @FPORVQU @T5OpKa @pooppiz @Sumpiriys @yooji_ni_e @dixswqp1 @ks06x @DFSOY @luni_mcc @bsmin1 @ARS_1QYJ @TOVMPX @PONSIZ

22 Jul 2024, 18:28 UTC25 viewsread 15 August 2026

вз @lorealinfo след - @Gog_gogo допы - @starirls @vilradh @limkls @imgeeyy @Nikayer @Vere_nea @fgfdg_dffdff @teddyqs

22 Jul 2024, 18:22 UTC22 viewsread 15 August 2026

рп @RUTHERFRD_FM Следящий - @GL1XWES допы: @pp_it_kss @ZX69GV @xwrzty @BD6SM9 @BDSMF69 @ottokheeeyo @FNX1VR @romanticismm @anstde @CRH1ST1N @F0S7ER @WhtsZt @ALD1NAS @D1RVAN

22 Jul 2024, 16:18 UTC17 viewsread 15 August 2026

рп @psinskie1 Следящий - @zaya_lp Допы - @DDS1ass @qwizqg @dixswqp1 @straightmaaan @ZENIJK @RAANIXX @wixhes @nefuuut @lolkkdne @yooji_ni_e @T5OpKa @diawixxxx @RML7WW

22 Jul 2024, 16:04 UTC17 viewsread 15 August 2026

вз @FATALIISTSS след: @kkklvus допы: @SQUZ11E @f1d4le @diane_meh

22 Jul 2024, 15:58 UTC17 viewsread 15 August 2026

вз @Pornelo_CatHouse следящий: @rmdblum доп: @will_mxx , @delormir , @P58wql , @ksksnie, @Minfuckyou , @Klohsd , @Dstrmk

20 Jul 2024, 19:35 UTC19 viewsread 15 August 2026

вз @CRSFMRMD след - @FRT1SK допы - @LiaFoster @rtusnb @KL1SOO2 @scvrswx @KL1SOO @millsiss @ccaseyw @rwsdc

20 Jul 2024, 16:23 UTC19 viewsread 15 August 2026

рп @VINCHENSKICLAN След: @NLVNSQ Допы: @FLUXRG @Leechiri @wowwowyippie @Fucking_XXL @zihen19 @H11LCRD

20 Jul 2024, 13:07 UTC20 viewsread 15 August 2026

актив @russkiegod следящий — @RAI52I. допы — @qwqerrs, @azumide, @keinmii, @xqwqxw, @pshlnhnst, @Adjcl, @JLL1NE, @danimatss , @haeguee, @ssytto, @soffirssk, @lukaseo, @honeymoney5, @chayrich.

20 Jul 2024, 09:53 UTC19 viewsread 15 August 2026

рп @MatadoresOscuros след - @t_adminnn допы - @t_admin0 @liptononon , @Minil110 , @Jkllllll0 , @DH7LEE , @bsfrdd , @F4DNKN , @hrsnfls

20 Jul 2024, 09:39 UTC18 viewsread 15 August 2026

рп @LNDRS_STUD след: @CLDRSG допы: @KLRSG @jkvrzh2 @cldcldl

Showing the 12 most recent of 20 posts we hold for @unionAscell. 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.

Mentions

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.

Cite this entry

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“союз листы Асцелла” (@unionAscell), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/unionAscell.

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.