Channel
@rakeraves
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
78subscribers
-2 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003866874175 |
|---|---|
| Type | Channel |
| Username | @rakeraves |
| Created | Between 1 February 2026 and 9 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/rakeraves |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 22:38 | 78 | -1 |
| 26 Aug 2026, 10:14 | 79 | -2 |
| 19 Aug 2026, 04:13 | 81 | +1 |
| 11 Aug 2026, 07:11 | 80 | no change |
| 10 Aug 2026, 10:46 | 80 | first reading |
20 posts held, back to 9 February 2026 — the 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
224 reactions across 13 posts, in 14 distinct kinds. The most used accounts for 19.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5330449894924650657 | 44 | 19.6% | |
| custom 5415759997101430996 | 38 | 17.0% | |
| custom 5330512571382385456 | 27 | 12.1% | |
| custom 5341798229312813103 | 27 | 12.1% | |
| custom 5192958349578099585 | 23 | 10.3% | |
| custom 5307680319078420359 | 23 | 10.3% | |
| custom 5352569010858776043 | 22 | 9.82% | |
| custom 5244882184904413858 | 5 | 2.23% | |
| custom 5462974890413933081 | 5 | 2.23% | |
| 👀 | 3 | 1.34% | |
| 👻 | 3 | 1.34% | |
| custom 5339082465656982317 | 2 | 0.893% | |
| custom 5463385914489191832 | 1 | 0.446% | |
| 🕊 | 1 | 0.446% |
Custom emoji. 11 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 13 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 224 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 9 February 2026 to 9 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rakeraves. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 9 February 2026 to 9 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
💌СЦЕНАРИЙ НЕ СОГЛАСОВАН. By @maxeshka 🟫Метки: AU, ревность, БДСМ, жёсткий секс, анальный секс, незащищённый секс, обездвиживание. 🟫Для прочтения: телеграф ; фикбук 📌Навигация • Другие работы по лидинтам #лидинты #нсфв
custom 53305125713823854562custom 53304498949246506571
Signed лина рейк
эпизодическое пьянство ❗TW: шутки про секс, алкоголь, наркотики❗ ʙᴄᴇ, чᴛо ᴨᴩидуʍᴀно, ᴄдᴇᴧᴀно и ᴄᴋᴀзᴀно ʍной, яʙᴧяᴇᴛᴄя ᴧиɯь ᴨᴧодоʍ буᴩноᴦо ʙообᴩᴀжᴇния и хоᴩоɯо ᴩᴀзʙиᴛой ɸᴀнᴛᴀзии. ничᴇᴦо нᴇ ᴨᴩоᴨᴀᴦᴀндиᴩую и нᴇ нᴀʙязыʙᴀю! #пиробукеры #стэдд #зарисовка #эпизодическоепьянство
custom 53305125713823854566custom 53304498949246506573👀2custom 52448821849044138581
Signed лина рейк
мне показалось это букер я схожу с ума
👻1custom 53305125713823854561
Signed лина рейк
когда пирыча ебал чо на жопе написал
Signed лина рейк
обнова, друзья, обнова, новый ЩИТПОСТ
Signed лина рейк
вот это #процесс
Signed лина рейк
#спойлеры
custom 53304498949246506572
Signed лина рейк
🤩 . . ➖➖➖➖. . #shelsh Рактив ➖_ 🤩 ➿➿➿ 🤩 «„➿#я вам: ¹. вы как причина жить, 🤩². вы как проявление любви, 🤩³. вы как триггер песня, 🤩🤩 ➿ «„ 😆 #вы мне: ¹. подписку, + репост в канал (3 друзьям) 🤩. реакция, (1,3) 🤩. скрин, 🤩. ожидание ! 🥺 МЕСТА НЕ ОГРАНИЧЕНЫ!!!!!!!!
Signed лина рейк
кароч мож вернусь мож нет всем пака)
Signed rake
друзья я ухожу из интернета
custom 54157599971014309966
Signed rake
song.link
Signed rake
ᴨоᴋой нᴀʍ ᴛоᴧьᴋо ᴄниᴛᴄя 1/? И вечный бой. Покой нам только снится. И пусть ничто не потревожит сны. Седая ночь, и дремлющие птицы качаются от синей тишины. ❗TW: травмирующее прошлое, абьюзивные отношения, обилие нецензурной лексики, паранойя, курение ❗ ʙᴄᴇ, чᴛо ᴨᴩидуʍᴀно, ᴄдᴇᴧᴀно и ᴄᴋᴀзᴀно ʍной, яʙᴧяᴇᴛᴄя ᴧиɯь ᴨᴧодоʍ буᴩноᴦо ʙообᴩᴀжᴇния и хоᴩоɯо ᴩᴀзʙиᴛой ɸᴀнᴛᴀзии. ничᴇᴦо нᴇ ᴨᴩоᴨᴀᴦᴀндиᴩую и нᴇ нᴀʙязыʙᴀю! #пироглебы …
custom 541575999710143099617custom 51929583495780995859custom 53304498949246506579custom 52448821849044138583custom 53076803190784203593custom 53305125713823854563👻2👀1
Signed rake
Showing the 12 most recent of 20 posts we hold for @rakeraves. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
@rakeraves named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ᴩᴇйᴋ ᴛᴇхниᴋ” (@rakeraves), 78 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/rakeraves.
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.