Telegram RegisterThe public register of Telegram
Telegram profile photo for ✿ ˚ . garansi bella ✎ .. 💕

Channel

✿ ˚ . garansi bella ✎ .. 💕

@garanshian

On this record: Topic · Growth · Engagement · Posts · Cite this entry

27subscribers

+6 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1003677874302
TypeChannel
Username@garanshian
Created23 January 2026 — measured — dated from the channel’s first post
First recorded17 August 2026
Last confirmed live3 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/garanshian

Topic

Ecommerce storefront — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 86% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

212824.517 August 2026 — 21 subscribers17 August 2026 — 21 subscribers24 August 2026 — 23 subscribers1 September 2026 — 25 subscribers10 September 2026 — 27 subscribers18 September 2026 — 28 subscribers3 October 2026 — 27 subscribers2717 August 20263 October 2026
7 measurements spanning 47 days, net +6. 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 20–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 06:5727-1
18 Sept 2026, 05:5728+1
10 Sept 2026, 09:5527+2
1 Sept 2026, 02:5825+2
24 Aug 2026, 20:1323+2
17 Aug 2026, 20:3621no change
17 Aug 2026, 09:1121first reading

Engagement

12 posts held, back to 23 January 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 21 February 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Feb 2026, 01:54 UTC892 viewsread 17 August 2026

perhatikan durasi garansi 1 day only gar 20 jam 3 day only gar 48 jam 7 day only gar 5 day 1 month only gar 20-25 day 1 years only gar 6 month "kenapa ga sampai akhir?" karna seperti saat kamu beli kulkas gar hanya 3 tahun tapi kalian memakai nya sampai seumur hidup.

23 Jan 2026, 11:32 UTC≈1,120 viewsread 17 August 2026

teman teman pastiin kalian setor screenshot KE AKU BUKAN KE ASIST ! dalam waktu sesuai wording, & isi rnk , hukumnya wajib dua duanya jika lebih dari itu aku bener bener minta maaf garansi tidak aktif alias nogar 🙏

23 Jan 2026, 11:02 UTC≈1,100 viewsread 17 August 2026
Photo

format garansi khusus netflix 1. username : 2. tnggl order & tnggl permasalahan : 3. terpakai berapa hari : 4. jenis : 1u/2u/semi 5. permasalahan akun : 6. link bukti login & rnk : 7. email akun netf : ( jika pakai link kosongkan ) format garansi aplikasi premium a. username : b. tnggl order & tnggl permaslhan : c. jenis : shar/priv d. nama aplikasi : e. terpakai berapa bari : f. link bukti login & rnk : g. email & …

23 Jan 2026, 11:01 UTC775 viewsread 17 August 2026

RUMUS REFUND 💭 (Harga x sisa hari ÷ total hari langganan) x service fee = total refund. Contoh : (5.000 x 55 hari ÷ 60 hari) x 0.5 = 2.291 Penjelasan : — Harga = harga reseller yang kamu beli di aku, bukan harga cust yang beli di kamu. — Sisa hari = sisa durasi yang kalian order (misalnya, kalian beli tanggal 10 dan bermasalah di tanggal 18. nah, 30 hari - 18 hari = 12 hari itu sisanya). — Total hari = Durasi ya…

23 Jan 2026, 11:00 UTCviews —

✿ ˚ . garansi bella ✎ .. 💕 pinned «SYARAT DAPET GARANSIAN HANYA MEMATUHI 2 POINT INI. 1. ISI RNK 1×24 JAM 2. SEND PROOF LOGIN 3. TIDAK LEFT RESS ! kalau ga menjalankan 3 , point tersebut = NO GARANSI, NO COMPLAIN BODOAMAT. GAUSAH KOAR KOAR MINTA GARANSIAN KALAU DARI AWAL GA NGEJALANIN…»

23 Jan 2026, 11:00 UTC673 viewsread 17 August 2026

SYARAT DAPET GARANSIAN HANYA MEMATUHI 2 POINT INI. 1. ISI RNK 1×24 JAM 2. SEND PROOF LOGIN 3. TIDAK LEFT RESS ! kalau ga menjalankan 3 , point tersebut = NO GARANSI, NO COMPLAIN BODOAMAT. GAUSAH KOAR KOAR MINTA GARANSIAN KALAU DARI AWAL GA NGEJALANIN 3 POINT DIATAS!, UNTUK REFFUND DI ATAS WAKTU 24X2 TIDAK MENGISI RNK TIDAK AKAN DI REFFUND !

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

“✿ ˚ . garansi bella ✎ .. 💕” (@garanshian), 27 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/garanshian.

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.