Telegram RegisterThe public register of Telegram
Telegram profile photo for @afespa archive.

Channel

@afespa archive.

@afespaarchive

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1001949369778
TypeChannel
Username@afespaarchive
CreatedBetween 1 April 2023 and 26 July 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live17 September 2026
Measurements held2
On Telegramt.me/afespaarchive

Growth

111 August 2026 — 1 subscribers15 August 2026 — 1 subscribers11 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, 09:021no change
11 Aug 2026, 05:021first reading

Engagement

19 posts held, back to 26 July 2023the 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.

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 16 August 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
42
Links
5

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

16 Aug 2023, 15:29 UTC186 viewsread 15 August 2026
Photo

#RulesNokosGanom Halo MYNE'S, menindaklanjuti dan demi kepentingan bersama. MYnespa memutuskan untuk membuat RULES UNTUK NOKOS TELEGRAM GANOM. Rules: - berlangganan @afespa untuk klaim garansi selama 5 bulan - akun buyer yang akan diganti nomornya wajib di keep oleh admin @afespa hingga bisa diganti. karena jika langsung diganti dihari itu maka akan ada announcement dari telegram seperti gambar diatas. Benefit: -

7 Aug 2023, 02:23 UTC225 viewsread 15 August 2026

Halo mutual-mutual @afespa gunakan format dibawah ini untuk pendataan mutual ya, thank you! @ store + @ akun + @ bot hfw

27 Jul 2023, 18:04 UTC212 viewsread 15 August 2026

Akun sosmed kosongan Instagram with folls (no label new) Instagram no folls (no label new)

27 Jul 2023, 17:00 UTC155 viewsread 15 August 2026

Ready gc y21/y22 Juni 21, 1 slot Juli 21, 10 slot Sept 21, 2 slot Nov 21, 1 slot Des 21, 9 slot Mar 22, 7 slot Ch kosongan with subs main acc Apr 21, with 123 subs. Juni 21, with 25 subs. Okt 21, with 24 subs. Des 21, with 26 subs. Des 21, with 4 subs. Ch kosongan tanpa subs Nov 21, 5 slot Jan 22, 5 slot Feb 22, 2 slot Apr 22, 1 slot Des 22, 1 slot Contact @afespabot if u interested.

26 Jul 2023, 11:02 UTC159 viewsread 15 August 2026

ORDERAN AGUSTUS Voucher Gofood • F Voucher Gofood • F Voucher Shopee • M Voucher Gofood • F Nokos Telegram • C Nokos Telegram • B Nokos Telegram • C Note, pengerjaan sesuai list orderan. MYne's yang orderan nya belum dikerjain mohon pengertiannya. Thank youuu.

26 Jul 2023, 07:00 UTC229 viewsread 15 August 2026

Click the Hastag according to your n•_•ds! ⎘ #VIU ⎘ #IQIYI ⎘ #IFLIX ⎘ #JOOX ⎘ #VSCO ⎘ #WETV ⎘ #TEZZA ⎘ #CANVA ⎘ #SCRIBD ⎘ #HBOGO ⎘ #REMINI ⎘ #LOKLOK ⎘ #NETFLIX ⎘ #SPOTIFY ⎘ #WATTPAD ⎘ #YOUTUBE ⎘ #GETCONTACT ⎘ #UNFOLDPLUS ⎘ #VIDEOPREMIER ⎘ #ALIGHTMOTION ⎘ #DISNEYPLUSHOTSTAR

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

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.

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.

“@afespa archive.” (@afespaarchive), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/afespaarchive.

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.