Telegram RegisterThe public register of Telegram
Telegram profile photo for Seri Mempelai Pakej, Review & Testimoni

Channel

Seri Mempelai Pakej, Review & Testimoni

@serimempelai

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

219subscribers

-2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001270489588
TypeChannel
Username@serimempelai
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 28 August 2026
On Telegramt.me/serimempelai

Growth

2192212207 August 2026 — 221 subscribers8 August 2026 — 221 subscribers15 August 2026 — 220 subscribers22 August 2026 — 219 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net -2. 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 219–221 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 15:53219-1
15 Aug 2026, 18:48220-1
8 Aug 2026, 10:33221no change
7 Aug 2026, 23:27221first reading

Engagement

6 posts held, back to 28 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 6 posts for this entry, the most recent from 8 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
7m 04s
Average length
1m 46s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

8 Mar 2026, 21:33 UTC52 viewsread 8 August 2026

𝗪𝗢𝗪𝗪!! 𝗕𝗜𝗔𝗥 𝗕𝗘𝗧𝗢𝗟!! 𝗣𝗔𝗞𝗘𝗝 𝗞𝗔𝗛𝗪𝗜𝗡 𝗔𝗟𝗟-𝗜𝗡 𝗡𝗜 𝗢𝗛𝗦𝗘𝗠 𝗦𝗚𝗧!! 𝗛𝗔𝗡𝗬𝗔 𝗗𝗜 𝗦𝗘𝗥𝗜 𝗠𝗘𝗠𝗣𝗘𝗟𝗔𝗜 𝗗𝗜𝗣𝗘𝗥𝗖𝗔𝗬𝗔𝗜 𝗦𝗘𝗝𝗔𝗞 𝗗𝗔𝗥𝗜 𝟮𝟬𝟬𝟯!! . Food Tasting Setiap Sabtu & Ahad dengan temujanji . Dah ada tempat sendiri? Atau buat majlis dekat rumah, dewan komuniti, taman atau venue sendiri? Kalau dah ada tempat majlis, yang lain kami uruskan dari A sampai Z! 😍 . Ohsem sgt tak payah nak pening-pening dah semua dah complete tau dlm pakej tu, Uolls hanya

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

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

“Seri Mempelai Pakej, Review & Testimoni” (@serimempelai), 219 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/serimempelai.

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.