Telegram RegisterThe public register of Telegram
Telegram profile photo for PAYMENT MEIZY STORE

Channel

PAYMENT MEIZY STORE

@paymentmeizy

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

2subscribers

+0 since we began measuring on 19 September 2026

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

Register entry

Telegram ID-1001947018141
TypeChannel
Username@paymentmeizy
Created6 June 2023 — measured — dated from the channel’s first post
First recorded19 September 2026
Last confirmed live19 September 2026
Measurements held2
On Telegramt.me/paymentmeizy

Growth

219 Sept 2026, 00:47 — 2 subscribers19 Sept 2026, 01:22 — 2 subscribers19 Sept 2026, 00:4719 Sept 2026, 01:22
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
19 Sept 2026, 01:222no change
19 Sept 2026, 00:472first reading

Engagement

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

What this channel posts

Photos
2
Links
1

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

31 May 2026, 20:26 UTC183 viewsread 19 September 2026

👍MENU PAYMENT😉 1️⃣QRIS NO FEE 2️⃣QRIS FEE URGENT 3️⃣EWALLET/BANK TNC

31 May 2026, 20:15 UTC185 viewsread 19 September 2026

⚠️ WAJIB DIBACA Semua pembayaran ke Store Meizy yang dilakukan tanpa menanyakan ketersediaan stok terlebih dahulu akan otomatis masuk sebagai deposit bot @Meizypremautoorder_bot. Store tidak melayani pengembalian dana akibat salah transfer (kelalaian dari pihak B), terutama jika diminta dikembalikan ke rekening berbeda. Hal ini untuk mencegah penipuan segitiga atau modus sejenis. Contoh : “Kak, salah transfer. Bisa…

31 May 2026, 19:59 UTC155 viewsread 19 September 2026

Another payment : Dana : +62 83192301841 GOPAY : +62 83192301841 Shopeepay : +62 83192301841 No fee jika sesama ewallet. +1k jika topup dari bank atau beda ewallet Seabank : 901313749676 Superbank : 000001263706 A.n Nova Fitria Almaisya

31 May 2026, 19:40 UTC170 viewsread 19 September 2026
Photo

MOHON PERHATIANNYA ❗️❗️❗️ FEE = 2.5% dari nominal payment (qris resto) Send bukti pembayaran :: @Meizyaaaa Digunakkan untuk pembayaran urgent lintas negara bila qris pertama tidak valid ✨✨✨✨✨✨✨✨✨✨✨✨✨ ⚠️ PLEASE TAKE NOTE !! Fee = 2.5% of the payment amount (Restaurant QRIS). Please send your payment proof to @Meizyaaaa This payment method is intended for urgent international transactions when the primary QRIS opt…

31 May 2026, 19:19 UTC311 viewsread 19 September 2026
Photo

📢NO FEE untuk transaksi di bawah 500k. Jika 500k keatas, silakan split payment atau transfer langsung ke rekening bank Store Meizy. Send bukti pembayaran :: @Meizyaaaa 📢NO FEE for transactions below IDR 500,000. For transactions of IDR 500,000 or more, please split the payment into multiple transactions or transfer directly to the Store Meizy bank account. Please send your payment proof to @Meizyaaaa Tysm!❤️

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

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

“PAYMENT MEIZY STORE” (@paymentmeizy), 2 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/paymentmeizy.

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.