Telegram RegisterThe public register of Telegram
Telegram profile photo for ρα𝗒ꭑ𝖾𐓣𝗍

Channel

ρα𝗒ꭑ𝖾𐓣𝗍

@gsaldo

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

1subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003724910870
TypeChannel
Username@gsaldo
Descriptionpayment SΞΉΟƒΙΎΞ± @jungahyeron
Created24 April 2026 β€” measured β€” dated from the channel’s first post
First recorded15 August 2026
Last confirmed live15 September 2026
Measurements held2
On Telegramt.me/gsaldo

Growth

112 August 2026 β€” 1 subscribers15 August 2026 β€” 1 subscribers12 August 202615 August 2026
2 measurements spanning 2 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, 11:161no change
12 Aug 2026, 23:521first reading

Engagement

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

What this channel posts

Photos
6
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

12 May 2026, 05:04 UTC37 viewsread 15 August 2026

πŸ’— Please proceed with payment with the account details below. πŸ’Έ Payment Qris πŸ’Έ ↳ Nomor Toko : RAMIYIE After the payment is successful, please send proof of transfer or a screenshot of the payment as verification. 🌟

12 May 2026, 04:09 UTC34 viewsread 15 August 2026
Photo

βœ‰οΈ Please proceed with payment with the account details below. πŸ’Έ Payment OVO πŸ’Έ ↳ Nomor : 087740870993 ↳ Nama : mega ***i After the payment is successful, please send proof of transfer or a screenshot of the payment as verification🌟

10 May 2026, 08:04 UTC73 viewsread 15 August 2026
Photo

🌟 Please proceed with payment with the account details below. 😱 Payment ShopeePay 😱 ↳ Nomor : 087740870993 ↳ Nama : mega ***i After the payment is successful, please send proof of transfer or a screenshot of the payment as verification. 🌟

10 May 2026, 08:04 UTC68 viewsread 15 August 2026
Photo

🌟 Please proceed with payment with the account details below. πŸ’‹ Payment Gopay πŸ’‹ ↳ Nomor : 087740870993 ↳ Nama : siora After the payment is successful, please send proof of transfer or a screenshot of the payment as verification. 🌟

10 May 2026, 08:02 UTC63 viewsread 15 August 2026
Photo

πŸ«₯ Please proceed with payment with the account details below. πŸ˜„ Payment Dana πŸ˜„ ↳ Nomor : 087740870993 ↳ Nama : HAYATI ↳ Link : siora After the payment is successful, please send proof of transfer or a screenshot of the payment as verification. 🌟

10 May 2026, 07:58 UTC65 viewsread 15 August 2026
Photo

𝓦elcome to this transaction room. Please select the payment service you require and proceed with your transaction comfortably. 🌟 ✦ 𝐃𝐀𝐍𝐀 🌟 ✦ π†πŽππ€π˜ 🌟 ✦ π’π‡πŽππ„π„ππ€π˜ 🌟 ✦ ππ‘πˆπ’ 🌟 ✦ πŽπ•πŽ Once payment is complete, please send proof of transfer or a screenshot of the payment for verification. Thank you for completing your transaction here β€” good luck! Belongs to @jungahyer

Showing the 12 most recent of 13 posts we hold for @gsaldo. 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 August 2026 β€” this entry's latest reading, not the date you are reading this.

β€œΟΞ±π—’κ­‘π–Ύπ“£π—β€ (@gsaldo), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/gsaldo.

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.