Channel
@KursyGuru
On this record: Also posting the same content · Growth · Engagement · Reactions · Advertising · Posts · Citations · Cite this entry
2,897subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001260645750 |
|---|---|
| Type | Channel |
| Username | @KursyGuru |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/KursyGuru |
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 07:57 | 2,897 | -2 |
| 7 Aug 2026, 01:15 | 2,899 | no change |
| 7 Aug 2026, 01:04 | 2,899 | first reading |
20 posts held, back to 14 August 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 20 posts for this entry, the most recent from 10 March 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 100.0% |
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 2 of the 20 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 August 2024 to 10 March 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VfnxyWLDrp | 1 | 26 November 2024 | 26 November 2024 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 20 most recent posts we hold, published 14 August 2024 to 10 March 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
✨ AI-подбор каналов для постинга вакансий и резюме Теперь в боте https://t.me/it_jobs_resumes_bot AI помогает подбирать подходящие каналы для публикации вакансий и резюме. Как это работает: 📝 вы заполняете форму вакансии или резюме 🤖 AI анализирует текст 📢 сервис сразу отмечает подходящие каналы ✍️ при желании выбор можно изменить вручную Это быстрее, удобнее и помогает не тратить время на ручной подбор. Попробов…
🔥 Скидка 50% на публикацию вакансий и резюме Если вы сейчас ищете сотрудника или работу - хороший момент разместиться дешевле. Мы сделали скидку 50% на публикацию во все каналы GeekLink. Это значит, что можно охватить сразу большую аудиторию IT-специалистов и компаний, но за половину стоимости. 👉 Посмотреть каналы: https://t.me/geeklink_ru/582 Разместить вакансию или резюме можно прямо через бота - быстро и без п…
AI-исправление резюме 🤖 Повышайте охваты своего резюме за счёт исправления типичных ошибок и улучшения формулировок. ИИ поможет сделать текст более понятным, структурированным и привлекательным для работодателей. Как использовать: 1️⃣ Запустите Telegram-бота: https://t.me/it_jobs_resumes_bot (выберите пункт «Разместить резюме»). 2️⃣ Заполните поля резюме. 3️⃣ Нажмите кнопку ✨ AI-исправление. Стоимость — 100 ⭐️ …
🍏🤖
IT нетворкинг 2.0! Встречайте Telegram-бот ☕️ Случайный кофе 2.0, который по пятницам подбирает собеседника для нетворкинга. В прошлой версии бота приняли участие более 1000 участников. В этой мы учли прошлые недостатки и пожелания. Теперь не нужно нигде дополнительно регистрироваться. Запускаете бот и принимаете участие! Для каких целей: - деловое общение (по работе, карьере, технологиям); - и/или свободное обще…
🗂 Автоподбор релевантных резюме. Доступно пользователям с Premium-подпиской. Что это такое Сервис сам подбирает кандидатов под профиль вашей вакансии, учитывая стек, грейд, опыт, зарплатные ожидания, формат работы и ключевые слова. Вы получаете готовую ленту резюме, отсортированную по степени совпадения и дате. Как это работает 1️⃣ Опубликуйте вакансию. 2️⃣ После модерации перейдите в панель управления вакансиям…
🔥 Раскройте весь потенциал своего IT-поиска с GeekLink! Неважно, ищете ли вы работу мечты или идеального кандидата — у нас есть все инструменты, чтобы ускорить этот процесс. 👨💻 Для кандидатов: 1️⃣ Будьте на виду у лучших. Опубликуйте резюме в GeekLink.io и получайте приглашения от топовых компаний. 2️⃣ После публикации в GeekLink резюме разлетится по подходящим 42 Telegram-каналам прямо к рекрутерам. 3️⃣ Хватит с…
🥳🎂 20 000-й зарегистрированный пользователь! Каждый из вас — часть большого сообщества IT и Digital-специалистов, которые развиваются, ищут работу, делятся опытом и прокачивают себя. Мы запустили GeekLink.io с идеей создать живой канал коммуникации между теми кто ищет новые карьерные возможности и теми, кто их предлагает. И это работает. Теперь нас уже двадцать тысяч. Это очень мотивирует двигаться дальше 💪
С момента основания на GeekLink опубликовали свыше 10 тысяч IT и Digital вакансий. И вот какая статистика получилась по средним зарплатам в порядке убывания (руб/мес). 1. Golang-разработчик 336 461 2. Machine Learning Engineer 289 000 3. Разработчик на C++ 287 245 4. Java-разработчик 283 374 5. Дата-инженер 280 538 6. Разработчик на Spring Framework 279 966 7. Администратор баз данных 279 071 8. DevOps-инженер 268 0…
✋ Всем привет! Рекрутеры и эйчары часто писали, что хотели бы видеть функцию открытия контактов в базе резюме. Рад сообщить, что теперь это возможно для пользователей с 🔥Premium-подпиской! С такой подпиской можно открывать до 10 контактов в день. Кроме этого доступно 10 новых веток личных сообщений. Продуктивной работы!
👨🎓🆕ч📞карта🗺📍💩
✋Всем привет! Отличная новость! Мы снизили стоимость размещения PRO-вакансий и резюме в GeekLink.io Было 2980 руб - стало 1980 руб 🔥 Для Premium-пользователей: было 1480 руб - стало 990 руб 🔥 PRO-вакансии и резюме автоматически поднимаются в каталоге и категориях + дополнительно постятся в TG-каналах и Linkedin. В среднем, PRO-вакансии и резюме получают в 4-5 больше охвата, чем стандартные! Не упустите возможност…
Showing the 12 most recent of 20 posts we hold for @KursyGuru. 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.
Citation-graph rank — 158,559 of 1,480,688entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Онлайн курсы 🎓 Агрегатор «Курсы.Гуру»” (@KursyGuru), 2,897 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/KursyGuru.
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.