Telegram RegisterThe public register of Telegram
Telegram profile photo for BACA INI (CH GARANSI).

Channel

BACA INI (CH GARANSI).

@garansicil

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

221subscribers

+26 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003038171201
TypeChannel
Username@garansicil
Created22 September 2025 — measured — dated from the channel’s first post
First recorded8 September 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/garansicil

Topic

Other / unclassifiable — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 23% 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

1952212088 August 2026 — 195 subscribers16 August 2026 — 201 subscribers23 August 2026 — 205 subscribers30 August 2026 — 206 subscribers8 September 2026 — 206 subscribers9 September 2026 — 210 subscribers18 September 2026 — 221 subscribers8 August 202618 September 2026
7 measurements spanning 40 days, net +26. 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 191–225 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 01:18221+11
9 Sept 2026, 01:20210+4
8 Sept 2026, 20:22206no change
30 Aug 2026, 17:12206+1
23 Aug 2026, 23:06205+4
16 Aug 2026, 17:24201+6
8 Aug 2026, 16:00195first reading

Engagement

11 posts held, back to 22 September 2025 — 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.

ERR · 30 days
59.3%
avg views ÷ 221 subscribers
Avg views / post
131
2 posts measured
Reaction rate
0.763%
reactions ÷ views · ER floor
Posts in window
2
of 11 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 September 2026
Posts held11 (22 September 2025 – 4 September 2026)
Views total262
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Sept 2026, 20:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

73 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 94.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6994.5%
🔥45.48%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 8 of the 11 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 73 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 22 September 2025 to 4 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Sept 2026, 12:22 UTC99 views0 reactionsread 8 September 2026

Bot auto order 24/7 dari @siujangbot pindah ke @picillbot kalo dirasa ada saldo deposit hubungi @osteila untuk pemindahan saldo ke bot baru. Masih pemindahan stock bertahap ya /start dulu aja botnya

1 Sept 2026, 04:34 UTC163 views2 reactionsread 8 September 2026
Photo

Garansi done ya, kalo ada yang kelewat rechat aja

❤2

Signed literasi ♡

18 Aug 2026, 12:39 UTC428 viewsread 8 September 2026

Diperhatikan lagi setiap garansian ya peeps. Disini udah selengkap itu sediain gimana cara garansi dan contohnya juga ada berupa foto.

11 Jan 2026, 14:35 UTC≈4,610 views13 reactionsread 8 September 2026
Photo

♥️ TATA CARA GARANSI intinya yg dibutuhin pas lapor garansi itu link proof login, pengisian format garansi yang lengkap & screenshot masalahnya. ㅤㅤ "gimana cara claim garansi?" 🤩 screenshot bagian "masalah" akunnya, jangan asal kasih ss yg lain/melenceng dari inti masalah. 🤩 isi format garansi yang lengkap, format garansi sudah tersedia di t.me/garansicil/14?single tinggal klik "salin kode" aja. gabisa salin ta…

❤13

2 Dec 2025, 15:45 UTC≈3,000 views0 reactionsread 8 September 2026
Sticker

Sticker, posted without a caption

2 Dec 2025, 06:54 UTC≈5,170 views32 reactionsread 8 September 2026
Photo

terimakasih banyak temen-temen yang udah jajan di picil, sebagian dari hasil penjualan tersebut telah kami alokasikan untuk membantu saudara-saudara kita yang membutuhkan uluran tangan di Sumatera. semoga dengan adanya sedikit kontribusi ini dapat memberikan keringanan dan harapan baru disana. dan kebaikan kalian menjadi langkah bersama membawa berkah untuk banyak orang ❤️

❤28🔥4

24 Sept 2025, 09:13 UTC≈7,130 views11 reactionsread 8 September 2026

SALIN FORMAT GARANSI APLIKASI & ISI YANG LENGKAP, SATUIN SAMA SCREENSHOT PERMASALAHANNYA LANGSUNG KIRIM KE @PIICIL note besar! jika pembelian dari bot WAJIB forward bagian "transaksi sukses" dari @siujangbot ❤️ Garansi pembelian dari bot/grup? Username mu: Tanggal pembelian: Nama aplikasi & jenis: Email & pass: Durasi beli: Sisa durasi: Jelaskan masalahnya: -lampirkan berupa screenshot. Link proof login di @garansic…

❤11

23 Sept 2025, 05:30 UTC≈7,140 views0 reactionsread 8 September 2026

ㅤㅤㅤㅤㅤㅤㅤㅤ 🗂 PROOF APPS PREMIUM kirim screenshot bukti kamu berhasil login dengan maksimal waktu: untuk harian 5 jam, mingguan 12 jam, bulanan 24 jam dihari yang sama saat akun diberikan. tidak kirim melebihi batas waktu yang sudah ditentukan, pembelian pada aplikasi tersebut menjadi no garansi. tidak ada toleransi ✅ Monitoring aplikasi. Nama aplikasi: Sharing/private: Lokasi & device: Durasi: ✍️ jika kakak ingin m…

23 Sept 2025, 04:37 UTC≈6,420 views15 reactionsread 8 September 2026
Photo

🫙 hii baca ini dulu yuk <3 PROSES GARANSI Proses garansi biasanya memakan waktu selama 0-3 hari dan maksimal 7 hari kalo ada kendala massal. Selama proses garansi apabila belum mencapai waktu estimasi tidak boleh spam. GARANSI HANGUS pembelian di bot auto order maupun grup wajib banget kirim proof login sebelum melebihi batas waktu yang telah ditentukan. gak ada toleransi cust baru login, seller…

❤15

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

“BACA INI (CH GARANSI).” (@garansicil), 221 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/garansicil.

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.