Channel
@RoseSupportChannel
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
16,589subscribers
-209 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001404585808 |
|---|---|
| Type | Channel |
| Username | @RoseSupportChannel |
| Created | 16 December 2019 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/RoseSupportChannel |
Technology — 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 67% 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 |
|---|---|---|
| 17 Sept 2026, 16:40 | 16,589 | -16 |
| 15 Sept 2026, 12:01 | 16,605 | -8 |
| 13 Sept 2026, 21:58 | 16,613 | -18 |
| 12 Sept 2026, 04:20 | 16,631 | -3 |
| 9 Sept 2026, 22:16 | 16,634 | -13 |
| 6 Sept 2026, 17:00 | 16,647 | -21 |
| 3 Sept 2026, 00:08 | 16,668 | -6 |
| 2 Sept 2026, 01:31 | 16,674 | -2 |
| 1 Sept 2026, 00:07 | 16,676 | -4 |
| 31 Aug 2026, 02:53 | 16,680 | -3 |
| 30 Aug 2026, 01:06 | 16,683 | -3 |
| 29 Aug 2026, 00:24 | 16,686 | -7 |
| 27 Aug 2026, 21:35 | 16,693 | +6 |
| 26 Aug 2026, 18:11 | 16,687 | -1 |
| 25 Aug 2026, 16:37 | 16,688 | -17 |
| 24 Aug 2026, 14:52 | 16,705 | -10 |
| 22 Aug 2026, 21:15 | 16,715 | -6 |
| 21 Aug 2026, 07:34 | 16,721 | -7 |
| 20 Aug 2026, 08:55 | 16,728 | -11 |
| 19 Aug 2026, 07:25 | 16,739 | first reading |
11 posts held, back to 16 December 2019 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 54 pages 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 11 posts for this entry, the most recent from 17 December 2019. An engagement rate over an empty window would be a number about nothing.
Channel Overview: Here is the current list of posts in this channel: Adding the bot Admin permissions Message formatting Message Buttons Saving Rules Translations Spam protection CAPTCHA This list will attempt to remain updated as future updates come out. Speaking of updates - join @MarieNews for the latest information on new Rose features. Want your own personal clone, with increased filters, custom pictures, and…
Admin permissions: To avoid slowing down, Rose caches admin rights for each user. This cache lasts about 10 minutes; this may change in the future. This means that if you promote a user manually (without using the /promote command), Rose will only find out ~10 minutes later. To force this, you can use the /admincache command; this will refresh the cache, and update the permissions for all the admins. If you are g…
Formatting your messages: On top of buttons, you can add lots of cool other feature to your rules, notes, filters, and greetings. This is done through mardkown; you can read all about it in the markdown section the /help.
Saving Rules: To set the rules in your chat, use /setrules. You can then add a button which links to your rules in your welcome message by adding {rules} to your welcome message.
Muting new users (captcha): One of Rose's feature is CAPTCHAs. These allow you to mute all new users until they've clicked a "prove you're human" button. This helps to fight spammers, by stopping bots from being able to speak when they join the group. You can enable this using: /captcha on. If you would like to edit the CAPTCHA button text, use /setcaptchatext Whatever you want your text to be.. You can change the …
Spammer protection: Basic measures: - Use antibot measures. Read the help about greetings, specifically about welcomemute. This will stop bots (but not necessarily userbots). - If spammers are using links, open the /help and read about blacklists. You can blacklist certain things, like specific links, and Rose will delete messages that match the blacklisted items. - If your spammers are flooding your group (sending …
If you would like to see a new language appear in Rose, or fix a broken translation, please come join us on Crowdin!
To add Rose to your chats, simply click here and select your chat. You should add her as admin if you intend to use any of her admin features. You can also click on @MissRose_bot, and go to the three dots on the top right of your screen, and select "add to group".
Buttons: This is how buttons are made in Rose. They follow the same logic as normal markdown links - just add a buttonurl://. The following button syntax will create 3 buttons. Button 1 and 2 are on the same line, because of the :same tag on button 2. Button 3 is on a newline, separate, because there is no :same tag. [Button 1](buttonurl://example.com) [Button 2](buttonurl://github.com:same) [Button 3](buttonurl:…
Welcome to the Rose Support channel! Feel free to either read the /help or go to MissRose.org for more information. Note: this is NOT a news channel! See @MarieNews for update notes.
Channel created
Showing the 11 most recent of 11 posts we hold for @RoseSupportChannel. 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.
Named by 2 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Rose Support” (@RoseSupportChannel), 16,589 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/RoseSupportChannel.
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.