Telegram RegisterThe public register of Telegram
Telegram profile photo for 𖹭 ۫ ׅ (..🍀🍋 arsip kajiwa

Channel

𖹭 ۫ ׅ (..🍀🍋 arsip kajiwa

@kajiwafile

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

28subscribers

+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-1002131131562
TypeChannel
Username@kajiwafile
Description✦ Garansi : https://t.me/kajiwafile/115 ✦ Guide : https://t.me/kajiwafile/72
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live14 September 2026
Measurements held2
On Telegramt.me/kajiwafile

Growth

287 August 2026 — 28 subscribers11 August 2026 — 28 subscribers7 August 202611 August 2026
2 measurements spanning 3 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 27–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 06:0228no change
7 Aug 2026, 18:3128first reading

Engagement

20 posts held, back to 29 September 2025the 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
5

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

5 Feb 2026, 10:25 UTC123 viewsread 11 August 2026

⸝ ֗ 🦋 𓈒 FEE INRUSH 𓂃 ⤾ ׁ ˖ 72 jam : 1.000 48 jam : 3.000 24 jam : 5.000 6 jam : 7.000 3 jam : 9.000 1 jam : 13.000

29 Sept 2025, 11:23 UTC260 viewsread 11 August 2026

↑ ۫ ⠖ benefit akses si merah prem - nonton bebas iklan - original series - series k-drama - series hollywood - international tv ↑ ۫ ⠖ si merah plan platinum - bebas nonton tayangan olahraga seperti : UCL - UEL - NBA - LIGA1 - BEIN 1&3 - WTA - IBL - dan tayangan olahraga lainnya ↑ ۫ ⠖ si merah plan diamond - bisa akses premiere league semua paket platinum

29 Sept 2025, 11:23 UTC243 viewsread 11 August 2026

↑ ۫ ⠖ disney plan basic - bisa login sampai 3 device - kualitas video HD 1080p - kualitas audio dolby 5.1 atmos ↑ ۫ ⠖ disney plan premium - bisa login sampai 10 device - kualitas video 4k ultra HD 2160p - kualitas audio dolby 5.1 atmos

29 Sept 2025, 11:23 UTC216 viewsread 11 August 2026

↑ ۫ ⠖ about plan iqiyi ada dua plan yaitu standart dan premium, jika pembelian 1slot sharing hanya bisa digunakan di 1 device saja, jika mengalami limit screen bisa download filmnya terlebih dahulu jika tidak bisa login melalui website iqiyi ↑ ۫ ⠖ benefit all plan - dapat menon konten ekslusif - bisa mendownload konten ↑ ۫ ⠖ plan std - jika satu akun terdapat 2 orang yang sedang menonton user lainnya harus menung

29 Sept 2025, 11:22 UTC155 viewsread 11 August 2026

↑ ۫ ⠖ about plan viu plan viu ada 2 premium biasa sama premium plus sama² anti limit ↑ ۫ ⠖ plan premium biasa bebas iklan + full hd + bisa mengunduh konten tanpa batasan + akses konten sudah premium ↑ ۫ ⠖ plan premium plus akses premium di film nya jadwal lebih dahulu tayang dari plan biasa + benefit lainnya sama seperti viu biasa

Showing the 12 most recent of 20 posts we hold for @kajiwafile. 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“𖹭 ۫ ׅ (..🍀🍋 arsip kajiwa” (@kajiwafile), 28 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/kajiwafile.

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.