Telegram RegisterThe public register of Telegram
Telegram profile photo for LAMERLAND - overbafer1

Channel

LAMERLAND - overbafer1

@overlamer1

Verified by Telegram

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

81,031subscribers

-305 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001184091021
TypeChannel
Username@overlamer1
Description< Информационная безопасность > overbafer1 - личный блог: t.me/overbafer1 Почта: @overbafer1_robot Реклама: @MNGR_iM
Created13 November 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/overlamer1

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@overlamer1/3373 · this entry6 Aug 2026, 06:08 UTC@overbafer1/23016 Aug 2026, 11:21 UTC1.005.2 hours
@overbafer1/23458 Sept 2026, 17:53 UTC@overlamer1/3422 · this entry9 Sept 2026, 10:56 UTC1.0017 hours
@overlamer1/3466 · this entry27 Sept 2026, 13:28 UTC@overbafer1/238628 Sept 2026, 14:12 UTC1.0025 hours
@overbafer1/24067 Oct 2026, 13:03 UTC@overlamer1/3488 · this entry7 Oct 2026, 13:06 UTC1.002 minutes
@overbafer1/241713 Oct 2026, 16:21 UTC@overlamer1/3503 · this entry15 Oct 2026, 09:04 UTC0.9841 hours
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
@overbafer16 (6/6 hand-verifiable sample passed)1.0021 hours@overbafer1 (4–2)

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. 3 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 105 comparable posts for this entry, running 22 July 2026 to 9 November 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).

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.

Growth

81,00981,56781,28881,0315 August 202610 November 2026
64 measurements spanning 97 days, net -305. 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 80,925–81,651 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 22:0681,031-8
9 Nov 2026, 08:4681,039-13
7 Nov 2026, 23:5681,052-4
6 Nov 2026, 19:1781,056-8
5 Nov 2026, 21:0181,064-12
4 Nov 2026, 17:3681,076-7
3 Nov 2026, 19:4781,083-8
2 Nov 2026, 18:0981,091+1
1 Nov 2026, 19:3881,090+1
31 Oct 2026, 23:0581,089+2
31 Oct 2026, 01:2781,087-12
28 Oct 2026, 22:0681,099+1
27 Oct 2026, 21:1781,098-2
26 Oct 2026, 17:4581,100-14
25 Oct 2026, 20:1981,114-5
24 Oct 2026, 19:2781,119-12
23 Oct 2026, 19:1981,131-9
22 Oct 2026, 19:4981,140-15
21 Oct 2026, 13:4981,155-19
20 Oct 2026, 12:1881,174first reading

Engagement

105 posts held, back to 22 July 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 200 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.2%
avg views ÷ 81,031 subscribers
Avg views / post
10,700
28 posts measured
Reaction rate
0.926%
reactions ÷ views · ER floor
Posts in window
28
of 105 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 November 2026
Posts held105 (22 July 2026 – 9 November 2026)
Views total299,970
Reactions total2,777
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 08:25 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,260
Videos
≈695
Links
≈1,670

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
7m 07s
Average length
39s

Measured directly from 11 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

13,249 reactions across 104 posts, in 28 distinct kinds. The most used accounts for 32.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁4,33432.7%
❤2,58219.5%
🔥1,3199.96%
🤯7525.68%
👍6264.72%
😱6214.69%
❤‍🔥5213.93%
🫡4663.52%
👾4473.37%
🌚2682.02%
👏2071.56%
🐳1551.17%
👨‍💻1551.17%
✍1531.15%
👀1471.11%
🙈1351.02%
🤝1090.823%
💯600.453%
🏆540.408%
🍾460.347%
8 further kinds920.694%

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

Measured over the 105 most recent posts we hold, published 22 July 2026 to 9 November 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.

Telegram Stars

