Telegram RegisterThe public register of Telegram
Telegram profile photo for КЕЙСЫ | Rafael_Russia

Channel

КЕЙСЫ | Rafael_Russia

@RafaeI_Russia

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

164subscribers

+2 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001610591311
TypeChannel
Username@RafaeI_Russia
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live15 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/RafaeI_Russia

Growth

16216416313 August 2026 — 162 subscribers13 August 2026 — 162 subscribers29 August 2026 — 163 subscribers15 September 2026 — 164 subscribers13 August 202615 September 2026
4 measurements spanning 33 days, net +2. 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 162–164 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 01:41164+1
29 Aug 2026, 11:35163+1
13 Aug 2026, 13:00162no change
13 Aug 2026, 12:48162first reading

Engagement

19 posts held, back to 28 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 19 posts for this entry, the most recent from 23 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Jul 2026, 14:15 UTC33 viewsread 13 August 2026

Отзыв участника команды по РКО: От @vv_tkachev #команда

23 Jul 2026, 14:14 UTC34 viewsread 13 August 2026

Очень много полезной инфы, приятная команда которая отвечает даже на самые банальные вопросы. Так же хочу отметить @raafaill, моего куратора, который отлично объясняет сложные вещи простыми словами. Кнопки бабла здесь нет, как и в ЛЮБОМ другом обучении. Но есть много информации про подводные камни и нюансы, которые самостоятельно скорее всего вы бы узнали только спустя кучу ошибок. А так же крутые связки, сильное о

16 Mar 2026, 14:33 UTC769 viewsread 13 August 2026

Отзыв участника команды по РКО: От @bakiev_v_telege #команда

11 Mar 2026, 13:58 UTC673 viewsread 13 August 2026

Отзыв участника команды по РКО: От @aquuam7 #команда

11 Mar 2026, 13:57 UTC≈2,150 viewsread 13 August 2026
Photo

Хотел бы оставить свой о совместной работе в команде RR Team с Рафаэлем По началу занимался продажами на Авито, но это приносило относительно небольшой доход Этого не хватало, мучали мысли чем заниматься, искал информацию в интернете и знакомый предложил зарегестировать карту, заплатив 500 рублей, мне стало интересно что за ниша, начал искать более подробную инфу, наткнулся на канал Рафаэля. Как итог, за пару меся

18 Dec 2025, 22:30 UTC580 viewsread 13 August 2026

Отзыв участника команды по РКО: От @Gress_TG #команда

18 Dec 2025, 22:29 UTC552 viewsread 13 August 2026

Хочу поделиться впечатлениями от команды Рафы: Скажу честно, это лучшее решение за последнее время. Долго думал стоит вступать в команду или нет, но все-таки решился и не прогадал. Первый месяц - чистая прибыль больше, чем сам вход в команду. Рафа и кураторы в команде могут решить любой вопрос. Сам Рафа подготовил четкую базу для работы, разложил все по полочкам. В общем, спасибо Рафе за доступ в команде, коллектив

17 Dec 2025, 22:46 UTC493 viewsread 13 August 2026

Отзыв участника команды по РКО От @Tr0faN #команда

Showing the 12 most recent of 19 posts we hold for @RafaeI_Russia. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“КЕЙСЫ | Rafael_Russia” (@RafaeI_Russia), 164 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/RafaeI_Russia.

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.