Telegram RegisterThe public register of Telegram
Telegram profile photo for Артур Соколов | КриптоБлог

Channel

Артур Соколов | КриптоБлог

@ArturSokolovKriptoblog

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Cite this entry

3,166subscribers

-16 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001215116967
TypeChannel
Username@ArturSokolovKriptoblog
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 November 2026
Measurements held18
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/ArturSokolovKriptoblog

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ArturSokolovKriptoblog/37566 · this entry4 Aug 2026, 16:38 UTC@cryptoliquidationss/48884 Aug 2026, 16:38 UTC1.00under a minute
@cryptoliquidationss/48915 Aug 2026, 14:11 UTC@ArturSokolovKriptoblog/37569 · this entry5 Aug 2026, 14:11 UTC1.00under a minute
@cryptoliquidationss/48925 Aug 2026, 14:11 UTC@ArturSokolovKriptoblog/37570 · this entry5 Aug 2026, 14:11 UTC1.00under a minute
@cryptoliquidationss/48966 Aug 2026, 08:54 UTC@ArturSokolovKriptoblog/37574 · this entry6 Aug 2026, 08:54 UTC1.00under a minute
@ArturSokolovKriptoblog/37575 · this entry6 Aug 2026, 12:56 UTC@cryptoliquidationss/48976 Aug 2026, 12:56 UTC1.00under a minute
@ArturSokolovKriptoblog/37576 · this entry6 Aug 2026, 19:47 UTC@cryptoliquidationss/48986 Aug 2026, 19:47 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@cryptoliquidationss9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 2 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @ArturSokolovKriptoblog — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3,1663,1823,1747 August 2026 — 3,182 subscribers7 August 2026 — 3,182 subscribers10 August 2026 — 3,181 subscribers26 August 2026 — 3,180 subscribers2 September 2026 — 3,181 subscribers6 September 2026 — 3,182 subscribers11 September 2026 — 3,180 subscribers14 September 2026 — 3,181 subscribers19 September 2026 — 3,180 subscribers29 September 2026 — 3,175 subscribers6 October 2026 — 3,174 subscribers13 October 2026 — 3,176 subscribers16 October 2026 — 3,173 subscribers19 October 2026 — 3,172 subscribers22 October 2026 — 3,171 subscribers25 October 2026 — 3,169 subscribers6 November 2026 — 3,168 subscribers19 November 2026 — 3,166 subscribers7 August 202619 November 2026
18 measurements spanning 105 days, net -16. 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 3,164–3,184 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Nov 2026, 22:573,166-2
6 Nov 2026, 06:493,168-1
25 Oct 2026, 12:303,169-2
22 Oct 2026, 19:173,171-1
19 Oct 2026, 12:473,172-1
16 Oct 2026, 04:183,173-3
13 Oct 2026, 02:443,176+2
6 Oct 2026, 15:593,174-1
29 Sept 2026, 23:353,175-5
19 Sept 2026, 07:363,180-1
14 Sept 2026, 19:163,181+1
11 Sept 2026, 00:193,180-2
6 Sept 2026, 09:183,182+1
2 Sept 2026, 05:243,181+1
26 Aug 2026, 15:423,180-1
10 Aug 2026, 09:203,181-1
7 Aug 2026, 09:013,182no change
7 Aug 2026, 08:493,182first reading

Engagement

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

Recent posts

7 Aug 2026, 15:39 UTC2 viewsread 7 August 2026
Photo

#BTCUSDT ВТС снял вторую цель, про которую я говорил ещё в начале недели, таким образом собрали ликвидность и идём в консолидацию на выходные Конечно это не та волатильность которую я хотел увидеть, но учитываем фактор рынка, так как идёт накопление ликвидности При достижении второй цели, можно фиксировать ещё часть позиции и держать токен дальше

7 Aug 2026, 10:20 UTC4 viewsread 7 August 2026

Пока цена удерживается выше 64.000, приоритет остается за продолжением восходящего движения

7 Aug 2026, 10:20 UTC4 viewsread 7 August 2026
Photo

#BTCUSDT BTC продолжает торговаться в зоне 64.000 - 64.600, где крупный капитал удерживает цену после импульсного роста Ближайшая ликвидность находится в диапазоне 65.000 Закрепление выше этой зоны откроет путь к 65.400

6 Aug 2026, 19:47 UTC2 viewsread 7 August 2026
Photo

Индекс страха и жадности остаётся на отметке 26, а значит рынок всё ещё находится в режиме ожидания Ни страха, ни жадности пока не хватает для сильного движения

6 Aug 2026, 12:56 UTC3 viewsread 7 August 2026
Photo

#ATOMUSDT Сейчас ключевая зона находится на 1.40 Закрепление выше этого уровня откроет путь к 1.50, где находится следующая крупная ликвидность Поддержкой остается 1.20 Пока цена торгуется ниже 1.40, структура остается коррекционной, а текущий рост выглядит как восстановление после снятия ликвидности

6 Aug 2026, 08:54 UTC3 viewsread 7 August 2026
Photo

#BTCUSDT 🥇ВТС, как и ожидалось, после теста зоны ОВ начал показывать рост ‼️Ранее уже пробили 1-ю цель - 64.500, далее я хочу видеть закреп и поход на 66.500. 📉Самое интересное, что мы не снимаем сквизы и стопы, а кит делает это плавно и не спеша, то есть таким образом собирают стопы и для выноса лонгистов

5 Aug 2026, 14:58 UTC3 viewsread 7 August 2026

Готовлю для вас обзор на #SOLUSST - хочу взять токен на среднесрок, поэтому ожидайте 👌

5 Aug 2026, 14:11 UTC3 viewsread 7 August 2026

Пока цена находится выше 63.600, приоритет остается за продолжением роста

5 Aug 2026, 14:11 UTC3 viewsread 7 August 2026

Сейчас ключевым сопротивлением выступает диапазон 64.400 - 64.700 Закрепление выше этой зоны откроет путь к 65.400, затем к 66.400

5 Aug 2026, 14:11 UTC3 viewsread 7 August 2026
Photo

#BTCUSDT BTC продолжает удерживаться выше зоны 63.600 - 64.000, что говорит о сохранении контроля со стороны покупателей

Showing the 12 most recent of 24 posts we hold for @ArturSokolovKriptoblog. 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 19 November 2026 — this entry's latest reading, not the date you are reading this.

“Артур Соколов | КриптоБлог” (@ArturSokolovKriptoblog), 3,166 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/ArturSokolovKriptoblog.

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.