Telegram RegisterThe public register of Telegram
Telegram profile photo for 난류 ✷ turbulence

Channel

난류 ✷ turbulence

@wast_ray

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

60subscribers

+2 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-1002481654039
TypeChannel
Username@wast_ray
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live8 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 8 September 2026
On Telegramt.me/wast_ray

Growth

5860597 August 2026 — 58 subscribers10 August 2026 — 58 subscribers24 August 2026 — 59 subscribers31 August 2026 — 60 subscribers7 August 202631 August 2026
4 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 58–60 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 00:2760+1
24 Aug 2026, 09:3559+1
10 Aug 2026, 06:1558no change
7 Aug 2026, 23:1858first reading

Engagement

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

What this channel posts

Video runtime
46s
Average length
15s

Measured directly from 3 videos 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.

Reaction mix

283 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 25.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54449309253495970437125.1%
custom 54204332651168658025720.1%
custom 53304862732976409525318.7%
custom 53212588667746676804616.3%
custom 54316829698760677444214.8%
custom 5317011509191136575124.24%
🕊20.707%

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

Measured over the 12 most recent posts we hold, published 3 August 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.

Recent posts

9 Aug 2026, 16:29 UTC22 views17 reactionsread 10 August 2026
Video

и ещё с (уже прошедшим по корейскому времени) днём рождения самого чудесного волчонка в диадеме🥺🤍 сияй, минги фиксонович!

custom 54449309253495970436custom 53212588667746676805custom 54204332651168658024custom 53304862732976409522

9 Aug 2026, 16:26 UTC23 views15 reactionsread 10 August 2026

а ещё, кстати, никак не могу после кореи привыкнуть к нашему солнцу🫠 мне (даже нам!) уж точно не показалось, в корее оно было более мягким и приятным, тут же оно испепеляет и выедает глаза🥹 матушка-земля встретила парочкой сенсорных перегрузок из-за количества света, я мне плохо с сердцем я задыхаюсь, положите меня пожалуйста туда, откуда взяли😫

custom 54449309253495970436custom 54204332651168658024custom 53212588667746676803custom 53304862732976409522

9 Aug 2026, 16:23 UTC24 views20 reactionsread 10 August 2026

возможно, в следующей жизни я бы была рада стать тем человеком, который "где родился, там и пригодился" но в этой, пожалуй, лучше смирюсь со своей участью и буду сбивать о гравий колени и мысли, чем попросту смирюсь с обстоятельствами

custom 54316829698760677446custom 54204332651168658025custom 54449309253495970434🕊2custom 53170115091911365751custom 53212588667746676801custom 53304862732976409521

9 Aug 2026, 16:22 UTC24 views20 reactionsread 10 August 2026

у меня сегодня первый 'одинокий' вечер спустя некоторое количество времени, и после поездки это одиночество как-то абсолютно по-новому ощущается в целом, разного рода осознания накрывают всё чаще и всё сильнее, и иногда кажется, что они пытаются помочь какими-то варварскими методами – всё пинают вперёд, говоря лишь отдельные слова и не выстраивая чёткого тз. так сложно привыкнуть к обыденности не было ещё никогда, ч

custom 54449309253495970437custom 53304862732976409526custom 53170115091911365753custom 53212588667746676802custom 54204332651168658022

9 Aug 2026, 05:36 UTC34 views22 reactionsread 10 August 2026

никогда бы не подумала, что вот так залипну однажды именно на саншайне, вот честно... да, были за это время "вспышки" любви к нему, как и ко всем мемберам помимо биас-лайна, но чтобы так долго и так упорно😫

custom 54204332651168658028custom 54449309253495970436custom 53212588667746676805custom 53304862732976409523

9 Aug 2026, 05:34 UTC34 views24 reactionsread 10 August 2026
Photo

отныне я, видимо, в заложниках у этой сладкой парочки, и не знаю, что с этим делать (пока и не планирую ничего делать🤓) сеульское помешательство на сане не заканчивается и не проходит бесследно

custom 54316829698760677449custom 53304862732976409526custom 54449309253495970436custom 54204332651168658023

7 Aug 2026, 04:19 UTC43 views19 reactionsread 10 August 2026

гайз, почему вы это всё не устроили, пока мы были в сеуле?😫😫

custom 54204332651168658027custom 53212588667746676805custom 53304862732976409525custom 54449309253495970432

4 Aug 2026, 00:11 UTC68 views30 reactionsread 10 August 2026

и самый чувственный экспириенс в жизни – слушать на рассвете turbulence в автобусе на пути в инчхон...

custom 54316829698760677449custom 54449309253495970438custom 53304862732976409527custom 53212588667746676804custom 54204332651168658022

4 Aug 2026, 00:08 UTC68 views30 reactionsread 10 August 2026
Photo

вот и всё, сегодня уже стартуем обратно к дому (пусть и в поисках своего дальнейшего home) сразу в голове голос макса из кухни и "ну вот и всё, хорошая получилась история...", ведь история правда получилась хорошая и абсолютно незабываемая👁️ и как будто это только начало. ещё обязательно свидимся! спасибо корее за этот опыт, а самое главное – спасибо за него моим милым прекрасным девочкам и судьбе, которая с ними с

custom 532125886677466768010custom 54204332651168658029custom 54449309253495970438custom 53304862732976409523

3 Aug 2026, 00:49 UTC56 views27 reactionsread 10 August 2026

вчера пришло осознание, что эта поездка действительно расставила точки над и. может, не все, но как минимум бóльшую их часть – за такой короткий срок и не стоит ожидать разгадки всех тайн вселенной и собственной жизни😶 не зря говорят, что любая поездка в азию трансформирует, потому что и эта исключением не стала осталось только выдумать, как вернуться в россию и смотреть на неё теми же глазами

custom 53170115091911365758custom 53304862732976409526custom 53212588667746676805custom 54449309253495970435custom 54204332651168658023

3 Aug 2026, 00:42 UTC55 views30 reactionsread 10 August 2026
Photo

дни в целом проходят настолько прекрасно, что хочется в этом мгновении задержаться надолго💚

custom 533048627329764095210custom 54316829698760677447custom 54449309253495970436custom 54204332651168658024custom 53212588667746676803

3 Aug 2026, 00:36 UTC55 views29 reactionsread 10 August 2026
Photo

`🐋.. ✨○ [ 🤩 ]❤️ ¡🌺; 🌟.. #난류 у нас уже целая традиция сложилась всегда ходить по океанариумам и островкам природы и животных, и сеул в список исключений не вошёл – lotte aquarium это просто нечто😭

custom 543168296987606774411custom 54449309253495970437custom 54204332651168658026custom 53212588667746676803custom 53304862732976409522

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

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

“난류 ✷ turbulence” (@wast_ray), 60 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/wast_ray.

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.