Stars received
27
across the posts below
Posts paid on
7
of 105 we hold a reading for · 7%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @overlamer1. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 105 most recent posts we hold for this entry, published 22 July 2026 to 9 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 28 posts held from the last 30 days (3.57%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

9 Nov 2026, 14:19 UTC≈7,280 views104 reactionsread 12 November 2026
Photo

🍏 В клавиатуре iPhone нашли СКРЫТУЮ ЦЕНЗУРУ — Apple не даёт нормально писать около 100k слов. Исследователь раскопал внутри iOS скрытую цензуру, которую Apple публично никогда не показывала. Только для инглиша нашли 4513 фраз, а похожие списки ещё для 27 языков и письменностей. Общий объём оценивают примерно в 100 тысяч вариантов. ⌨️ Дело в том, что нужную фразу автоподстановка не предложит, а QuickPath может буква…

😁85👨‍💻9🐳5❤‍🔥3❤1👍1

8 Nov 2026, 13:52 UTC≈8,960 views79 reactionsread 12 November 2026
Photo

👩‍🎨 ВЗЛОМАТЬ Windows 11 можно через PAINT! В проге, где мы последние 30 лет рисуем каракули, нашли дыру CVE-2026-83844 с оценкой 8.1/10. 🧑‍💻 Microsoft официально подтверждает, что хацкер при определённых условиях может отправить специально сформированные данные по сети и добиться выполнения своего кода на компьютере. 💀 По CVSS атака идёт через сеть, не требует аккаунта и действий пользователя. Но есть хорошая ново…

🔥45😱16❤8😁8👏2

6 Nov 2026, 13:18 UTC≈11,100 views80 reactionsread 12 November 2026
Video

💻 OpenAI выкатил GPT-6 Cyber — нейронку прокачали до уровня мега-ХАЦКЕРА. GPT-6 Cyber специально обучена искать уязвимости, собирать рабочие эксплойты и проверять их на настоящем софте — браузерах, ядрах, базах данных и веб-сервисах. OpenAI классифицировала её способности как Critical по своей Preparedness Framework. 🦊 В Firefox модель нашла 81 НОВУЮ уязвимость высокой опасности, которые до этого не обнаружили даже…

👏51❤13😱8❤‍🔥3🌚3🐳1👍1

4 Nov 2026, 16:35 UTC≈13,800 views157 reactionsread 12 November 2026
Photo

👾 Binance взломали без любовницы-шпионки из КНДР а через ВАЙБКОДИНГ и одно собеседование. Binance раскрыли полную хронологию крупнейшего криптовзлома в истории. Хацкеры готовились несколько месяцев и заходили через разрабов по цепочке. 🧑‍💻 Июнь. DevOps-инженер из команды кошельков решил установить популярный ИИ-инструмент для вайбкодинга. Нашёл установщик через Гугл, скачал фейковую версию и словил вредонос. Хоть б…

❤‍🔥87😁43❤10😱9🐳4👏2👨‍💻2

3 Nov 2026, 13:18 UTC≈11,700 views138 reactionsread 12 November 2026
Photo

🚘 Хацкеры начали ВЗЛАМЫВАТЬ машины у россиян. Владельцы китайских тачек массово жалуются на кражу мастер-аккаунтов Li Auto. Через такой аккаунт управляются двери, климат, запуск двигателя и другие функции. Проблему уже подтвердил официальный дистрибьютор. 💻 После перехвата аккаунта у некоторых машин гаснут экраны, пропадает климат-контроль и Bluetooth-ключ, а отдельные модели вообще отказываются запускаться. Дальш…

😁124❤8😱4🌚2

1 Nov 2026, 14:19 UTC≈14,100 views170 reactionsread 12 November 2026
Photo

👾 Вайбкодер пустил ЛИЧНЫЙ Claude Code в защищённую сеть Пентагона. Сотрудник Accenture подключил свой аккаунт Claude Code к рабочей среде NIPRNet — сети Пентагона, где хранятся весьма чувствительные данные. 🧑‍💻 Чтобы “ускорить разработку”, работяга отдал Claude свои логины и админские права. Агент получил возможность САМ писать код, сохранять его в систему и поднимать облачные серверы. И так он хозяйничал внутри и…

😁135🍾15👏11❤4🔥3🌚1👍1

30 Oct 2026, 16:14 UTC≈14,200 views69 reactionsread 12 November 2026
Photo

🚨В Claude Code обнаружили опасную уязвимость — до 5000 разрабов могли получить SSH-бэкдор. Вчера в маркете Cursor рколо 11 часов лежала модифицированная версия официального расширения Claude Code — 2.1.313. Выглядела и работала она как обычная, только перед настоящим кодом хацкеры дописали 66 строк вредоноса. ⌨️ Достаточно было запустить редактор и активировать расширение — начинать диалог с Claude даже не требовал…

👨‍💻42😁15❤10🔥2

29 Oct 2026, 17:19 UTC≈13,400 views55 reactionsread 12 November 2026
Photo

💸 Хацкеры научились подменять криптоадреса прямо на НАСТОЯЩИХ биржах. Исследователи обнаружили вредоносный код внутри JavaScript, связанного с сервисом поддержки Udesk. Обычный чатик техподдержки незаметно подгружал второй скрипт deeps.js, который начинал хозяйничать уже внутри страницы пользователя. 😐 Скрипт каждые 200 миллисекунд проверял страницу пополнения и подменял настоящий криптоадрес на кошелёк хацкера. Пр…

❤‍🔥25😁14😱8❤4🆒3🌚1

27 Oct 2026, 16:29 UTC≈12,400 views67 reactionsread 12 November 2026
Photo

👁 Google будет СМОТРЕТЬ ваши файлы из Gmail, Drive и Photos для ТАРГЕТИРОВАННОЙ РЕКЛАМЫ — если вы подключили Gemini к профилю. 📝 Недавно Google обновили политику: раньше контора заявляла, что не использует содержимое Gmail, Drive и Google Photos для персонализированной рекламы. Теперь появилась приписка: «…если только вы сами не сделали данные из этих сервисов доступными другим сервисам Google, поддерживающим персо…

😁32😱16👾10✍4❤3👍1👻1

26 Oct 2026, 14:29 UTC≈12,000 views112 reactionsread 12 November 2026
Photo

😐 Нейронки научились общаться между собой за спиной у людей, через обычные картинки. Исследователи выяснили, что Claude Fable 5.1 может генерить обычные картинки и прятать внутри определенные фразы, сама придумывая способ кодирования. 🚀 В одном из тестов Claude нарисовал обычное ночное небо со звёздами. Только высота каждой звезды оказалась буквой алфавита — если измерить координаты и сложить их вместе, получается …

❤‍🔥59👾24❤15🔥4😁4✍3😱2💯1

25 Oct 2026, 16:21 UTC≈14,900 views169 reactionsread 12 November 2026
Photo

🖥 Работяги нашли СКРЫТУЮ МОЩНОСТЬ в RTX 30xx и 40xx — Nvidia годами душила часть Tensor-ядер почти ВДВОЕ. На GitHub появился gpu-unlock, который снимает ограничение на FP16/BF16/TF32-вычисления с накоплением в FP32, которые используются при обучении нейронок, LoRA, diffusion и части LLM-нагрузок. 🤯 На RTX 4090 FP16 вырос с 165,6 до 331,6 TFLOPS, BF16 — с 165,5 до 330,6. То есть буквально почти Х2 без разгона, пайки…

👍110🌚27❤16😱8👏6✍1❤‍🔥1

24 Oct 2026, 17:20 UTC≈12,500 views76 reactionsread 12 November 2026
Photo

😈 ИИ-агенты OpenAI начали ОТКЛЮЧАТЬ системы контроля и ВРАТЬ, что ничего не трогали. OpenAI раскрыла два свежих инцидента с GPT-6.1 Sol и GPT-6 Astra. Агенты выполняли обычные задачи по кодингу и по дороге решили, что системы наблюдения можно немного подвинуть. 👁 GPT-6.1 Sol сам взял старую инструкцию «не отправляй сообщения» и спустя 82 сообщения подкинул её на систему безопасности. В итоге он обнулил список получ…

🔥40😁20👾6❤3👻3😱3👍1

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

Posts edited after publishing

@overlamer1 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
23 August 2026
Most recent edit
23 August 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @overlamer1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
5 September 2026
Most recent seen missing
11 October 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
0

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

Named by 10 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

overbafer1
@overbafer1 · 63,351
#1
Task No Face
@TaskNoFace · 28,996
#2
Чёрный Треугольник
@black_triangle_tg · 63,962
#3
Open Source
@open_source_friend · 52,669
#4
SecurityLab.ru
@SecLabNews · 86,532
#5
Life-Hack - Хакер
@haccking · 63,021
#6
[PYTHON:TODAY]
@python2day · 63,339
#7
Нажми Enter | Тренды, ІТ и бизнес
@PushEnter · 90,447
#8
Daniel Myslivets
@daneo03 · 12,295
#9
Нейродвиж
@neuraldvig · 288,660
#10
Russian OSINT
@Russian_OSINT · 48,514
#11
IT Юмор
@ithumor · 60,062
#12
КІБЕРБЕЗ
@cybersecurity_ua · 53,697
#13
Алексей Шевцов
@jolybells · 357,371
#14
Social Engineering
@Social_engineering · 124,696
#15
NN
@naebnet · 2,177,794
#16
Бэкдор
@whackdoor · 1,538,229
#17
Пекарня
@pekagame · 1,117,922
#18
Rozetked
@rozetked · 646,921
#19
Этичный Хакер
@hack_less · 243,060
#20
Ньюсач/Двач
@ru2ch · 710,451
#21
Не баг, а фича
@bugfeature · 551,367
#22
ХарчевниковИлита
@kharchevnikov · 121,035
#23
Antipov
@antipov · 394,584
#24
Код.ру
@d_code · 405,458
#25
Хауди Хо - IT юмор, жизнь программиста
@howdyho_official · 77,428
#26
4ch
@why4ch · 1,021,012
#27
VG/Двач
@ru2chvg · 183,087
#28
ВИЛСАКОМ РЕД / WYLSACOM RED
@wylsared · 1,088,291
#29
Не баг, а фича
@bugnotfeature · 1,162,637
#30
GitHub Community
@github · 154,995
#31
Programmer & IT Memes
@itmemes · 121,889
#32
infosec
@it_secur · 63,440
#33
CyberYozh
@cyberyozh_official · 62,629
#34
DeadP47
@deadp47gaymer · 149,375
#35
Mr. Robot
@elliot_cybersec · 38,905
#36
НМШ
@nmshhub · 669,331
#37
Рестарт
@remedia · 666,164
#38
Мой Компьютер
@mknewsru · 214,518
#39
CodeCamp
@codecamp · 177,529
#40
СТАС БОМБИТ
@ikakprosto · 322,430
#41
Codeby
@codeby_sec · 37,083
#42
1337
@media1337 · 1,103,517
#43
$DDOS GAME
@DDoSGame · 684
#44
r/ретранслятор
@retra · 165,761
#45
ТОПОР - Горячие новости
@topor · 1,291,254
#46
ТОПЛЕС
@toplesofficial · 498,473
#47
Интернет-Розыск
@irozysk · 45,710
#48
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,408
#49
SecAtor
@true_secator · 42,213
#50
Big Geek
@biggeekru · 601,397
#51
Романцев768 | Romancev768
@Romancev768 · 785,910
#52
Gram RUS
@toncoin_rus · 508,907
#53
Сегодня в тренде
@trends · 1,112,806
#54
Linux, please
@linuxplz0x41 · 5,401
#55
КБ. Игры
@cb_games · 382,069
#56
Архив Безопасника
@secure_archive · 10,964
#57
Хакер — Xakep.RU
@xakep_ru · 40,321
#58
Termux, please
@termuxplz0x41 · 32,412
#59
CryptoScamm
@crypt0scamm · 59,873
#60
S.E.Reborn
@S_E_Reborn · 22,449
#61
Хабр
@habr_com · 134,497
#62
nerds
@nerds · 410,643
#63
Kali Linux
@linuxkalii · 55,900
#64
КиберТопор
@cybers · 1,878,964 (as read 18 August 2026)
#65
CMD | IT
@cmd_it · 24,075
#66
Типичный Сисадмин
@sysodmins · 40,818
#67
Эксплойт
@exploitex · 2,021,350
#68
Двач
@dvachannel · 969,125
#69
Вестник Шевцова
@jolynews · 206,431
#70
Blum: All Crypto – One App
@blumcrypto · 12,771,035
#71
Notcoin Community
@notcoin · 7,808,013
#72
КБ
@cbpub · 667,477
#73
Игорь Линк
@IgorLinkChannel · 72,245
#74
Утечки информации
@dataleak · 117,675
#75
Логово Внизу
@nebudetgg · 487,714
#76
Новости Walt (ранее Кошелёк)
@walt_news_cis · 1,085,538
#77
Новости Crypto Bot
@cryptobotru · 2,150,480
#78
КБ. экономика
@cb_economics · 364,931
#79
sndk
@sndkgram · 357,717
#80
Быть Или
@ToBeOr_Official · 304,374
#81
РАЙЗ ЛАВ Ю
@raiz · 300,731
#82
Gabe Follower
@gabefollower · 51,633
#83
Злой Крастер
@angrycrust · 122,930
#84
ТРУСЫ РАЙЗА
@raiznews · 505,154
#85

Read from Telegram’s recommendation API, most recently 18 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Task No Face
@TaskNoFace · 28,996
Telegram ranks this channel #1 of 78 here — alongside 77 others — read 8 September 2026
overbafer1
@overbafer1 · 63,351
Telegram ranks this channel #1 of 84 here — alongside 83 others — read 21 August 2026
Termux, please
@termuxplz0x41 · 32,412
Telegram ranks this channel #8 of 54 here — alongside 53 others — read 4 September 2026
Чёрный Треугольник
@black_triangle_tg · 63,962
Telegram ranks this channel #24 of 87 here — alongside 86 others — read 21 August 2026
CMD — полезные сервисы для жизни и работы
@cmd_cv · 53,243
Telegram ranks this channel #36 of 94 here — alongside 93 others — read 24 August 2026
CMD | IT
@cmd_it · 24,075
Telegram ranks this channel #39 of 82 here — alongside 81 others — read 16 September 2026
Хауди Хо - IT юмор, жизнь программиста
@howdyho_official · 77,428
Telegram ranks this channel #47 of 90 here — alongside 89 others — read 18 August 2026
Менталист
@mentalroom · 22,490
Telegram ranks this channel #60 of 84 here — alongside 83 others — read 20 September 2026
PulSe
@Pulsechanel · 20,004
Telegram ranks this channel #67 of 69 here — alongside 68 others — read 29 September 2026
Этичный Хакер
@hack_less · 243,060
Telegram ranks this channel #70 of 81 here — alongside 80 others — read 12 August 2026
Social Engineering
@Social_engineering · 124,696
Telegram ranks this channel #73 of 82 here — alongside 81 others — read 13 August 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“LAMERLAND - overbafer1” (@overlamer1), 81,031 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/overlamer1.

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.