Telegram RegisterThe public register of Telegram
Telegram profile photo for Penipu Laporan

Channel

Penipu Laporan

@penipu_laporan

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

23,646subscribers

-631 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001484399379
TypeChannel
Username@penipu_laporan
DescriptionFormat laporan di pinned send LAPORAN ke @LaporanRPJBbot Laporan lengkap disertai format, payment/qris, bukti tf dan bukti chat (ss bukti tf, bukti chat, dll dlm 1 BBC ) diskusi @jualbelidiskusi pm @basepromosirpjb @jual_beli_grosir rekber @miumyiu
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/penipu_laporan

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

23,64624,27723,961.56 August 2026 — 24,277 subscribers7 August 2026 — 24,277 subscribers8 August 2026 — 24,264 subscribers9 August 2026 — 24,259 subscribers10 August 2026 — 24,247 subscribers11 August 2026 — 24,237 subscribers12 August 2026 — 24,220 subscribers13 August 2026 — 24,212 subscribers14 August 2026 — 24,196 subscribers16 August 2026 — 24,172 subscribers17 August 2026 — 24,142 subscribers18 August 2026 — 24,123 subscribers19 August 2026 — 24,102 subscribers20 August 2026 — 24,100 subscribers21 August 2026 — 24,096 subscribers22 August 2026 — 24,075 subscribers24 August 2026 — 24,057 subscribers25 August 2026 — 24,041 subscribers26 August 2026 — 24,031 subscribers27 August 2026 — 24,032 subscribers28 August 2026 — 24,031 subscribers29 August 2026 — 24,010 subscribers30 August 2026 — 24,002 subscribers31 August 2026 — 23,990 subscribers1 September 2026 — 23,977 subscribers2 September 2026 — 23,956 subscribers3 September 2026 — 23,939 subscribers5 September 2026 — 23,921 subscribers8 September 2026 — 23,870 subscribers11 September 2026 — 23,819 subscribers13 September 2026 — 23,801 subscribers14 September 2026 — 23,786 subscribers16 September 2026 — 23,761 subscribers19 September 2026 — 23,728 subscribers25 September 2026 — 23,646 subscribers6 August 202625 September 2026
35 measurements spanning 50 days, net -631. 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 23,551–24,372 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
25 Sept 2026, 22:3723,646-82
19 Sept 2026, 07:4023,728-33
16 Sept 2026, 19:5723,761-25
14 Sept 2026, 20:1823,786-15
13 Sept 2026, 08:3923,801-18
11 Sept 2026, 09:1823,819-51
8 Sept 2026, 16:5623,870-51
5 Sept 2026, 12:1723,921-18
3 Sept 2026, 15:3923,939-17
2 Sept 2026, 06:0823,956-21
1 Sept 2026, 08:4523,977-13
31 Aug 2026, 10:0523,990-12
30 Aug 2026, 06:4424,002-8
29 Aug 2026, 05:0424,010-21
28 Aug 2026, 03:2524,031-1
27 Aug 2026, 06:1724,032+1
26 Aug 2026, 07:3824,031-10
25 Aug 2026, 06:2324,041-16
24 Aug 2026, 07:0424,057-18
22 Aug 2026, 16:4224,075first reading

Engagement

66 posts held, back to 13 July 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 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.77%
avg views ÷ 23,646 subscribers
Avg views / post
418
15 posts measured
Reaction rate
0.158%
reactions ÷ views · ER floor
Posts in window
15
of 66 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. It is computed over the 4 of 15 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 September 2026
Posts held66 (13 July 2026 – 24 September 2026)
Views total6,265
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Sept 2026, 01:43 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.

What this channel posts

Photos
≈28,500
Videos
≈146
Links
≈10,300

Lifetime counters from Telegram’s own channel header, read 28 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

16 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 81.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1381.3%
👍212.5%
😱16.25%

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 14 of the 66 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 66 most recent posts we hold, published 13 July 2026 to 24 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

