Telegram RegisterThe public register of Telegram

Channel

#Криптомысли

@cryptoroom

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

77subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001133220675
TypeChannel
Username@cryptoroom
DescriptionПо настроению трейдеров можно понять куда движется рынок, но это не точно. Самые интересные мысли о криптомире. 🇨 🇷 🇾 🇵 🇹 🇴 🇷 🇴 🇴 🇲
Created5 October 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/cryptoroom

Growth

776 August 2026 — 77 subscribers9 August 2026 — 77 subscribers6 August 20269 August 2026
2 measurements spanning 4 days. 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 76–78 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 20:1777no change
6 Aug 2026, 04:1077first reading

Engagement

20 posts held, back to 15 November 2018the 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 6 April 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
99
Videos
1
Links
83

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. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

6 Apr 2024, 09:47 UTC203 viewsread 9 August 2026

Любопытная скамуха, вывод работать давольно быстро https://t.me/bittonapp_bot?start=r7fnwmto

Signed Анна [HODL] Науменко 🦄

19 Jan 2022, 20:57 UTC437 viewsread 9 August 2026

Привет ) вы меня ещё читаете?

Signed Анна [HODL] Науменко 🦄

16 Feb 2019, 20:58 UTC848 viewsread 9 August 2026

#buybitcoin Реальная стоимость биткоина в рублях с учётом всех комиссий на биржах. https://truebtc.io/

Signed Unicorn🦄

9 Feb 2019, 09:10 UTC851 viewsread 9 August 2026
Photo

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

Signed Unicorn🦄

7 Feb 2019, 12:41 UTC552 viewsread 9 August 2026

​​Что-то затевается) неужели туземуен! https://www.vestifinance.ru/amp/articles/114199

Signed Unicorn🦄

20 Dec 2018, 03:09 UTC210 viewsread 9 August 2026
Forwarded from @F_S_C_P

Насколько выгодно будет держать ноду Эфира после Serenity? Расчеты, риски в статье от разработчика Эфира: https://spark.adobe.com/page/QxufRzl9E5uQu/

Signed Анна [HODL] Науменко 🦄

20 Dec 2018, 03:08 UTC153 viewsread 9 August 2026
Forwarded from @F_S_C_PPhoto

Photo, posted without a caption

Signed Анна [HODL] Науменко 🦄

20 Dec 2018, 03:08 UTC167 viewsread 9 August 2026
Forwarded from @F_S_C_PFile

File, posted without a caption

Signed Анна [HODL] Науменко 🦄

18 Dec 2018, 05:39 UTC126 viewsread 9 August 2026
Forwarded from @F_S_C_P

https://t.me/BitLenta/3042 если смотреть по количеству обработанных блокчейном транзакций то картина немного другая http://blocktivity.info/

Signed Анна [HODL] Науменко 🦄

17 Dec 2018, 18:01 UTC326 viewsread 9 August 2026
Photo

Photo, posted without a caption

Signed Анна [HODL] Науменко 🦄

6 Dec 2018, 17:14 UTC334 viewsread 9 August 2026

Анти Данилевский написал неплохой обзор того, что сейчас происходит на крипторынке и с ICO и куда этот паровоз движется... Читать тут

Signed Unicorn🦄

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

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

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.

“#Криптомысли” (@cryptoroom), 77 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/cryptoroom.

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.