Telegram RegisterThe public register of Telegram

Channel

переезд / ros.88

@rossiioo

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

78subscribers

-1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001996254157
TypeChannel
Username@rossiioo
CreatedBetween 1 October 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/rossiioo

Growth

787978.512 Aug 2026, 10:05 — 79 subscribers12 Aug 2026, 10:15 — 79 subscribers13 Aug 2026, 01:25 — 78 subscribers12 Aug 2026, 10:0513 Aug 2026, 01:25
3 measurements taken within a single day, net -1. 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 78–79 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:2578-1
12 Aug 2026, 10:1579no change
12 Aug 2026, 10:0579first reading

Engagement

20 posts held, back to 12 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 30 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

560 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 28.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 534827809371694300015928.4%
💘8915.9%
custom 53485104256778560857513.4%
custom 53484821862678841946912.3%
custom 53485847457919437536712.0%
custom 5348449011940488495396.96%
👾325.71%
custom 5348077785032192138305.36%

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 areTelegram’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 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 560reactions 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 12 February 2026 to 30 May 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.

Recent posts

30 May 2026, 07:29 UTC54 viewsread 12 August 2026

чёт вас тут всё ещё дохуя..🥺

Signed https://rossi0.88

8 Mar 2026, 09:41 UTC143 views9 reactionsread 12 August 2026

и вновь напоминаю про переезд. Свастона, вернись в стаю, молю💩

💘5👾4

Signed rosiio

1 Mar 2026, 07:03 UTC180 views9 reactionsread 12 August 2026

вы чо.. переезд.. ну пожалуйста 😭

💘6👾3

Signed rosiio

24 Feb 2026, 12:40 UTC217 views6 reactionsread 12 August 2026

млелеле перееезд,не забываем 🎧 всех жду всех жду

👾6

Signed rosiio

23 Feb 2026, 05:05 UTC230 views14 reactionsread 12 August 2026

напоминаю про переезд🎧

👾14

Signed rosiio

22 Feb 2026, 16:15 UTC241 views16 reactionsread 12 August 2026

мьмь.. вроде оформила всё что нужно. Данный канал удалять не стану, оставлю как архив, как минимум для себя. Всех мью и вз попрошу просто отметиться под спец.постом в новом канале что вы все на месте, чтобы я никого не теряла. Итак, Роса начинает свой путь с самого начала, опять,ахах https://t.me/rosiiioo https://t.me/rosiiioo https://t.me/rosiiioo

💘11👾5

Signed rosiio

22 Feb 2026, 14:52 UTC204 views14 reactionsread 12 August 2026

🍪┊если сделаю переезд, это будет мой четвёртый канал🎧

custom 534827809371694300014

Signed rosiio

22 Feb 2026, 14:46 UTC175 views18 reactionsread 12 August 2026

🍪┊знаете что🎧 подумываю очередной переезд сделать. Но с одной стороны так жаль этот канал, а с другой хочу видеть в канале тех, кто реально замечает Меня. Блем.. Хочется поменять всё и вся, начать всё заново. Да, жалко такую цифру терять, лично мне, но ведь, захочу - наберу снова, так ведь?. Как вы относитесь к этому?🎧

custom 534851042567785608518

Signed rosiio

22 Feb 2026, 07:51 UTC150 views43 reactionsread 12 August 2026
Photo

はい 🍪┊ ɴᴇᴡ ᴘᴏsᴛ♡ 🤍🤍✦ ме.. решила поиграться с текстурами всякими. Вроде неплохо вышло. ꒰ 𝙩𝙖𝙜𝙨 ꒱ // #ОС ꒰ ´ ˘꒱੭ 。 rosiio 𓂃 👾 ♡♡

custom 534827809371694300019custom 534851042567785608513custom 534858474579194375310custom 53480777850321921381

Signed rosiio

21 Feb 2026, 14:30 UTC114 views43 reactionsread 12 August 2026
Photo

🍪┊как же он ахуено тут выглядит, я хз буду ли доделывать

custom 534827809371694300020custom 534807778503219213814custom 53485847457919437538💘1

Signed rosiio

21 Feb 2026, 13:05 UTC113 views36 reactionsread 12 August 2026
Photo

はい 🍪┊ ɴᴇᴡ ᴘᴏsᴛ♡ 🤍🤍✦ БЛЯТЬ ЭТО АХЦЕНО от любимы жирочан ꒰ 𝙩𝙖𝙜𝙨 ꒱ // #ОС ꒰ ´ ˘꒱੭ 。 rosiio 𓂃 👾 ♡♡

custom 534827809371694300019custom 534851042567785608511💘5custom 53484490119404884951

Signed rosiio

21 Feb 2026, 10:53 UTC96 views45 reactionsread 12 August 2026
Photo

はい 🍪┊ ɴᴇᴡ ᴘᴏsᴛ♡ 🤍🤍✦ Мел...Ме..Мелоди.. бляха меня даже на полноценку хватило, ахуеть ꒰ 𝙩𝙖𝙜𝙨 ꒱ // #фдарт ꒰ ´ ˘꒱੭ 。 rosiio 𓂃 👾 ♡♡

custom 534848218626788419422custom 534827809371694300013custom 53480777850321921389💘1

Signed rosiio

Showing the 12 most recent of 20 posts we hold for @rossiioo. 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.

Citation-graph rank

Citation-graph rank — 631,187 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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.

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

“переезд / ros.88” (@rossiioo), 78 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/rossiioo.

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.