Telegram RegisterThe public register of Telegram

Channel

RamCode

@ramcode

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Stars · Posts · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

80,946subscribers

-269 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001304521977
TypeChannel
Username@ramcode
DescriptionЛичный блог Ram'a На связи в @grozny
Created27 December 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/ramcode

Topic

Personal blog — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 40% 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 why it has no browse page of its own yet.

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 word for word 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ramcode/207 · this entry22 Nov 2025, 11:54 UTC@tmbots/51122 Nov 2025, 11:54 UTC1.00under a minute
@ramcode/209 · this entry3 Dec 2025, 18:21 UTC@tmbots/5123 Dec 2025, 18:21 UTC1.00under a minute
@ramcode/215 · this entry4 Feb 2026, 19:55 UTC@tmbots/5164 Feb 2026, 20:02 UTC1.007 minutes
@ramcode/217 · this entry12 Feb 2026, 16:21 UTC@tmbots/51712 Feb 2026, 16:21 UTC1.00under a minute
@ramcode/218 · this entry22 Feb 2026, 18:30 UTC@tmbots/51922 Feb 2026, 18:30 UTC1.00under a minute
@ramcode/219 · this entry1 Mar 2026, 20:00 UTC@tmbots/5211 Mar 2026, 20:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tmbots9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (90)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 22 November 2025 to 27 July 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).

Across the whole group of 2, the earliest publisher we hold is @ramcode — 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 6 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

80,94681,21581,080.56 August 2026 — 81,215 subscribers6 August 2026 — 81,215 subscribers6 August 2026 — 81,201 subscribers7 August 2026 — 81,167 subscribers8 August 2026 — 81,123 subscribers9 August 2026 — 81,091 subscribers10 August 2026 — 81,031 subscribers11 August 2026 — 80,990 subscribers12 August 2026 — 80,946 subscribers6 August 202612 August 2026
9 measurements spanning 6 days, net -269. 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,906–81,255 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:5380,946-44
11 Aug 2026, 05:3180,990-41
10 Aug 2026, 03:5181,031-60
9 Aug 2026, 05:2181,091-32
8 Aug 2026, 07:1381,123-44
7 Aug 2026, 09:4681,167-34
6 Aug 2026, 11:1081,201-14
6 Aug 2026, 01:3481,215no change
6 Aug 2026, 00:5281,215first reading

Engagement

20 posts held, back to 22 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.3%
avg views ÷ 80,946 subscribers
Avg views / post
8,320
1 post measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 27 July 2026
Posts held20 (22 November 202527 July 2026)
Views total8,320
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 18:50 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
83
Videos
5
Links
84

Lifetime counters from Telegram’s own channel header, read 12 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.

Telegram Stars

Stars received
72,993
across the posts below
Posts paid on
20
of 20 we hold a reading for · 100%
Most on one post
58,200
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ramcode. 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 20 most recent posts we hold for this entry, published 22 November 2025 to 27 July 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

27 Jul 2026, 17:20 UTC≈8,320 views0 reactions145 Starsread 12 August 2026

💳 Оплата зарубежных сервисов в последнее время — лотерея Виртуальные карты отклоняются одна за другой: то платёж не проходит без внятной причины, то сервис просто не принимает такую карту. 👍 Тот, на котором я в итоге остановился — Zarub. Ни разу не подвёл. Буквально вчера оплачивал через него Claude — прошло моментально. Что там есть: → Виртуальные зарубежные карты для Claude, ChatGPT, Spotify и остальных сервисо

28 Jun 2026, 19:42 UTC≈33,700 views0 reactions182 Starsread 12 August 2026
Photo

У Proxy Coffee появился свой VPN 🔑 К привычным прокси добавили полноценный VPN-сервис. Более 10 серверов с кофейными названиями — на любой вкус. Лично взял Эспрессо — сеть прет как от кофеина ☕️ Безлимитный трафик, низкие цены, работа в РФ без проблем. ☕️ Попробовать: бот / мини-апп

9 May 2026, 14:37 UTC≈47,300 views0 reactions108 Starsread 12 August 2026

💻 Proxy Coffee запустили прокси, который работает даже в условиях ядерной войны. Внутри сервиса появился новый сервер ☕️ TG Espresso — с ним Телеграм работает при отключении мобильного интернета и даже при вторжении инопланетян. Подключить можно в 1 клик прямо в боте 👇 ⭐ Бот: @proxy_coffee_bot

28 Apr 2026, 17:02 UTC≈31,300 views0 reactions10,000 Starsread 12 August 2026
Photo

👑 Многие спрашивают про галочки у меня. Корона на @grozny — это верификация Major. Можно оформить прямо в @major — на аккаунт, канал или бота. 💰 К примеру, галочку на аккаунт как у меня можно взять за $3500 в год. Теперь все пользователи с верификацией Major получают ещё и эксклюзивную поддержку в Telegram — через @MajorSuppBot. 👑 Стать королём → @major

