⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 need abang & temen @jylatte ──────────── 🪷 # !! ꒰ Nara ꒱ 🥢 🥡; @jylatte
Signed RPRL PROMOTE

Channel
@rprlpromotes
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
19,818subscribers
+150 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003094220348 |
|---|---|
| Type | Channel |
| Username | @rprlpromotes |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/rprlpromotes |
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 10 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 14:02 | 19,818 | -33 |
| 14 Sept 2026, 15:41 | 19,851 | +16 |
| 13 Sept 2026, 00:17 | 19,835 | +1 |
| 11 Sept 2026, 01:38 | 19,834 | +54 |
| 8 Sept 2026, 05:00 | 19,780 | +12 |
| 5 Sept 2026, 03:42 | 19,768 | -4 |
| 3 Sept 2026, 11:38 | 19,772 | +10 |
| 2 Sept 2026, 08:13 | 19,762 | +2 |
| 1 Sept 2026, 09:33 | 19,760 | -5 |
| 31 Aug 2026, 09:07 | 19,765 | -10 |
| 30 Aug 2026, 07:53 | 19,775 | +19 |
| 29 Aug 2026, 04:24 | 19,756 | +1 |
| 28 Aug 2026, 03:27 | 19,755 | +1 |
| 27 Aug 2026, 02:18 | 19,754 | +14 |
| 26 Aug 2026, 02:42 | 19,740 | -2 |
| 25 Aug 2026, 05:58 | 19,742 | +3 |
| 24 Aug 2026, 07:36 | 19,739 | +37 |
| 22 Aug 2026, 18:17 | 19,702 | +11 |
| 21 Aug 2026, 10:07 | 19,691 | +9 |
| 20 Aug 2026, 06:47 | 19,682 | first reading |
78 posts held, back to 1 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 55 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 5 of 31 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 78 (1 August 2026 – 2 September 2026) |
| Views total | 16,818 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:00 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
9 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 88.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 88.9% | |
| 🥰 | 1 | 11.1% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 13 of the 78 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 78 most recent posts we hold, published 1 August 2026 to 2 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 need abang & temen @jylatte ──────────── 🪷 # !! ꒰ Nara ꒱ 🥢 🥡; @jylatte
Signed RPRL PROMOTE
.
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 gua cri temen yang asik yng bisa di ajak ngejamet ayo gas lah ke rc ──────────── 🪷 Jeanna; @Jea_aa
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 temenan ayoo sinii:D ──────────── 🪷 c; @lau_cya
Signed RPRL PROMOTE
⊹🦋 #moots˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 hayuk moots ig and tiktok and wa butkon (ga nerima wa gb) soalnyaa ──────────── 🪷 が. naza; @nazaeil
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 wlw temenan, dom jkt klo bsa ──────────── 🪷 𝐚𝐫𝐚𝐚; @rLecet
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 ada wlw jakarta ga? temenan yu ──────────── 🪷 l; @lopyuuue
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 eh temenan dong pls... need someone to taaaallkkkk😓😓😩 @bolenpjsang ──────────── 🪷 ayvi, 🙉💕🕺🏻💥; @bolenpjsang
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 nyari wlw pls tapi yang gausa cuek btw gua domnya ──────────── 🪷 l; @lopyuuue
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 siapa yg disini nd kakak on cewek?? kebetulan temen aku lagi cari adek cewek yang excited, ga pasif (kalo topik obrolan udh mau abis, inisiatif ngasih topik obrolan baru), suka yapping and cerita random, ga dry text, ga matpik and ga ghosting. yang mau chat aku ya note: yg suka bahas NSFW/18+ chat, matpik, convokiller, ghosting and dry text GA USAH CHAT ‼️ ──────────── 🪷 ೨ৎ’ …
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 ──────────── 🪷 why; @gtaadc
Signed RPRL PROMOTE
⊹🦋 #rplf˳ 🪽 ♡*:·. 💌 💌 💌 💌 💌 💌 💌 💌 💌 💌 Gas temenan sama gw,kalau lu asik gua lebih asik gas ke rc ──────────── 🪷 Jeanna; @Jea_aa
Signed RPRL PROMOTE
Showing the 12 most recent of 78 posts we hold for @rprlpromotes. 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.
@rprlpromotes edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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.
@rprlpromotes named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“RPRL PROMOTE” (@rprlpromotes), 19,818 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/rprlpromotes.
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.