Telegram RegisterThe public register of Telegram
Telegram profile photo for penipu trade @waantsq

Channel

penipu trade @waantsq

@penipuwaantsq

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

1subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1004325533973
TypeChannel
Username@penipuwaantsq
Created10 August 2026 — measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live17 September 2026
Measurements held2
On Telegramt.me/penipuwaantsq

Growth

110 August 2026 — 1 subscribers15 August 2026 — 1 subscribers10 August 202615 August 2026
2 measurements spanning 5 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 08:151no change
10 Aug 2026, 11:451first reading

Engagement

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

What this channel posts

Photos
8
Links
2

Lifetime counters from Telegram’s own channel header, read 15 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

10 Aug 2026, 10:22 UTC27 viewsread 15 August 2026
Photo

ini proof kalo qr dan ton nya milik si scammer ya, aku ga sempet ss tapi untungnya udah aku fw ke temenku jadi masih ada proof nya!

10 Aug 2026, 10:18 UTC28 viewsread 15 August 2026

anw diisni emg dia ga nanya nanya usn ku bentukannya gimana ya tapi dia lgsg gas gas aja buat trade tanpa liat bentukannya 😭😭😭

10 Aug 2026, 10:15 UTC28 viewsread 15 August 2026

a.n qriss nya toko juhoon. aku rasa dia pake jaspin jadi seller jaspin yg liat ini mungkin bisa hati hati karena takut qriss nya dipakai untuk nipu.

10 Aug 2026, 10:14 UTC28 viewsread 15 August 2026
Photo

TON KEEPERNYA : UQB68C8RxFzWLPepUTz263E3_M2pqlDpru7B0sb3QTZQe19p

10 Aug 2026, 10:14 UTC27 viewsread 15 August 2026

USERNAME TRADE YG DIA PAKAI : @iucur @iucfu dia pakenya i besar jadi hati hati. YANG ASLI DUA DUANYA PU DAN PAKE L. USN DIA : @waantsq id nya 8375814688 tg://openmessage?user_id=8375814688.

10 Aug 2026, 10:13 UTC27 viewsread 15 August 2026
Photo

disini aku lgsg tf qriss nya ke dia sebesar 50p. ( ini sengaja ya karena aku mau negur dia. after aku tegur aku langsung di clear chat dan di block) untungnya aku dh save id tele, usn, ton dan qriss yg dia pakai

10 Aug 2026, 10:11 UTC25 viewsread 15 August 2026
Photo

dan ini afternya aku udh sadar kalo ternyata dia penipu jadi aku mainin dia. aku blg aku bisa add $ dan nyuruy dia buat send nomor / ton nya dia.

10 Aug 2026, 10:10 UTC24 viewsread 15 August 2026
Photo

https://t.me/c/3938979273/1129376 awalnya aku lat di pm an dia yg ini ma trade usn aku ke lucu nya dia. dan kayak yg di cht ini kalo dia ngajakin aku trade ke lu u dan blg ps nya 4xx awal. lalu aku nolak karena kurang suka bentukan lucu nya dia (disini aku ga sadar samsek kalo ternyata lucu nya dia itu pake i besar bukan pake L.) dan dia menawarkan trade ke lucur nya milik dia.

Showing the 10 most recent of 10 posts we hold for @penipuwaantsq. 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 2 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.

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

“penipu trade @waantsq” (@penipuwaantsq), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/penipuwaantsq.

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.