Video message, posted without a caption
🍌53🌚3😁2❤1😍1

Channel
@postypashki_old
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
47,236subscribers
+4,027 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001756387595 |
|---|---|
| Type | Channel |
| Username | @postypashki_old |
| Description | 6 лет помогаем получать офферы в BigTech, поступать в ШАД и проходить в топовые магистратуры. Вопросы, реклама: @vice22821 По покупке курсов: @menshe_treh Наши курсы: https://old.postypashki.ru/ Чат: @postypashki_old_chat Ютуб: youtube.com/@OfferBerry |
| Created | 31 January 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/postypashki_old |
Education — 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 9 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.
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.
Posts published here appear in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 6 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @postypashki_old/1829 · this entry4 Aug 2026, 15:50 UTC | @chad_protocol/5074 Aug 2026, 17:04 UTC | 1.00 | 74 minutes |
| @postypashki_old/1840 · this entry10 Aug 2026, 17:33 UTC | @chad_protocol/51310 Aug 2026, 17:43 UTC | 1.00 | 11 minutes |
| @postypashki_old/1980 · this entry18 Oct 2026, 17:06 UTC | @chad_protocol/57618 Oct 2026, 20:23 UTC | 1.00 | 3.3 hours |
| @chad_protocol/58921 Oct 2026, 14:58 UTC | @postypashki_old/1997 · this entry26 Oct 2026, 14:59 UTC | 1.00 | 5 days |
| @postypashki_old/1827 · this entry2 Aug 2026, 08:51 UTC | @algoses/5892 Aug 2026, 12:03 UTC | 1.00 | 3.2 hours |
| @postypashki_old/1829 · this entry4 Aug 2026, 15:50 UTC | @algoses/5914 Aug 2026, 18:05 UTC | 1.00 | 2.2 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @chad_protocol | 7 (7/7 hand-verifiable sample passed) | 1.00 | 3.3 hours | this entry (5–2) |
| @algoses | 10 (8/8 hand-verifiable sample passed) | 1.00 | 5.0 hours | this entry (10–0) |
| @zadachi_ds | 8 (8/8 hand-verifiable sample passed) | 1.00 | 7.0 hours | this entry (7–1) |
| @postypashki_mems | 6 (6/6 hand-verifiable sample passed) | 1.00 | 3.3 hours | this entry (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. 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 145 comparable posts for this entry, running 21 July 2026 to 14 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.
Of the group of 6 channels, the one whose matching posts we hold earliest is @ProdAnalysis. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 15 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.
This channel is in a group of 6 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 04:10 | 47,236 | +36 |
| 10 Nov 2026, 17:57 | 47,200 | +54 |
| 9 Nov 2026, 03:09 | 47,146 | +53 |
| 7 Nov 2026, 20:45 | 47,093 | +16 |
| 6 Nov 2026, 17:45 | 47,077 | +17 |
| 5 Nov 2026, 20:44 | 47,060 | +28 |
| 4 Nov 2026, 19:59 | 47,032 | +20 |
| 3 Nov 2026, 19:38 | 47,012 | +23 |
| 2 Nov 2026, 19:08 | 46,989 | +28 |
| 1 Nov 2026, 22:00 | 46,961 | +23 |
| 1 Nov 2026, 00:17 | 46,938 | +7 |
| 31 Oct 2026, 01:08 | 46,931 | +29 |
| 30 Oct 2026, 00:06 | 46,902 | +1 |
| 28 Oct 2026, 22:16 | 46,901 | +15 |
| 27 Oct 2026, 23:36 | 46,886 | +32 |
| 26 Oct 2026, 20:30 | 46,854 | +19 |
| 25 Oct 2026, 23:06 | 46,835 | +33 |
| 24 Oct 2026, 20:45 | 46,802 | +15 |
| 23 Oct 2026, 22:26 | 46,787 | +38 |
| 23 Oct 2026, 01:18 | 46,749 | first reading |
157 posts held, back to 21 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 208 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 157 (21 July 2026 – 15 November 2026) |
| Views total | 620,430 |
| Reactions total | 1,997 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 10:07 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.
Lifetime counters from Telegram’s own channel header, read 15 November 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.
Measured directly from 3 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.
9,831 reactions across 155 posts, in 31 distinct kinds. The most used accounts for 24.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,360 | 24.0% | |
| 🔥 | 2,353 | 23.9% | |
| 😁 | 2,169 | 22.1% | |
| 🍌 | 1,584 | 16.1% | |
| 👍 | 247 | 2.51% | |
| 🤯 | 210 | 2.14% | |
| ❤🔥 | 166 | 1.69% | |
| 🎃 | 109 | 1.11% | |
| 💋 | 93 | 0.946% | |
| 🤓 | 87 | 0.885% | |
| 🍓 | 57 | 0.58% | |
| 🌚 | 51 | 0.519% | |
| ⚡ | 45 | 0.458% | |
| 💯 | 45 | 0.458% | |
| 🐳 | 41 | 0.417% | |
| 👏 | 35 | 0.356% | |
| 😢 | 29 | 0.295% | |
| 😱 | 27 | 0.275% | |
| 🤔 | 22 | 0.224% | |
| 👀 | 20 | 0.203% | |
| 11 further kinds | 81 | 0.824% |
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 157 of the 157 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 9,885 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 157 most recent posts we hold, published 21 July 2026 to 15 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.
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 |
|---|---|---|---|
| 2SDnjcd9GCK | 1 | 8 August 2026 | 8 August 2026 |
| 2VSb5xofJie | 1 | 17 August 2026 | 17 August 2026 |
| 2VtzqvMiGqY | 1 | 22 July 2026 | 22 July 2026 |
| 2W5zFHGYhey | 1 | 6 October 2026 | 6 October 2026 |
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 157 most recent posts we hold, published 21 July 2026 to 15 November 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.
Telegram’s own ‘edited’ marker: 11 of 40 posts held from the last 30 days (27.5%) 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).
Video message, posted without a caption
🍌53🌚3😁2❤1😍1
Как устроена секция "ML Coding" На первый взгляд, ML Coding звучит как "небольшое упражнение по написанию кода, связанного с ML, но не leetcode". Именно так часто формулируют рекрутеры. На практике же сложность и формат могут сильно варьироваться: от десяти строк на PyTorch до полноценного пайплайна обработки данных. Поэтому первый шаг к успеху - вытащить максимум конкретики ещё до интервью. Где искать информацию •…
❤8🔥3👍1👏1
Где ты застрял по пути к офферу? На собеседовании сложно объяснить, как ML-модель будет работать в продукте? Теряешься на кейсах по A/B-тестам? Или до интервью дело не доходит: на отклики не отвечают? Выбирай курс под задачу, которую хочешь решить: ✨ML System Design Разберёшь пайплайн данных, инференс, нагрузку и мониторинг качества. Спроектируешь ML-систему и потренируешься защищать свои решения на собеседовании…
❤7❤🔥2👌2🔥2
Реально собеседование ML System Design От тим лида WildBerries. Cмотрим! Смотрим! https://www.youtube.com/watch?v=UfTekz0bhiw Именно такие мок собесы мы проводим на нашем курсе ML System Design. Это лишь малая часть того, чему мы учим. Если хотите научиться щелкать кейсы как орешки, вести диалог и защищать свои решения, то вам к нам. Сейчас действует хорошая скидка в честь черной пятницы! ➡️ Записаться
😁9🔥3❤1
Гайд на собесы аналитика в Ozon Ozon Camp 16 ноября объявит набор на стажировку по аналитике. Наши выпускники сейчас активно ходят по собесам, поэтому по горячим следам собрали гайд с реальными вопросами и задачами из Ozon. Внутри: SQL, Python, A/B-тесты, статистика и продуктовая аналитика: с 16 по 20 грейд, от стажёра до Senior. У каждой задачи указаны грейд и ориентир по времени на решение. 🔥 А разбор экзаменов …
🔥20😁4❤1🍌1
Слив протоколов АВ тестирования для кейс-интервью Х5 Прямо сейчас идет набор на стажировку X5: BIG IN. Наши выпускники не только сейчас активно проходят собесы, но и уже давно закрепились в штате и проводят собесы. В честь нашей черной пятницы наших курсов, делимся гайдом по проведению АВ тестирования в Х5 на основе внутренних методичек, публичных выступлений и протоколов проведения собеседований. Делитесь с друзья…
😁8❤7🤔3🍌1🎃1🔥1
Чёрная пятница от Поступашек! Товарищи, хотите получить оффер в бигтех, перейти на более высокую позицию или увеличить зарплату? Мы открыли распродажу всех карьерных курсов Поступашек, которые помогут достичь этих целей — записывайся 📌 Скидки действуют только до 15 ноября включительно! Все курсы и актуальные цены можно посмотреть на сайте. 🔊Обращаем внимание на новую линейку курсов по ML System Design, A/B-тестам,…
😁21❤3🍌1🎃1🔥1
Как устроиться в Яндекс в 2027 году Товарищ, ты прошёл 10 собесов, решил задачку на графы, познакомился с командой. И тут рекрутер пишет: «Остался финальный этап. Подскажи точное время и год рождения». 0. Пробей даты рождения эйчара и нанимающего. Проверь совместимость с обоими. Если с эйчаром 90%, а с нанимающим 12%, добавь в резюме «умею работать со сложными стейкхолдерами». 1. Убери дату рождения из резюме. На …
😁203🔥52❤22👍5😢3🍌1🐳1🤓1
Как собеседуют в Nebius Рассказывает наш выпускник, который проходил недавно собеседование на позицию Senior ML Engineer, удалёнка из Европы, все интервью проходило на русском. Процесс и этапы HR вышел на меня сам в Linkedin. Первый созвон: обсуждение вакансии, мотивация. Команда раньше тренировала собственные модели, но сейчас фокус сместился на тонкую настройку под клиентов. Уже на этом этапе мне показалось, что …
❤35😁11🔥6🎃2🌚1🍌1👍1
Продолжаем знакомиться с талантливыми воспитанниками «Поступашек». Сегодня в гостях - Андрей, обычный парень из Воронежа, который сейчас живет в Лондоне и работает ресерч инженером в банке Револют. При этом сам Андрей долгое время занимался музыкой, потом пробовал себя в разработке, а потом кардинально сменил направление на дата сайнс и ресерч. Обо всем этом в ролике. Смотрим интервью по ссылке: https://www.youtube.…
🔥24❤7🍌4🐳2❤🔥1
Помните того чела, который на вопрос рекрутера ответил, что знаком с алгоритмом Ynna Zist и Yasasu Bivu? Ну вот наш преподаватель бэкенда позвал его на собес и пришёл вьетнамец, который отвечал нейронкой на все вопросы (даже про сломанный сервер в майнкрафте). Смотрим, смотрим, смешнявку, если любите маму! https://www.youtube.com/watch?v=yrUMPFIlhQg
🔥33🍌9❤6😁2
Полный цикл отбора в Revolut (Backend SWE) Процесс найма от выпускника наших курсов бэкенда. Весь процесс до оффера занял три недели. Прямо сейчас у Revolut идет набор на стажировку с релокацией в Дубай/Лондон помогут. Красный паспорт - не проблема. Первый звонок с рекрутером Разговор примерно на 30 минут: опыт, проекты, мотивация и почему вообще интересен Revolut. Не пересказываем резюме, лучше рассказать про пар…
❤28🔥10👍3😁2
Showing the 12 most recent of 157 posts we hold for @postypashki_old. 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.
@postypashki_old edited 20 posts 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.
We recorded 14 posts on @postypashki_old 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.
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.
Named by 22 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@postypashki_old named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was 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.
Read from Telegram’s recommendation API, most recently 28 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.
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.
This channel appears in 56 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“Поступашки - ШАД, Стажировки и Магистратура” (@postypashki_old), 47,236 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/postypashki_old.
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.