Telegram RegisterThe public register of Telegram
Telegram profile photo for spill penipu nokos

Channel

spill penipu nokos

@spillanpenipunokos

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 27 August 2026

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

Register entry

Telegram ID-1004325554038
TypeChannel
Username@spillanpenipunokos
Created26 August 2026measured — dated from the channel’s first post
First recorded27 August 2026
Last confirmed live13 September 2026
Measurements held2
On Telegramt.me/spillanpenipunokos

Growth

227 Aug 2026, 08:15 — 2 subscribers27 Aug 2026, 08:30 — 2 subscribers27 Aug 2026, 08:1527 Aug 2026, 08:30
2 measurements taken within a single day. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 08:302no change
27 Aug 2026, 08:152first reading

Engagement

14 posts held, back to 26 August 2026the 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
3900.0%
avg views ÷ 2 subscribers
Avg views / post
78.0
11 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
14
of 14 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 1 of 11 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 26 August 2026
Posts held14 (26 August 202626 August 2026)
Views total858
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Aug 2026, 08:30 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
7
Links
1

Lifetime counters from Telegram’s own channel header, read 27 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

26 Aug 2026, 06:14 UTC100 viewsread 27 August 2026

dan mungkin ini juga jadi pembelajaran buat aku supaya lebih hati hati dan teliti saat memilih store.. aku nyesel banget karena ga ngelakuin itu..

26 Aug 2026, 06:12 UTC100 viewsread 27 August 2026

tolong ya guys.. aku gabisa apa apain lagi selain minta tolong sama kalian, soalnya akun kita berdua udah di block juga. makasih yaa buat yang udah bantuin

26 Aug 2026, 06:11 UTC100 viewsread 27 August 2026

aku gatau mungkin dia butuh uang atau gimana tapi aku juga gabisa terima kalo dia cari uang dengan cara nipu kaya gini, aku mau uang aku kembali dan dia kena spam, yang baik hati mungkin bisa bantu aku spam dia ya.. :(

26 Aug 2026, 06:07 UTC98 viewsread 27 August 2026
Photo

kita chat ga dibales, kita spam juga biar dibales ternyata tetep dibiarin aja. padahal dia aktif di ch store nya, mau di telpon juga gabisa

26 Aug 2026, 06:06 UTC73 viewsread 27 August 2026
Photo

terus pas dicek lagi ternyata temen aku di banned dari ch nya

26 Aug 2026, 06:05 UTC66 viewsread 27 August 2026
Photo

karena aku udah sadar ini penipu, akhirnya aku chat kaya di ss an aku sampe akhirnya di block sama dia

26 Aug 2026, 06:03 UTC45 viewsread 27 August 2026
Photo

terus aku tuh ngide buat chat seller nya siapa tau emang beneran lagi diluar, ternyata dia bales, fast respon juga

26 Aug 2026, 06:01 UTC42 viewsread 27 August 2026
Photo

nih guys awalnya temen aku tuh mau beli 2 nokos luar, terus kita tunggu karna dia bilang nya lagi diluar. abis kita tunggu beberapa jam dia ga bales bales lagi sampe temen aku chat beberapa kali, tetep ga dibales.

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

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

“spill penipu nokos” (@spillanpenipunokos), 2 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/spillanpenipunokos.

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.