Telegram RegisterThe public register of Telegram
Telegram profile photo for well

Channel

well

@spillpenipuanfoto

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

2subscribers

+1 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003973216955
TypeChannel
Username@spillpenipuanfoto
Created14 August 2026 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live11 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 11 October 2026
On Telegramt.me/spillpenipuanfoto

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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

121.514 August 2026 — 1 subscribers14 August 2026 — 1 subscribers15 September 2026 — 2 subscribers14 August 202615 September 2026
3 measurements spanning 32 days, net +1. 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–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 23:172+1
14 Aug 2026, 21:321no change
14 Aug 2026, 11:451first reading

Engagement

9 posts held, back to 14 August 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 1 page of 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 9 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Aug 2026, 09:18 UTC58 viewsread 14 August 2026

Saya berharap setelah adanya kronologi dan bukti yang saya lampirkan, semuanya bisa lebih berhati-hati dan tidak ada lagi yang sampai tertipu atau mengalami kerugian dari kejadian seperti ini. Tolong selalu cek identitas, rekber, dan seluruh proses transaksi sebelum mengirimkan uang atau gift kepada siapa pun.

14 Aug 2026, 09:17 UTC58 viewsread 14 August 2026

Untuk saat ini saya sudah melampirkan kronologi dan bukti percakapan dari awal transaksi sampai akun penerima gift. Saya tidak mengirimkan Rp55.000 tersebut dan saya tidak menerima pembayaran Rp145.00 Saya hanya meminta agar UPG/gift saya dikembalikan karena transaksi tidak berhasil diselesaikan sesuai kesepakatan. Bukti yang saya lampirkan saya upload sesuai urutan kejadian. Silakan cek dan nilai sendiri berdasark…

14 Aug 2026, 09:16 UTC58 viewsread 14 August 2026
Photo

Pada bagian ini saya lampirkan akun yang tercatat sebagai penerima gift/UPG dalam proses transaksi: 👤 ID: 8161415446 👦🏻 Nama: Here i am 🌐 Username: @Mempasrah 🕑 Diperbarui: 14/08/2026 Saya mencantumkan akun ini sebagai bukti untuk memperjelas ke mana gift/UPG tersebut tercatat atau diterima dalam proses transaksi. Saya lampirkan informasi akun ini bersama bukti lainnya agar hubungan antara buyer, pihak rekber, dan…

14 Aug 2026, 09:14 UTC56 viewsread 14 August 2026
Photo

Saya kemudian menjelaskan bahwa saya tidak memiliki dana tersebut dan mencoba menawarkan cara transaksi lain yang tidak mengharuskan saya mengeluarkan uang terlebih dahulu. Saya juga sudah menjelaskan kondisi saya kepada pihak yang bersangkutan. Setelah itu saya tetap meminta agar transaksi diselesaikan dengan cara yang jelas dan UPG saya dikembalikan apabila transaksi memang tidak dapat dilanjutkan.

14 Aug 2026, 09:12 UTC56 viewsread 14 August 2026
Photo

Setelah proses dengan rekber dilanjutkan, kemudian muncul permintaan terkait kekurangan nominal sebesar Rp55.000. Saya diminta untuk menyediakan atau mengirimkan nominal tersebut agar proses transaksi dapat dilanjutkan. Namun, saya tidak bisa memenuhi permintaan tersebut karena memang tidak sedang memegang dana Rp55.000.

14 Aug 2026, 09:12 UTC53 viewsread 14 August 2026
Photo

Setelah buyer mengarahkan transaksi untuk menggunakan rekber, saya kemudian melanjutkan proses transaksi dengan pihak rekber yang diberikan. REKBER Usn: @Daptang ID: 7194291708 CH: @TTmulf_PLACE Pada bagian ini saya mulai berkomunikasi langsung dengan pihak rekber mengenai proses transaksi UPG. Saya mengikuti arahan yang diberikan terkait proses rekber dan nominal yang harus dipenuhi. Saya lampirkan screenshot per…

14 Aug 2026, 09:08 UTC49 viewsread 14 August 2026

Setelah buyer menyatakan ingin mengambil UPG saya, pembicaraan kemudian berlanjut ke metode transaksi. Buyer menanyakan mengenai penggunaan rekber untuk transaksi ini. Saya kemudian mengikuti pembahasan tersebut karena saya juga ingin transaksi dilakukan dengan cara yang jelas dan aman untuk kedua pihak. Setelah itu mulai dibahas mengenai proses pembayaran serta nominal yang harus dipenuhi dalam transaksi. Pada tah…

14 Aug 2026, 09:07 UTC48 viewsread 14 August 2026
Photo

Pada awalnya, buyer dengan username @fotoinblur menghubungi saya karena tertarik untuk take UPG yang sedang saya jual. Dari awal saya memang sedang menawarkan UPG tersebut untuk dijual, kemudian buyer menyampaikan ketertarikannya dan kami mulai membahas mengenai transaksi. Saya melayani pembicaraan tersebut seperti transaksi pada umumnya. Setelah buyer menyatakan tertarik, kami kemudian lanjut membahas mengenai meto…

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

“well” (@spillpenipuanfoto), 2 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/spillpenipuanfoto.

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.