24 Sept 2026, 12:17 UTC135 viewsread 28 September 2026

👤 7598360009 👦🏻 Noni J @wajibrnk urgent free call max 1 🌐 @banjarmajsin 🇮🇩 Indonesian 🕑 Diperbarui pada 24/09/2026

Signed felix

24 Sept 2026, 12:17 UTC135 viewsread 28 September 2026
Photo

Nama / Username Pelapor : deluna @yourvies Nama / Username penipu + no id penipu : @penjahfit 7598360009 Ch store / ch testi + no id store/testi : @livdocprof Tertipu sebesar : 8.000 Akses pembayaran : qris Rincian penipuan : aku mau beli chatgpt, udah pembayaran dll kata dia nunggu makernya on, ditunggu2 ga juga selesai, minta ganti apk lain ga di respon, minta reffund katanya send aja udah di send ga di reffund …

Signed felix

18 Sept 2026, 17:16 UTC295 views0 reactionsread 28 September 2026
Photo

Nama / Username Pelapor : pira & @ipayah Nama / Username penipu + no id penipu : Mirelle Piero + @Tepierro Ch store / ch testi + no id store/testi : @ResultLoren Tertipu sebesar : 24.000 Akses pembayaran : qriss Rincian penipuan : awalnya aku wtb jasa isi kuesioner di base wib, terus aku liat akun kakaknya kaya trusted & storenya beneran trusted. dia juga join moneyfess. disini aku bayar setengah karena feeling aku…

Signed felix

16 Sept 2026, 11:29 UTC302 viewsread 28 September 2026

Nama / Username Pengirim Laporan : @iPendraraw Nama / Username penipu + no id penipu : @Bkerdaya+8809940395 Ch store / ch testi : @danhsyat Tertipu sebesar : 30.000 Nomor penipu : - Akses pembayaran : - Rincian penipuan : jasa chat 40 nomer tapi kga di pay" Cho terus korbannya juga bnyk di antaranya ada @petanrung @aLintasan bnyk lagi mungkin selain itu terus dia juga masih aktif nge Rep in WTB orng chooo blm di …

Signed felix

14 Sept 2026, 14:54 UTC399 viewsread 28 September 2026

untuk semua komplain aku terima sampai besok jam 5 sore wib ya guys 🙏 semua chat aku perhatikan kok 🙏

Signed felix

8 Sept 2026, 17:15 UTC745 views3 reactionsread 28 September 2026

halo, ini aku felix dan tolong baca pesan ini ya teman2 semua. jadi tadi siang terjadi maintenance dari sisi server, dan aku mengerti bahwa sepertinya ada banyak akun yang tiba2 kehilangan beberapa fitur kuota nya. tolong di aktifasi ulang aja, bagi yang koinnya kurang nanti chat aku langsung. terimakasih untuk perhatiannya, dan mohon maaf untuk masalah yang terjadi. akhir2 ini aku emang agak slr dikarenakan sibuk ba…

❤3

Signed felix

5 Sept 2026, 15:52 UTC824 views1 reactionsread 28 September 2026
Photo

Photo, posted without a caption

❤1

Signed felix

5 Sept 2026, 15:52 UTC662 views0 reactionsread 28 September 2026
Photo

Nama / Username Pengirim Laporan : @fairieztowns Nama / Username penipu + no id penipu : @arraey (8977902066) Ch store / ch testi : @xsalvatire Tertipu sebesar : 20000 Nomor penipu : - Akses pembayaran : QRIS a.n kedai angels Rincian penipuan : aku hit dia dari base wtb buat edit carousel tapi ga ada kabar samsek, minta reff juga ga dibales. lengkapnya ada di @kedaiangelspenipu

Signed felix

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 12 registered channels — 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.

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

“Penipu Laporan” (@penipu_laporan), 23,646 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/penipu_laporan.

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.