Telegram RegisterThe public register of Telegram
Telegram profile photo for параллели всегда пересекаются

Channel

параллели всегда пересекаются

@AlwaysCrossing

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

10subscribers

+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-1002523453554
TypeChannel
Username@AlwaysCrossing
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live14 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 October 2026
On Telegramt.me/AlwaysCrossing

Growth

9109.57 August 2026 — 9 subscribers12 August 2026 — 9 subscribers14 October 2026 — 10 subscribers7 August 202614 October 2026
3 measurements spanning 68 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 9–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Oct 2026, 23:5610+1
12 Aug 2026, 12:039no change
7 Aug 2026, 15:209first reading

Engagement

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

Recent posts

6 Aug 2026, 13:51 UTC3 viewsread 12 August 2026
Forwarded from @andryuninthelegend

Пытки Год назад закончились для меня. Быть арестованным в 26 лет, помещенным в high security тюрьму в Лиссабоне с убийцами и нарко-бизнесменами ( и 2 раза получить отказ в залоге из-за того, что русский ). Судья сказала в день ареста: 45 лет тюрьмы ( трудности перевода, упустили слово !максимум! ). 2 недели с мыслью о смерти в средневековых условиях и без связи с внешним миром. Тюрьма в США после экстрадиции казалас…

3 Aug 2026, 22:03 UTC3 viewsread 12 August 2026

Перед тем как загнать в стойло надо продемонстрировать, что можно будет выйти

3 Aug 2026, 22:03 UTC3 viewsread 12 August 2026
Forwarded from @riskoff_posts

🎩 #Strategy #MSTR #Bitcoin Strategy sold 1,638 BTC at $63,957 on Aug 2, its third BTC sale in 34 days after moves on Jun 30 and Jul 5. The firm now holds 842,138 BTC (4% of supply) at a $75,419 average cost, $10.9B underwater, while its cash reserve grew from $871M to $4B over the same stretch.

1 Aug 2026, 15:35 UTCviews —

параллели всегда пересекаются pinned «https://t.me/eightyeightpertwentytwo»

31 Jul 2026, 22:13 UTC5 viewsread 12 August 2026
Forwarded from @riskoff_posts

📊 #AERO #UNI #DeFi Aerodrome processed $11.38B in volume on Base over the trailing 30 days versus Uniswap's $7.92B, but Uniswap captured $11.27M in fees against Aerodrome's $6.26M, per @0xchainink. Uniswap converts 14.2 bps per dollar routed compared to Aerodrome's 5.5 bps, while Aerodrome spent $1.25 per dollar of fees earned on emissions versus zero for Uniswap.

31 Jul 2026, 22:09 UTC5 viewsread 12 August 2026
Forwarded from @Nat_SelectionPhoto

Последнюю неделю сижу вообще без сделок - крипте просто нечего предложить. Биток падает 7 дней подряд, ликвидность тонкая, объемы на минимуме - летнее рыночное затишье в ожидании катализатора для роста Кстати заметил что в последние дни сразу несколько крупнейших управляющих компаний публично высказались в поддержку Clarity Act: -Franklin Templeton ($1,79 трлн под управлением) -Goldman Sachs в лице CEO Дэвида Солом…

31 Jul 2026, 21:02 UTC5 viewsread 12 August 2026
Forwarded from @dmitry_shukinPhoto

Photo, posted without a caption

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

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

“параллели всегда пересекаются” (@AlwaysCrossing), 10 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/AlwaysCrossing.

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.