Бесконечно рада, что связала свою жизнь с ролью вожатой ❤️🔥
custom 545188158259384993513custom 59539571520527481385

Channel
@reynevercry
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
302subscribers
-4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002380580032 |
|---|---|
| Type | Channel |
| Username | @reynevercry |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/reynevercry |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 04:56 | 302 | -1 |
| 30 Aug 2026, 21:35 | 303 | -2 |
| 24 Aug 2026, 01:14 | 305 | -1 |
| 8 Aug 2026, 19:00 | 306 | no change |
| 8 Aug 2026, 18:47 | 306 | first reading |
19 posts held, back to 12 May 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 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
716 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 31.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5244870902025312054 | 222 | 31.0% | |
| custom 5404850483816832388 | 121 | 16.9% | |
| custom 5451881582593849935 | 99 | 13.8% | |
| custom 5310283352727635519 | 94 | 13.1% | |
| custom 5451875105783168761 | 83 | 11.6% | |
| custom 5953957152052748138 | 53 | 7.40% | |
| 🕊 | 44 | 6.15% |
Custom emoji. 6 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 19 of the 19 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 716 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 12 May 2026 to 8 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.
Бесконечно рада, что связала свою жизнь с ролью вожатой ❤️🔥
custom 545188158259384993513custom 59539571520527481385
Заодно покажу, где Рей пропадала, пхпхп
custom 59539571520527481385custom 54518815825938499351
Хотите поделюсь частичкой себя? Кусочком лета, так сказать👀
custom 54518815825938499357custom 59539571520527481383
Posted without readable text
custom 545188158259384993513custom 59539571520527481389
ﮩﮩﮩ٨ـﮩ٨ـﮩﮩ٨ wolf!Castiel ﮩ٨ﮩﮩ٨ـﮩ٨ـﮩ
custom 545188158259384993526custom 595395715205274813823
Стая, я вернулась 🤙 Защищала диплом, но теперь я с вами ⛓💥🖤
custom 545188158259384993521
Не могу не поделиться маленькой радостью, теперь айпад похож на скетчбук🕊✨
🕊23custom 545188158259384993512custom 59539571520527481386
Скоро лето🌼
🕊21custom 54518815825938499356custom 59539571520527481382
АУ, где Кастиель вместо пустоты попадает в прошлое и случайно сталкивается с мелким Дином 🌟🌟
custom 524487090202531205427custom 531028335272763551916custom 545187510578316876110custom 54048504838168323884
Всех с первым днём лета кстати, вовремя я написала, да)🐶 Всем желаю удачно сдать сессии и экзамены☺️✊
custom 531028335272763551921custom 54048504838168323886custom 52448709020253120544
🅱️🅱️🅱️🅱️📌📌🅱️🅱️🅱️🅱️ «Взаперти»
custom 524487090202531205427custom 540485048381683238822custom 531028335272763551917custom 54518751057831687612
💫💫💫👁️🪽🌟📌👁️✨✨✨ «Ангел-хранитель»
custom 524487090202531205431custom 540485048381683238826custom 545187510578316876114custom 53102833527276355194
Showing the 12 most recent of 19 posts we hold for @reynevercry. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“⛓️ ℝ𝕖𝕪𝕖𝕔𝕙𝕜𝕒 🤍 🕊” (@reynevercry), 302 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/reynevercry.
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.