Telegram RegisterThe public register of Telegram
Telegram profile photo for Roleplay Sq Promote

Channel

Roleplay Sq Promote

@RoleplaySqpromote

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

346,394subscribers

-5,745 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1001201395902
TypeChannel
Username@RoleplaySqpromote
DescriptionBot Sendbio @sendpromotebot List Channel SFS @RoleplaySFS jualbeli @jual_beli_grosir Grup @promotelpm ----- admin @fellixleskz
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held36
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/RoleplaySqpromote

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 82% 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.

Growth

346,394352,139349,266.56 August 2026 — 352,139 subscribers6 August 2026 — 352,139 subscribers7 August 2026 — 352,047 subscribers8 August 2026 — 351,833 subscribers8 August 2026 — 351,699 subscribers9 August 2026 — 351,456 subscribers10 August 2026 — 351,147 subscribers12 August 2026 — 350,841 subscribers13 August 2026 — 350,683 subscribers14 August 2026 — 350,461 subscribers16 August 2026 — 350,231 subscribers17 August 2026 — 350,007 subscribers18 August 2026 — 349,770 subscribers19 August 2026 — 349,540 subscribers20 August 2026 — 349,595 subscribers21 August 2026 — 349,558 subscribers23 August 2026 — 349,379 subscribers24 August 2026 — 349,215 subscribers25 August 2026 — 349,172 subscribers26 August 2026 — 349,133 subscribers27 August 2026 — 349,259 subscribers28 August 2026 — 349,191 subscribers29 August 2026 — 349,167 subscribers30 August 2026 — 349,152 subscribers31 August 2026 — 349,061 subscribers1 September 2026 — 348,971 subscribers2 September 2026 — 348,728 subscribers3 September 2026 — 348,708 subscribers5 September 2026 — 348,576 subscribers8 September 2026 — 348,259 subscribers11 September 2026 — 347,923 subscribers13 September 2026 — 347,716 subscribers15 September 2026 — 347,794 subscribers17 September 2026 — 347,788 subscribers19 September 2026 — 347,430 subscribers26 September 2026 — 346,394 subscribers6 August 202626 September 2026
36 measurements spanning 51 days, net -5,745. 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 345,532–353,001 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)SubscribersChange
26 Sept 2026, 11:40346,394-1,036
19 Sept 2026, 14:59347,430-358
17 Sept 2026, 04:38347,788-6
15 Sept 2026, 03:58347,794+78
13 Sept 2026, 10:18347,716-207
11 Sept 2026, 12:02347,923-336
8 Sept 2026, 17:41348,259-317
5 Sept 2026, 07:37348,576-132
3 Sept 2026, 09:48348,708-20
2 Sept 2026, 05:43348,728-243
1 Sept 2026, 02:47348,971-90
31 Aug 2026, 02:58349,061-91
30 Aug 2026, 06:06349,152-15
29 Aug 2026, 08:16349,167-24
28 Aug 2026, 11:13349,191-68
27 Aug 2026, 13:44349,259+126
26 Aug 2026, 16:22349,133-39
25 Aug 2026, 19:17349,172-43
24 Aug 2026, 21:07349,215-164
23 Aug 2026, 08:24349,379first reading

Engagement

2,340 posts held, back to 6 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 117 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.012%
avg views ÷ 346,394 subscribers
Avg views / post
40.1
1,200 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1,200
of 2,340 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 October 2026
Posts held2,340 (6 August 2026 – 2 October 2026)
Views total48,151
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Oct 2026, 08:35 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.

What this channel posts

Photos
≈1
Links
≈258,000

Lifetime counters from Telegram’s own channel header, read 2 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

2 Oct 2026, 08:34 UTC1 viewsread 2 October 2026

juhoon #rpsp temenan atau demenan? [ Jju vnx ] @ctolestt 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:34 UTC2 viewsread 2 October 2026

keonho #rpsp temenan atau demenan? [ Abas Kemal. ] @iKeontho 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:33 UTC7 viewsread 2 October 2026

juhoon #rpsp aku mau nawarin cc, chat yang mau join [ harp ] @vquines 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:33 UTC7 viewsread 2 October 2026

yeonju #rpsp aku mau cari fambest, fams or besti? ayo chat [ ivy ailydore. ] @chwaracters 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:33 UTC8 viewsread 2 October 2026

Anon sess #rpsp temenan atau demenan? [ Ali, زَيَّان. ] @qelayapan 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:33 UTC8 viewsread 2 October 2026

#rpsp wlw temenan atau demenan? [ Cassidy Rhodes @BolehHello ] @caddyse 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:33 UTC8 viewsread 2 October 2026

cantik #rpsp aku mau cari pacar, kiw deketan [ Shaziá Ärney ] @sweetsweeat 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:33 UTC9 viewsread 2 October 2026

Sunghoon #rpsp temenan atau demenan? [ Halfdan pathetic ] @kanekikefn 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:32 UTC11 viewsread 2 October 2026

titut nyimut #rpsp temenan atau demenan? [ 𓏼 ♡𐬹ᛧ @𝓡 𝒂𝒃𝒆𝒓𝒚 𝒈𝒆𝒓𝒍𝒊𝒂𝒏𝒂 ] @beiberryie 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:32 UTC12 viewsread 2 October 2026

west #rpsp aku mau cari pacar, kiw deketan [ careen ] @careenvxx 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:32 UTC11 viewsread 2 October 2026

yuha wlw #rpsp temenan atau demenan? [ (♡) 𓂃 ellie: 🩷 ] @stellwau 󠀠

Signed Roleplay Sq Promote

2 Oct 2026, 08:32 UTC11 viewsread 2 October 2026

eric #rpsp hts / fwa ? [ ISSAC. ] @Kasefw 󠀠

Signed Roleplay Sq Promote

Showing the 12 most recent of 2,340 posts we hold for @RoleplaySqpromote. 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 3 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.

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

“Roleplay Sq Promote” (@RoleplaySqpromote), 346,394 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/RoleplaySqpromote.

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.