Telegram RegisterThe public register of Telegram

Channel

ПЕРЕЕЗД 𝖲𝗈𝗈𝖲𝗁𝗎 𝗅𝗈𝗏𝖾𝗋 優しさ ❄ #MONO

@sooshulov

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

84subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002406315498
TypeChannel
Username@sooshulov
DescriptionMeowha's gallery 🤍🩶 ПОСТ С СУШУ https://t.me/sooshulov/33348?single Сушу лавер !!! @Myahaanon36bot
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
On Telegramt.me/sooshulov

Growth

848584.57 August 2026 — 85 subscribers7 August 2026 — 84 subscribers9 August 2026 — 84 subscribers7 August 20269 August 2026
3 measurements spanning 2 days, 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 84–85 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 17:1884no change
7 Aug 2026, 21:2084-1
7 Aug 2026, 15:5885first reading

Engagement

10 posts held, back to 28 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 10 posts for this entry, the most recent from 25 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1,820
Links
382

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

25 Mar 2026, 19:43 UTC58 viewsread 9 August 2026

https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover

10 Mar 2026, 15:45 UTC79 viewsread 9 August 2026

https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover https://t.me/sooshulover

10 Mar 2026, 15:43 UTCviews —

Channel name was changed to «ПЕРЕЕЗД 𝖲𝗈𝗈𝖲𝗁𝗎 𝗅𝗈𝗏𝖾𝗋 優しさ ❄ #MONO»

10 Mar 2026, 15:41 UTC73 viewsread 9 August 2026

всем привет переезд на @sooshulover да, архив остаётся по Сушу!! просто актив упал ещё давно, но я всё равно часто делала посты и активно продвигалась, но в последнее время я сама никак не активлю.. поэтому я решила начать всё с чистого листа!!! как бы больно и сложно делать это мне не было:(.. спасибо этому каналу и всем тем, кто следил за ним:) переходите если хотите следить за мной и дальше!! этот канал и весь мт

9 Mar 2026, 09:30 UTC50 viewsread 9 August 2026
Photo

ㅤ# HAPᎮ¥ SOᎧ.JIN DΔY !! - 0903 « grꪖнge » мυmо алLей _ ; ♥️ έναν и гα - ℘ажéй ㅤㅤㅤчтσ Ṯa : кōe люb * ꪜь, " 血な ? коғᦔа тҿβе 18?

4 Mar 2026, 11:50 UTC123 viewsread 9 August 2026
Photo

i∂éa fθr a pr् : φile for υ ㅤㅤվ nαмe : 面白い ㅤㅤशु b * i0 : gîve m3 oNe гσoд hön - e꯱t ki$s ꪖnd I'лl be al.rigհt

4 Mar 2026, 11:50 UTC106 viewsread 9 August 2026
Photo

ㅤॡ Sőo iNst - ꪖgŕam 25Feᑲrυąr√ ㅤㅤㅤㅤзáл.8zу пिд сꪜü : тꫀр, в сαm‌ॄе сĘрdце : « lùv » !! ㅤㅤㅤㅤㅤøбнꪊми меηя ‥ 愛

1 Mar 2026, 13:30 UTC139 viewsread 9 August 2026
Photo

ㅤㅤㅤㅤ; Mu : s1c Shőw wěeķ 1 beħiꪀд the scɆ.нes ❞ 74℉ I d0η't gi - вe a fuÇk abσυt λoꪜe Ꮗ 'CaüSe we aꭈׁׅe 아이들 uհ 伯 ㅤу𐒄ри, еćlи м5.nя не любꪊшьヾ!

28 Feb 2026, 09:40 UTC201 viewsread 9 August 2026
Photo

ㅤSynčo.пaŦion 2ñd dαy in Se૭ul ೯ ㅤㅤㅤглäzа ꪗ сtр6ха, ӄак пρа - вилσ, вел : ꪊки ती ૪ ι-Đle Wørľd t0ur ' « o£tèn » ぬ゙

Showing the 10 most recent of 10 posts we hold for @sooshulov. 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

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

“ПЕРЕЕЗД 𝖲𝗈𝗈𝖲𝗁𝗎 𝗅𝗈𝗏𝖾𝗋 優しさ ❄ #MONO” (@sooshulov), 84 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/sooshulov.

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.