Telegram RegisterThe public register of Telegram
Telegram profile photo for Lazarchuk_ru- Лазарчук🛸

Channel

Lazarchuk_ru- Лазарчук🛸

@lazarchuck

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

142subscribers

-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-1001491284716
TypeChannel
Username@lazarchuck
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 November 2026
Measurements held4
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/lazarchuck

Topic

Literature — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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
@urus_hay/9477 Aug 2026, 03:47 UTC@lazarchuck/2749 · this entry7 Aug 2026, 04:15 UTC0.9928 minutes
@urus_hay/94326 Jul 2026, 14:05 UTC@lazarchuck/2745 · this entry26 Jul 2026, 14:19 UTC0.9914 minutes
@urus_hay/9467 Aug 2026, 01:38 UTC@lazarchuck/2748 · this entry7 Aug 2026, 01:44 UTC0.986 minutes
@urus_hay/9389 Jul 2026, 11:55 UTC@lazarchuck/2738 · this entry9 Jul 2026, 12:17 UTC0.9822 minutes
@urus_hay/93529 Jun 2026, 14:56 UTC@lazarchuck/2737 · this entry29 Jun 2026, 15:21 UTC0.9625 minutes
@urus_hay/94429 Jul 2026, 17:55 UTC@lazarchuck/2746 · this entry29 Jul 2026, 18:24 UTC0.9429 minutes
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
@urus_hay6 (6/6 hand-verifiable sample passed)0.9724 minutes@urus_hay (6–0)

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 6 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 10 comparable posts for this entry, running 12 May 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 @urus_hay. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

1421441437 August 2026 — 144 subscribers8 August 2026 — 144 subscribers8 September 2026 — 143 subscribers8 November 2026 — 142 subscribers7 August 20268 November 2026
4 measurements spanning 93 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 142–144 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 15:14142-1
8 Sept 2026, 23:37143-1
8 Aug 2026, 21:17144no change
7 Aug 2026, 16:19144first reading

Engagement

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

Reaction mix

41 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 53.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2253.7%
🔥1024.4%
❤512.2%
😱24.88%
👏12.44%
😁12.44%

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

Measured over the 17 most recent posts we hold, published 9 May 2026 to 7 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

7 Aug 2026, 04:15 UTC36 views4 reactionsread 8 August 2026

✏️ Андрей Лазарчук: Давайте, други милые, буянить и шалить. Над каждою могилою не будем слезы лить. Беду-судьбу лохматую устанем проклинать И жизнь свою сломатую не станем поминать. Мильонов мы не нажили, до звезд не добрались. Но взяли и отважились, сошлись и собрались. А значит продолжаются веселые года, И где-то разгорается далекая звезда, Закутана, замотана туманами потерь... Когда еще взойдет она! Но ты, товари…

❤2👍2

7 Aug 2026, 01:44 UTC45 views5 reactionsread 8 August 2026

✏️ Андрей Лазарчук: - ...Но ничего не сказал франкистам отважный республиканский лётчик, только повторял своё имя - Хулио Тибенада... Это реальный анекдот из конца 30-х, дед рассказал. Тогда в их лагерь законопатили несколько "испанцев", от них он и слышал. Сцуко. Дед, в отличие от многих молчаливых ветеранов, довольно много рассказывал и про дореволюционную жизнь, и про гражданскую, и про лагеря, и про Отечественную…

👍5

29 Jul 2026, 18:24 UTC116 viewsread 8 August 2026

✏️ Андрей Лазарчук: в аду для перфекционистов ни серы нету ни огня и лишь слегка несимметрично стоят щербатые котлы в раю для перфекцонистов в достатке сера и смола блестят котлы из нержавейки и пламя ровное гудит

26 Jul 2026, 14:19 UTC139 views3 reactionsread 8 August 2026

✏️ Андрей Лазарчук: О граммар-наци и плохом знании матчасти: Напишет кто-нибудь "попал как кур во щи", и тут же набегают знающие люди с повязками и наганами: "Правильно писать "в ощип"!" "Почему правильно?" - "А из кур щей не варят!" Вообще-то варят. Но в этом случае разговор уходит в область кулинарии, где спорщики явно не сильны. Теперь смотрим. В классике встречаются три варианта: Во щи В ощип Во щип (щип - это т…

❤1🔥1😁1

20 Jul 2026, 18:15 UTC134 viewsread 8 August 2026
Photo

✏️ Андрей Лазарчук: Попытайтесь угадать, что на этом фото. Кто уже знает, тот молчит

20 Jul 2026, 16:18 UTC122 views4 reactionsread 8 August 2026
Photo

✏️ Андрей Лазарчук: 90 лет

👍2🔥2

15 Jul 2026, 11:10 UTC159 views2 reactionsread 8 August 2026

✏️ Андрей Лазарчук: #Интернет_магазин_Окей, вы бессовестные твари. Заказ не доставлен, трубку на горячей линии не берут, по почте ответили весьма издевательски и замолчали. Наихудшая обратная связь из всех магазинов, с которыми мне приходилось иметь дело

😱2

9 Jul 2026, 12:17 UTC165 views4 reactionsread 8 August 2026

✏️ Андрей Лазарчук: Журналист: - Вы будете готовы вводить бесполётную зону? Трамп: - Ээ... если надо, то да, но смотрите, я имею в виду, смотрите, я вам говорю, когда у нас будет сделка, мы будем иметь сделку, будут гарантии безопасности и или не будет гарантий безопасности. Я думаю, если мы придём к решению, а я думаю что да, то мы получим сделку, сейчас мы хотим увериться в сделке. Некоторые не думают, что она реал…

👍4

29 Jun 2026, 15:21 UTC170 viewsread 8 August 2026

✏️ Андрей Лазарчук: Один наш доктор пытался ввести забавный обычай Родился у него первый ребёнок - помер Андропов. Родился второй - помер Черненко. Все говорили: ну теперь если что, раскрутим НН на третьего. Однако второй ребёнок рос болезненным, требовал много внимания, и на третьего НН не решился. Вот так и распался Советский Союз

20 Jun 2026, 14:30 UTC208 viewsread 8 August 2026

✏️ Андрей Лазарчук: А посоветуйте что почитать такого лёгкого, ненапряжного?

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“Lazarchuk_ru- Лазарчук🛸” (@lazarchuck), 142 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/lazarchuck.

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.