Telegram RegisterThe public register of Telegram
Telegram profile photo for Морось

Channel

Морось

@morossssya

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

195subscribers

+2 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002159225540
TypeChannel
Username@morossssya
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live1 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/morossssya

Growth

1931951949 August 2026 — 193 subscribers10 August 2026 — 194 subscribers1 September 2026 — 195 subscribers9 August 20261 September 2026
3 measurements spanning 23 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 193–195 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 03:28195+1
10 Aug 2026, 02:31194+1
9 Aug 2026, 06:30193first reading

Engagement

17 posts held, back to 24 January 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 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 17 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

622 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 28.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 519085364809932955817528.1%
custom 519077738236505661513822.2%
9915.9%
custom 5190444896061771013426.75%
custom 5190905230656557979396.27%
🍌386.11%
🐳335.31%
🍓243.86%
custom 5190775406680099061233.70%
71.13%
custom 519068178498298159140.643%

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 14 of the 17 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 622 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 24 January 2026 to 3 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.

Recent posts

3 Aug 2026, 03:00 UTC87 views44 reactionsread 9 August 2026
Photo

☁️

custom 519085364809932955820custom 5190777382365056615163🐳3custom 51909052306565579792

Signed Tatyana Ezzhalova

19 Jul 2026, 10:48 UTC287 views61 reactionsread 9 August 2026
Photo

💕🪷

custom 519077738236505661527custom 519085364809932955815🍌76🐳2custom 51904448960617710132custom 51907754066800990611custom 51909052306565579791

Signed Tatyana Ezzhalova

6 Jul 2026, 02:05 UTC395 views60 reactionsread 9 August 2026
Photo

Артфайт месть

custom 519085364809932955823custom 519077738236505661518custom 519044489606177101395🐳2🍌1custom 51906817849829815911custom 51909052306565579791

Signed Tatyana Ezzhalova

3 Jul 2026, 05:58 UTC204 views5 reactionsread 9 August 2026

🥹💕

🍌31🐳1

Signed Tatyana Ezzhalova

3 Jul 2026, 05:58 UTC228 views20 reactionsread 9 August 2026
Forwarded from @marengoooooPhoto

Танцуй, танцуй, пока не сбросишь ты оков Пока не стопчешь двести пар железных башмаков Первоатака для @morossssya 🎪

custom 519044489606177101394🍌41🍓1🐳1

Signed Tatyana Ezzhalova

2 Jul 2026, 23:05 UTC188 views13 reactionsread 9 August 2026

💖💖💖!!!

6🍌3🐳2custom 51907754066800990611custom 51907773823650566151

Signed Tatyana Ezzhalova

2 Jul 2026, 23:05 UTC196 views24 reactionsread 9 August 2026
Forwarded from @MaplewinddPhoto

Тут птичка напевает! Ах, погодите Сорока, точно... Тут блестяшку принесли! для Мороси 🌀 🤩 #Artfight2026

11custom 51908536480993295585🐳3custom 51907773823650566152🍌1custom 51904448960617710131custom 51906817849829815911

Signed Tatyana Ezzhalova

2 Jul 2026, 03:57 UTC329 views62 reactionsread 9 August 2026
Photo

Атака на артфайт для Блэкчеррика😜

custom 519085364809932955825🍌17custom 5190905230656557979106🍓1🐳1custom 51907754066800990611custom 51907773823650566151

Signed Tatyana Ezzhalova

2 May 2026, 13:07 UTC320 views66 reactionsread 9 August 2026
Photo

С днём грязных скетчей

custom 519077738236505661527🍓219custom 51909052306565579793🐳2custom 51908536480993295582custom 51906817849829815911custom 51907754066800990611

Signed Tatyana Ezzhalova

22 Apr 2026, 09:13 UTC570 views70 reactionsread 9 August 2026
Photo

🌌🐦

custom 519085364809932955833custom 51907754066800990611813custom 51909052306565579793🐳1custom 51904448960617710131custom 51907773823650566151

Signed Tatyana Ezzhalova

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

Forward network

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.

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

“Морось” (@morossssya), 195 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/morossssya.

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.