⚠️JEJAK PENIPU USN PELAPOR :: @eitcheroses USN PENIPU :: @odyserry @permahii @gemistale @prostects @dvressy @kyutiiew @ssluttiees @nchiic @pruposed @excepct @tiinnyv @aurgument @crowje @yourslutiee ID PENIPU :: 8674377581 8316473674 CH PRIBADI PENIPU :: - CH PAY/EWALLET PENIPU :: Qris A.N Olaafiie LINK CH KRONOLOGI :: @RalinePenipu

Channel
JEJAK PENIPU
@jejak_penipu
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
7,564subscribers
-397 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002214389613 |
|---|---|
| Type | Channel |
| Username | @jejak_penipu |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/jejak_penipu |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 15:59 | 7,564 | -40 |
| 15 Sept 2026, 09:37 | 7,604 | -23 |
| 12 Sept 2026, 03:38 | 7,627 | -28 |
| 8 Sept 2026, 02:42 | 7,655 | -52 |
| 2 Sept 2026, 16:03 | 7,707 | -20 |
| 30 Aug 2026, 20:08 | 7,727 | -20 |
| 27 Aug 2026, 23:55 | 7,747 | -29 |
| 24 Aug 2026, 19:56 | 7,776 | -39 |
| 21 Aug 2026, 09:28 | 7,815 | -29 |
| 18 Aug 2026, 05:04 | 7,844 | -42 |
| 15 Aug 2026, 00:46 | 7,886 | -34 |
| 11 Aug 2026, 06:04 | 7,920 | -32 |
| 8 Aug 2026, 13:32 | 7,952 | -9 |
| 7 Aug 2026, 17:18 | 7,961 | first reading |
Engagement
31 posts held, back to 29 June 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 17 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.414%
- avg views ÷ 7,564 subscribers
- Avg views / post
- 31.3
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 31 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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 31 (29 June 2026 – 28 August 2026) |
| Views total | 94 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:44 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
5 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🆒 | 3 | 60.0% | |
| 🔥 | 2 | 40.0% |
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 3 of the 31 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 29 June 2026 to 28 August 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
⚠️JEJAK PENIPU USN PELAPOR :: @ibeetch USN PENIPU :: @hayatof ID PENIPU :: 8731871974 CH PRIBADI PENIPU :: @llukestore CH PAY/EWALLET PENIPU :: LINK CH KRONOLOGI :: https://t.me/SPILLHAYATOF
⚠️JEJAK PENIPU USN PELAPOR :: @eitcheroses USN PENIPU :: @kyutiiew @odyserry @permahii @yourslutiee ID PENIPU :: 8885258004 CH PRIBADI PENIPU :: - CH PAY/EWALLET PENIPU :: Qris A.N Olaafiie LINK CH KRONOLOGI :: @RalinePenipu
⚠️JEJAK PENIPU USN PELAPOR :: @Ifuckwthu USN PENIPU :: @gfwooImin ID PENIPU :: 8977283853 CH PRIBADI PENIPU :: DIA MAKE GC GEDE GUYS 2K MEM GC NYA ADA DI PROOF CH PAY/EWALLET PENIPU :: qris LINK CH KRONOLOGI :: @proofsimiskin
⚠️JEJAK PENIPU USN PELAPOR :: @ihaateus USN PENIPU :: @nShouId ID PENIPU :: 8609550303 CH PRIBADI PENIPU :: - CH PAY/EWALLET PENIPU :: - LINK CH KRONOLOGI :: @PENIPUCOOKKK
⚠️JEJAK PENIPU USN PELAPOR :: @annaydelrey USN PENIPU :: @docite ID PENIPU :: 8123039278 CH PRIBADI PENIPU :: @ressdocit CH PAY/EWALLET PENIPU :: LINK CH KRONOLOGI :: https://t.me/docitesipenipu
⚠️JEJAK PENIPU USN PELAPOR :: @deuki USN PENIPU :: @riengkus ID PENIPU :: 7489705216 CH PRIBADI PENIPU :: @rekber_jennle CH PAY/EWALLET PENIPU :: ngga ke simpan karna langsung diban dari grup LINK CH KRONOLOGI :: @spillriengkus
⚠️JEJAK PENIPU USN PELAPOR :: @tqamat USN PENIPU :: @lkeoonhoahnz ID PENIPU :: 8382739445 CH PRIBADI PENIPU :: (kalau ada) CH PAY/EWALLET PENIPU :: qr LINK CH KRONOLOGI :: @spilalaric
⚠️JEJAK PENIPU USN PELAPOR :: @etikadd USN PENIPU :: @ChyaCluyut @InternationalCambodia ID PENIPU :: (5210267104) (7117611100) CH PRIBADI PENIPU :: @WERDELINUS CH PAY/EWALLET PENIPU :: LINK CH KRONOLOGI :: https://t.me/penipumusnahbgst
take down
⚠️JEJAK PENIPU USN PELAPOR :: @introvr USN PENIPU :: @bbactery (first) @xAttire (clone) ID PENIPU :: 8260492018 CH PRIBADI PENIPU :: @rDropDead @bMustika (diprivate chnya) CH PAY/EWALLET PENIPU :: dana (085191244043) LINK CH KRONOLOGI :: @penipugrace
⚠️JEJAK PENIPU USN PELAPOR :: @lucuentil USN PENIPU :: @sweetheners @f1marchys ID PENIPU :: 6608634301 CH PRIBADI PENIPU :: - CH PAY/EWALLET PENIPU :: - LINK CH KRONOLOGI :: @MiskinTololBgt
Showing the 12 most recent of 31 posts we hold for @jejak_penipu. 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.
Posts edited after publishing
@jejak_penipu edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 25 August 2026
- Most recent edit
- 25 August 2026
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
@ralinepenipu · 14 postsBAYAR 700K GW ANJIRRR @.sWhouid
@PENIPUCOOKKK · 63 posts@excepct
@excepct · 12 postsyourslutiee
@yourslutiee · 22 postsaku slr karenaa?
@akuslrkarena · 231 postkorban STORE SPINDER / WSTORET
@arkatamapenipu · 31 post@aurgument
@aurgument · 11 postsab
@dvressy · 11 postkeep
@etikadd · 11 post.
@juncgsaebi · 11 postKAWAI RUKA
@kazairuka · 31 postㅤㅤㅤ.
@LLukestore · 101 postSpill own @hupsubs
@mejikuhibiniudor · 61 post.
@naiaravyy · 81 post𝓦𝘩𝘪𝘴𝘱𝘦𝘳𝘴 𝘰𝘧 𝘯𝘰𝘪𝘳 𖤓 24th
@nchiic · 11 postPENIPU BANGSATT
@penipubgstanjg · 31 postSpill penipu @ChyaCluyut @InternationalCambodia
@penipumusnahbgst · 21 postusername kotor @hUpsubs
@pramugarzi · 11 postp
@pruposed · 11 posthdu karl karl
@ripperkarl · 21 postSPILL @LLUKESTORE @HAYATOF
@SPILLHAYATOF · 141 post𝗖𝗛 𝗔𝗚𝗘𝗡𝗧 𝗔𝗖𝗛𝗶𝗔
@WERDELINUS · 8,0681 postpenipu grace @bbactery @xAttire
@wHanasui · 11 postPENIPU @yanopencreatedxd
@yanpenipu · 51 post
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.
Handles this channel named that no longer answer
- Dead references
- 38
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 5
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 33
- vacant every time we have ever looked
@jejak_penipu named 38 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 5 posts, 8 August 2026 – 23 August 2026 · confirmed gone 15 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 4 posts, 8 August 2026 – 29 August 2026 · confirmed gone 9 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 3 posts, 9 August 2026 – 23 August 2026 · confirmed gone 17 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 8 August 2026 – 13 August 2026 · confirmed gone 14 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 23 August 2026 – 23 August 2026 · confirmed gone 27 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 5 posts, 8 August 2026 – 23 August 2026
named in 4 posts, 8 August 2026 – 29 August 2026
named in 3 posts, 8 August 2026 – 29 August 2026
named in 3 posts, 9 August 2026 – 23 August 2026
named in 3 posts, 8 August 2026 – 13 August 2026
named in 3 posts, 8 August 2026 – 13 August 2026
named in 3 posts, 8 August 2026 – 13 August 2026
named in 2 posts, 29 August 2026 – 29 August 2026
named in 2 posts, 8 August 2026 – 23 August 2026
named in 2 posts, 8 August 2026 – 23 August 2026
named in 2 posts, 8 August 2026 – 13 August 2026
named in 2 posts, 8 August 2026 – 13 August 2026
named in 2 posts, 8 August 2026 – 13 August 2026
named in 2 posts, 8 August 2026 – 13 August 2026
named in 2 posts, 8 August 2026 – 13 August 2026
named in 2 posts, 8 August 2026 – 13 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 1 post, 29 August 2026 – 29 August 2026
named in 1 post, 29 August 2026 – 29 August 2026
named in 1 post, 29 August 2026 – 29 August 2026
named in 1 post, 29 August 2026 – 29 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“JEJAK PENIPU” (@jejak_penipu), 7,564 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/jejak_penipu.
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.