Supergroup
Ролевые Игры
@role_play_in_tg
On this record: Growth · Engagement · Citations · Cite this entry
3,435members
+112 since we began measuring on 8 August 2026
706 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002268767470 |
|---|---|
| Type | Supergroup |
| Username | @role_play_in_tg |
| Description | Здесь вы можете найти сюжет на любой вкус, а в придачу к нему и хорошего сорола - автора сюжета! Создавайте и публикуйте свои текстовые сюжеты, ищите соролов, общайтесь или даже виртите 🤭 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 12 |
| On Telegram | t.me/role_play_in_tg |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 8 Sept 2026, 20:47 | 3,435 | no change |
| 6 Sept 2026, 08:57 | 3,435 | +7 |
| 2 Sept 2026, 08:28 | 3,428 | +2 |
| 30 Aug 2026, 16:47 | 3,426 | +10 |
| 28 Aug 2026, 00:58 | 3,416 | +3 |
| 25 Aug 2026, 10:25 | 3,413 | +12 |
| 22 Aug 2026, 10:17 | 3,401 | +18 |
| 18 Aug 2026, 13:48 | 3,383 | +17 |
| 15 Aug 2026, 05:36 | 3,366 | +21 |
| 12 Aug 2026, 02:02 | 3,345 | +20 |
| 8 Aug 2026, 18:50 | 3,325 | +2 |
| 8 Aug 2026, 06:01 | 3,323 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 12 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.
@alliya_home · 671 postCurrant Creek
@curruntcreek · 221 post𝖧𝖧𝖱 - 𝖨𝖭𝖥𝖮 #roleplay #hotelhazbin #hellivaboss
@HHRrol · 331 postWelcome to the hotel Astoria | rp
@hotel_Astoria_rp · 141 postINFO | H.U.R.T.
@HURTrp · 521 post𝐈𝐋𝐋𝐔𝐒𝐈𝐎𝐍 𝐎𝐅 𝐆𝐋𝐎𝐑𝐘.
@infoofhawrolep · 1491 post𝐈𝐍𝐅𝐎 | 𝐋𝐢𝐥𝐢𝐮𝐦 𝐒𝐩𝐨𝐫𝐭𝐢𝐧𝐠 𝐀𝐜𝐚𝐝𝐞𝐦𝐲
@liliumsportingacademy_rp · 651 postNOWHERE | INFO
@NowhereINFORMATION · 291 postИнфо ролевой Астрэя
@Omeshavers_20th_century · 421 post✧ 𝚈𝚞𝚏𝚘𝚛𝚒𝚊 𝚒𝚗𝚏𝚘 *.✧
@somniainformation · 641 post𝐒𝐎𝐍𝐆 𝐎𝐅 𝐎𝐋𝐃 𝐕𝐀𝐋𝐘𝐑𝐈𝐀
@songofoldvalyria · 751 postСквозь тьму — ролевой проект по вселенной Эшамот | Through the darkness — roleplay project of Eshamot universe
@Through_Darkness_RP · 1331 post
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Ролевые Игры” (@role_play_in_tg), 3,435 members as measured 8 September 2026. Telegram Register, tgregister.com/channel/role_play_in_tg.
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.