
Channel
RTM - orisFX
@orisfxRTM
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,297subscribers
-14 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001732227129 |
|---|---|
| Type | Channel |
| Username | @orisfxRTM |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/orisfxRTM |
Topic
Crypto & trading — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 20:00 | 3,297 | -4 |
| 9 Nov 2026, 07:46 | 3,301 | +4 |
| 6 Nov 2026, 05:27 | 3,297 | +2 |
| 31 Oct 2026, 02:11 | 3,295 | -8 |
| 27 Oct 2026, 23:36 | 3,303 | +14 |
| 24 Oct 2026, 15:28 | 3,289 | -3 |
| 21 Oct 2026, 22:20 | 3,292 | -1 |
| 18 Oct 2026, 13:05 | 3,293 | +4 |
| 13 Oct 2026, 00:49 | 3,289 | -1 |
| 6 Oct 2026, 17:39 | 3,290 | -2 |
| 30 Sept 2026, 04:41 | 3,292 | +6 |
| 19 Sept 2026, 11:40 | 3,286 | +2 |
| 9 Sept 2026, 20:18 | 3,284 | no change |
| 6 Sept 2026, 12:18 | 3,284 | -7 |
| 1 Sept 2026, 17:33 | 3,291 | -3 |
| 29 Aug 2026, 13:16 | 3,294 | -2 |
| 26 Aug 2026, 13:23 | 3,296 | -6 |
| 23 Aug 2026, 09:38 | 3,302 | -3 |
| 20 Aug 2026, 05:55 | 3,305 | -3 |
| 17 Aug 2026, 13:44 | 3,308 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@tsestocks · 25,937
Telegram ranks this channel #27 of 92 here — alongside 91 others — read 12 September 2026
@sholeghalamkar1 · 21,905
Telegram ranks this channel #51 of 92 here — alongside 91 others — read 24 September 2026
@uniquegoldd · 107,714
Telegram ranks this channel #57 of 60 here — alongside 59 others — read 16 August 2026
@BaaTrader · 26,332
Telegram ranks this channel #59 of 87 here — alongside 86 others — read 12 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“RTM - orisFX” (@orisfxRTM), 3,297 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/orisfxRTM.
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.