Telegram RegisterThe public register of Telegram

Channel

AUSSIVE's ARCHIVE.

@Archissive

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

7subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002050168691
TypeChannel
Username@Archissive
Created14 April 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/Archissive

Growth

77 August 2026 — 7 subscribers12 August 2026 — 7 subscribers7 August 202612 August 2026
2 measurements spanning 5 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”. The vertical axis spans 6–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 18:327no change
7 Aug 2026, 06:487first reading

Engagement

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

What this channel posts

Photos
3
Links
3

Lifetime counters from Telegram’s own channel header, read 12 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

14 Apr 2024, 07:01 UTC≈2,270 viewsread 12 August 2026

𖦽. COST TABLE @AUSSIVE. TAKE YOUR FORM HERE! 𐙚.ᐟ MOODBOARD BASIC 6 slides: Rp3.000 9 slides: Rp5.000 12 slides: Rp6.000 𐙚.ᐟ MOODBOARD SEMI—DECORATION • 6 slides with one slide decoration: start Rp4.000 with two slides decoration: start Rp5.000 with three slides decoration: start Rp6.000 • 9 slides with one slide decoration: start Rp6.000 with two slides decoration: start Rp7.000 with three slides decoration: start …

14 Apr 2024, 06:42 UTC≈1,930 viewsread 12 August 2026
Photo

𖦽. REPLACEMENT TERMS Customers are encouraged to provide their own muse photos for the best results. Photos must be submitted within 2×24 hours after payment. Orders will be delivered without replacement if no photos are received within the deadline. Seller-provided photos are available for an additional fee of Rp500–1.000, depending on the catalogue. Please confirm availability beforehand. 𖦽. REVISION POLICY All o…

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

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

“AUSSIVE's ARCHIVE.” (@Archissive), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Archissive.

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.