Telegram RegisterThe public register of Telegram
Telegram profile photo for Freeze Инсайдит

Channel

Freeze Инсайдит

@FreezeSignals

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

365subscribers

-29 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-1002689112157
TypeChannel
Username@FreezeSignals
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/FreezeSignals

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

365394379.57 August 2026 — 394 subscribers8 August 2026 — 394 subscribers8 August 2026 — 393 subscribers15 August 2026 — 391 subscribers23 August 2026 — 387 subscribers30 August 2026 — 382 subscribers9 September 2026 — 376 subscribers17 September 2026 — 373 subscribers2 October 2026 — 368 subscribers13 October 2026 — 365 subscribers7 August 202613 October 2026
10 measurements spanning 67 days, net -29. 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 361–398 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 05:37365-3
2 Oct 2026, 21:20368-5
17 Sept 2026, 17:20373-3
9 Sept 2026, 04:37376-6
30 Aug 2026, 20:15382-5
23 Aug 2026, 11:39387-4
15 Aug 2026, 16:07391-2
8 Aug 2026, 11:37393-1
8 Aug 2026, 06:00394no change
7 Aug 2026, 15:45394first reading

Engagement

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

Reaction mix

147 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 40.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6040.8%
❤3423.1%
🔥2718.4%
😁96.12%
👏64.08%
🍾42.72%
💩32.04%
🤩32.04%
🤯10.68%

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 20 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 147 reactions 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 16 March 2026 to 9 April 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 Apr 2026, 13:05 UTC374 views4 reactionsread 8 August 2026

По $ARIA только смотрел спреды. по 0.4 появились кластерные движения. продажи шли небольшими объёмами, поэтому на лоях не заливался решение было коллективным и осознанным. ошибкой это назвать сложно, просто такой заход не для всех. справедливая ушла вниз значительно. возможность была, но не для всех, требовалась быстрая реакция и готовность к адлу. у многих сегодня минус по Bybit, у меня результат средний. не лучший…

🔥2🤯1😁1

8 Apr 2026, 09:43 UTC433 views12 reactionsread 8 August 2026

$DRIFT открыл депозит, и можно было очень хорошо залиться. я лично спал в это время, заколоть было нереально. с профитом, кто отработал

👍6❤3🤩3

7 Apr 2026, 16:00 UTC421 views7 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🍾4😁3

7 Apr 2026, 15:34 UTC357 views8 reactionsread 8 August 2026
Photo

ставка на полимаркете на 3-ю мировую?

❤3🔥3👍2

22 Mar 2026, 10:23 UTC489 views7 reactionsread 8 August 2026

короче, ребят, беру паузу на некоторое время вернусь отдохнувший и с холодной головой не теряйте главное

❤7

21 Mar 2026, 12:13 UTC596 views1 reactionsread 8 August 2026
Photo

напоминание для тех кто забыл, что через 2 дня $BP TGE Все свои мысли по нему писал в постах выше.👆👆 кто не видел, ознакомьтесь

❤1

21 Mar 2026, 09:27 UTC526 views7 reactionsread 8 August 2026

Сейчас рассказали интересную тенденцию. Корейские биржи и вообще Tier-1 площадки, которые на анонсах любят рисовать вкусные свечи, снова начали подавать признаки жизни. ДАВНО такого не было. Начал потихоньку пробовать заходить в позиции под анонс корейцев. Что уже было: · $ROBO после анонса: классический рост и потом укатка. · $PHA точно такая же история Мои мысли по стратегии: Вообще, шортить палки от бирж сейч…

👍5🔥2

18 Mar 2026, 15:49 UTC512 views23 reactionsread 8 August 2026

РЕБЯТ, НУЖНА ОБРАТНАЯ СВЯЗЬ В последнее время много пишу сюда про разные темы, разборы ситуаций, примеры сделок, просто мысли по рынку Я тут подумываю сделать гайд в виде статьи. Чтобы человек после прочтения реально мог взять и применить Но тематику пока не выбрал Черканите в коменты, что хотели бы увидеть и накидайте реакции если заходит такая тема

👍14👏4🔥4❤1

18 Mar 2026, 14:49 UTC499 views10 reactionsread 8 August 2026

$BARD начинаю немного выходить, под 0.5-1% всех с профитам

❤4👍3🔥3

18 Mar 2026, 13:38 UTC492 views11 reactionsread 8 August 2026

бинанс $BARD лонг aster шорт 7 процентов спред

👍5❤3🔥3

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

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

“Freeze Инсайдит” (@FreezeSignals), 365 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/FreezeSignals.

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.