31 Mar 2026, 17:39 UTC≈40,200 views0 reactions215 Starsread 12 August 2026
Photo

🌩 Тучи над Телеграм сгущаются Сегодня Telegram начал активно рассылать уведомления пользователям из РФ, что сегодня последний день для покупки Premium. На деле — вряд ли последний, просто покупать станет чуть сложнее. ⛔️ А вот доступ к самому мессенджеру действительно могут ограничить уже с завтрашнего дня. На фоне блокировок миллионы людей ставят сторонние клиенты вроде Telega, которые могут читать ваши переписки

28 Mar 2026, 19:51 UTC≈37,900 views0 reactions124 Starsread 12 August 2026

🐸 Как я стал изгоем всей банковской системы Недавно, проводя обычный P2P-обмен с USDT на карту через CryptoBot, я оказался частью так называемой схемы треугольника. 💱 Как это работает: мошенник создает заявку на обмен, переводит тебе деньги с чужого (украденного или взломанного) счета, а крипту забирает себе. Жертва обнаруживает пропажу, обращается в банк, тот направляет запрос в ЦБ. В итоге все твои счета отлетают

22 Mar 2026, 14:30 UTC≈54,500 views0 reactions231 Starsread 12 August 2026

🔠 Блокировки Telegram в РФ усиливаются каждый день На данный момент более 50 000 пользователей ежедневно сидят тут через мои бесплатные прокси. Но их соединение в опасности — оно может оборваться в любой момент из-за новых блокировок. 🛡 У меня есть уникальное решение — устойчивые прокси с защитой от блокировок в Proxy.Coffee Только что добавил 2 новые локации: 🇬🇧 Лондон и 🇫🇷 Париж. За последнюю неделю переработал

1 Mar 2026, 20:00 UTC≈64,600 views0 reactions440 Starsread 12 August 2026

📕 Мой самый первый бот, который я запустил почти 11 лет назад, получил большое обновление. Это бот для чтения и прослушивания Корана. Теперь это полноценное мини-приложение внутри Telegram с удобным интерфейсом. ☪️ Решил выпустить обновление в этот символичный месяц — ведь Рамадан это месяц Корана. Любимая фича: теперь любым аятом можно сразу поделиться в чате или опубликовать в сторис Попробуйте: Quran

22 Feb 2026, 18:30 UTC≈60,900 views0 reactions212 Starsread 12 August 2026
Photo

🤝 Партнёрство с Proxy.Coffee Теперь каждый из вас может получать 30% с каждого платежа вашего реферала — пожизненно. ☕️ Мы выпустили большое обновление бота: • партнерская программа • новые серверы • автопродление прокси • два режима подключения Telegram-прокси: стандартный и с обходом DPI • множество мелких улучшений Вывод вашего дохода — на любой удобный вам способ. 💰 Зарабатывайте вместе с нами: приглашайте п

12 Feb 2026, 16:21 UTC≈99,700 views0 reactions473 Starsread 12 August 2026

⭐ Запустил свой прокси-сервис! Приватные прокси для Telegram & WhatsApp за один клик. Разверните свой прокси и получите индивидуальную ссылку подключения за пару секунд: 😎 Telegram: tg.proxy.coffee/.. 📱 WhatsApp: wa.proxy.coffee/.. Уже доступно более 5 серверов, и их количество будет только расти. Переключение между серверами — бесплатно. 🛡 Трафик защищён шифрованием MTProto и TLS — нет никаких логов. Полноценно

6 Feb 2026, 17:01 UTC≈55,300 views0 reactions122 Starsread 12 August 2026
Photo

✨ Заметили новый значок верификации Hold на канале? Кажется, мне как настоящему холдеру криптовалюты он подходит идеально. 😎 По моему опыту это уже третий рыночный цикл — и в каждом были моменты, когда можно было красиво зафиксироваться и выдохнуть… Вот опять, наблюдаю в эти дни как рынок льётся вниз, но я уже привык — и даже ловлю дежавю. 🐸 А вы тоже холд или уже фикс?

4 Feb 2026, 19:55 UTC≈53,000 views0 reactions378 Starsread 12 August 2026

⛱️ Только что запустил ИИ-бота, который анализирует текст и оформляет ваши посты кастомными эмодзи. А ведь неделю назад Telegram открыл доступ к кастомным эмодзи для всех ботов. Раньше это стоило от 1000 до 5000 TON. 🔍 Но чтобы вставить эмодзи, нужно знать его ID и сформировать тег. Делать это вручную — неудобно. Мой @EmojiusBot решает две задачи сразу: 1⃣ Разработчики ботов: отправляете эмодзи — получаете его ID

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 168,075 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

Domains linked from posts

3 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

proxy.coffee1 post · 12 February 2026 – 12 February 2026 · example post
rebooks.me1 post · 9 January 2026 – 9 January 2026 · example post
tpayer.net1 post · 29 January 2026 – 29 January 2026 · example post

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

“RamCode” (@ramcode), 80,946 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ramcode.

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.