Telegram RegisterThe public register of Telegram
Telegram profile photo for klarifikasi hassle

Channel

klarifikasi hassle

@klarifhassle

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

3subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002443623991
TypeChannel
Username@klarifhassle
Descriptionbelong to @thehasslebot.
Created1 December 2024measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/klarifhassle

Growth

36 August 2026 — 3 subscribers13 August 2026 — 3 subscribers6 August 202613 August 2026
2 measurements spanning 7 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:463no change
6 Aug 2026, 18:163first reading

Engagement

6 posts held, back to 1 December 2024the 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 6 posts for this entry, the most recent from 2 December 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Dec 2024, 03:57 UTC187 viewsread 13 August 2026

Halo, kami dari keluarga Hassle (@TheHassle). Dibuatnya channel ini adalah untuk mengklarifikasi dan meluruskan masalah yang terjadi akhir akhir ini terkait pembohongan publik dan pembelaan terhadap Zivayra yang tertera di @SpillHassleFamily dan @hasslespill. 1. Pembohongan Publik Kami mengakui bahwa tindakan kami salah dan tidak tegas. Apa yang kami umumkan kepada publik dan yang terjadi memang benar tidak sama. D

2 Dec 2024, 03:57 UTC196 viewsread 13 August 2026

2. Pembelaan Zivayra Kemudian, di awal saat spill Ziva yang kedua muncul, kami memang pernah percaya kepada Ziva karena sender tersebut belum mengeluarkan bukti apapun, dan mengira bahwa itu hanya ujaran kebencian. Tapi seiring berjalannya waktu, sender mulai memberikan bukti kuat terkait masalah Ziva. Saat itu lah kami sadar bahwa perbuatan Ziva sangat fatal sehubungan dengan bukti yang dilampirkan. Maka dari itu, k

2 Dec 2024, 03:57 UTC213 viewsread 13 August 2026

Kami (@TheHassle), dengan tulus meminta maaf atas kejadian yang tidak menyenangkan ini. Kami menyadari adanya kesalahan dalam cara kami menangani situasi dan kami sangat menyesal karena hal tersebut telah menimbulkan banyak kekecewaan dan ketidaknyamanan dari berbagai pihak. Kedepannya kami akan berkomitmen untuk lebih berhati-hati, tegas, dan bijak dalam menindak lanjuti anggota keluarga yang bermasalah agar kami b

Showing the 6 most recent of 6 posts we hold for @klarifhassle. 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.

Citation-graph rank

Citation-graph rank — 1,275,195 of 1,570,450entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“klarifikasi hassle” (@klarifhassle), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/klarifhassle.

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.