Telegram RegisterThe public register of Telegram
Telegram profile photo for ریتــــم خلســــه

Channel

ریتــــم خلســــه

@RITMEKHALSE

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

25,790subscribers

+828 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003936147735
TypeChannel
Username@RITMEKHALSE
CreatedBetween 1 April 2026 and 15 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/RITMEKHALSE

Topic

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 88% 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

24,94425,83325,388.57 August 2026 — 24,962 subscribers8 August 2026 — 24,951 subscribers9 August 2026 — 24,944 subscribers10 August 2026 — 24,984 subscribers11 August 2026 — 25,012 subscribers12 August 2026 — 25,017 subscribers12 August 2026 — 25,024 subscribers14 August 2026 — 25,052 subscribers15 August 2026 — 25,052 subscribers15 August 2026 — 25,071 subscribers17 August 2026 — 25,077 subscribers18 August 2026 — 25,076 subscribers19 August 2026 — 25,089 subscribers20 August 2026 — 25,091 subscribers21 August 2026 — 25,114 subscribers24 August 2026 — 25,132 subscribers25 August 2026 — 25,138 subscribers26 August 2026 — 25,156 subscribers27 August 2026 — 25,166 subscribers28 August 2026 — 25,205 subscribers29 August 2026 — 25,284 subscribers30 August 2026 — 25,347 subscribers31 August 2026 — 25,399 subscribers1 September 2026 — 25,450 subscribers2 September 2026 — 25,481 subscribers3 September 2026 — 25,538 subscribers5 September 2026 — 25,582 subscribers9 September 2026 — 25,737 subscribers11 September 2026 — 25,816 subscribers13 September 2026 — 25,833 subscribers15 September 2026 — 25,829 subscribers17 September 2026 — 25,806 subscribers19 September 2026 — 25,790 subscribers25,7907 August 202619 September 2026
33 measurements spanning 43 days, net +828. 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 24,811–25,966 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 17:3525,790-16
17 Sept 2026, 03:5525,806-23
15 Sept 2026, 07:0025,829-4
13 Sept 2026, 14:2125,833+17
11 Sept 2026, 17:1725,816+79
9 Sept 2026, 03:1925,737+155
5 Sept 2026, 19:4225,582+44
3 Sept 2026, 16:0225,538+57
2 Sept 2026, 07:1325,481+31
1 Sept 2026, 04:0725,450+51
31 Aug 2026, 03:3625,399+52
30 Aug 2026, 03:3425,347+63
29 Aug 2026, 06:4525,284+79
28 Aug 2026, 06:3425,205+39
27 Aug 2026, 05:5525,166+10
26 Aug 2026, 08:3625,156+18
25 Aug 2026, 12:0625,138+6
24 Aug 2026, 08:4525,132+18
21 Aug 2026, 07:3625,114+23
20 Aug 2026, 07:3425,091first reading

Engagement

No public post preview. We read this entry on 15 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

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

“ریتــــم خلســــه” (@RITMEKHALSE), 25,790 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/RITMEKHALSE.

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.