Telegram RegisterThe public register of Telegram
Telegram profile photo for Поступач

Channel

Поступач

@postypashki_mems

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

5,874subscribers

+31 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001639988310
TypeChannel
Username@postypashki_mems
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/postypashki_mems

Topic

Memes & entertainment — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 2 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@algoses/5892 Aug 2026, 12:03 UTC@postypashki_mems/1361 · this entry3 Aug 2026, 09:04 UTC1.0021 hours
@algoses/5914 Aug 2026, 18:05 UTC@postypashki_mems/1367 · this entry4 Aug 2026, 18:26 UTC1.0021 minutes
@postypashki_mems/1489 · this entry31 Oct 2026, 14:04 UTC@algoses/67431 Oct 2026, 15:04 UTC1.0060 minutes
@postypashki_old/181928 Jul 2026, 16:10 UTC@postypashki_mems/1355 · this entry29 Jul 2026, 19:25 UTC1.0027 hours
@postypashki_old/18294 Aug 2026, 15:50 UTC@postypashki_mems/1367 · this entry4 Aug 2026, 18:26 UTC1.002.6 hours
@postypashki_old/200131 Oct 2026, 09:59 UTC@postypashki_mems/1489 · this entry31 Oct 2026, 14:04 UTC1.004.1 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
@algoses5 (5/5 hand-verifiable sample passed)1.0060 minutes@algoses (3–2)
@postypashki_old6 (6/6 hand-verifiable sample passed)1.003.3 hours@postypashki_old (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. 1 of the 4 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 15 comparable posts for this entry, running 25 July 2026 to 31 October 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 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 keys clone_copy · clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 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.

Growth

5,8275,8875,8576 August 2026 — 5,843 subscribers6 August 2026 — 5,843 subscribers6 August 2026 — 5,841 subscribers9 August 2026 — 5,832 subscribers12 August 2026 — 5,827 subscribers16 August 2026 — 5,831 subscribers19 August 2026 — 5,841 subscribers22 August 2026 — 5,849 subscribers25 August 2026 — 5,840 subscribers28 August 2026 — 5,836 subscribers30 August 2026 — 5,832 subscribers2 September 2026 — 5,836 subscribers8 September 2026 — 5,856 subscribers12 September 2026 — 5,857 subscribers16 September 2026 — 5,868 subscribers25 September 2026 — 5,887 subscribers4 October 2026 — 5,875 subscribers11 October 2026 — 5,879 subscribers14 October 2026 — 5,878 subscribers17 October 2026 — 5,882 subscribers20 October 2026 — 5,878 subscribers23 October 2026 — 5,874 subscribers26 October 2026 — 5,872 subscribers2 November 2026 — 5,868 subscribers5 November 2026 — 5,864 subscribers9 November 2026 — 5,867 subscribers13 November 2026 — 5,874 subscribers5,8746 August 202613 November 2026
27 measurements spanning 100 days, net +31. 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 5,818–5,896 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
13 Nov 2026, 18:095,874+7
9 Nov 2026, 08:115,867+3
5 Nov 2026, 15:165,864-4
2 Nov 2026, 07:365,868-4
26 Oct 2026, 19:455,872-2
23 Oct 2026, 16:475,874-4
20 Oct 2026, 22:115,878-4
17 Oct 2026, 15:565,882+4
14 Oct 2026, 09:205,878-1
11 Oct 2026, 02:175,879+4
4 Oct 2026, 20:595,875-12
25 Sept 2026, 02:595,887+19
16 Sept 2026, 11:565,868+11
12 Sept 2026, 15:565,857+1
8 Sept 2026, 08:565,856+20
2 Sept 2026, 22:095,836+4
30 Aug 2026, 21:075,832-4
28 Aug 2026, 06:285,836-4
25 Aug 2026, 16:135,840-9
22 Aug 2026, 13:575,849first reading

Engagement

49 posts held, back to 24 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 10 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
34.4%
avg views ÷ 5,874 subscribers
Avg views / post
2,020
13 posts measured
Reaction rate
1.88%
reactions ÷ views · ER floor
Posts in window
13
of 49 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 3 November 2026
Posts held49 (24 July 2026 – 3 November 2026)
Views total26,240
Reactions total494
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 15:52 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

Video runtime
4m 23s
Average length
44s

Measured directly from 6 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

1,656 reactions across 41 posts, in 23 distinct kinds. The most used accounts for 26.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥43026.0%
❤40024.2%
🥰18911.4%
🤩875.25%
🙏865.19%
💯835.01%
😍663.99%
😭603.62%
🍌523.14%
❤‍🔥362.17%
🤔321.93%
😱291.75%
🌚281.69%
👍221.33%
🤯171.03%
💔90.543%
🐳70.423%
🕊70.423%
👏50.302%
🤓50.302%
3 further kinds60.362%

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

Measured over the 49 most recent posts we hold, published 24 July 2026 to 3 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.

Recent posts

Telegram’s own ‘edited’ marker: 6 of 13 posts held from the last 30 days (46.2%) 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).

3 Nov 2026, 16:45 UTC≈1,090 views25 reactionsread 4 November 2026
Photo

Когда выкладываешь первое резюме на хх составленное за 2 минуты: @postypashki_mems

❤23🍌2

2 Nov 2026, 06:27 UTC≈1,560 views42 reactionsread 4 November 2026
Video

@postypashki_mems

🔥33❤6👍2🐳1

1 Nov 2026, 13:45 UTC≈1,550 views29 reactionsread 4 November 2026
Photo

Хочу чтобы hr присылали отказы только такими открытками: @postypashki_mems

❤29

31 Oct 2026, 14:04 UTC≈1,030 views1 reactionsread 4 November 2026
Photo

Ты станешь специалистом, которого не заменит ИИ Написать код, запустить модель или посчитать A/B-тест теперь может ИИ. Поэтому одного умения пользоваться инструментами уже мало. Компаниям нужен человек, который понимает, какую задачу решает, может выбрать подход, заметить ошибку и довести дело до результата. Рутину поручат ИИ. Тебе доверят то, где нужно думать самому и отвечать за решение — за это и будут платить. …

🔥1

30 Oct 2026, 20:49 UTC≈2,350 views46 reactionsread 4 November 2026
Photo

@postypashki_mems

🙏33❤8🥰4🍓1

29 Oct 2026, 15:55 UTC≈2,040 views57 reactionsread 4 November 2026
Photo

Безумие — это точное повторение одного и того же действия, раз за разом, в надежде на изменение @postypashki_mems

🙏51👍4❤1💯1

29 Oct 2026, 15:47 UTC≈1,980 views29 reactionsread 4 November 2026
Photo

это в 2030 график вакансий (мне пох-й что это не функции) @postypashki_mems

🔥29

29 Oct 2026, 11:53 UTC≈2,310 views55 reactionsread 4 November 2026
Photo

стажеры би лайк @postypashki_mems

🤔31🔥11❤8😍5

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 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.

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.

Поступашки - ШАД, Стажировки и Магистратура
@postypashki_old · 47,414
Telegram ranks this channel #5 of 90 here — alongside 89 others — read 28 August 2026
Поступашки - Олимпиады, ЕГЭ, ДВИ
@postupashki · 31,954
Telegram ranks this channel #7 of 80 here — alongside 79 others — read 6 September 2026
Young&&Yandex
@Young_and_Yandex · 112,971
Telegram ranks this channel #7 of 92 here — alongside 91 others — read 14 August 2026
Т-Образование
@tbank_education · 113,774
Telegram ranks this channel #9 of 91 here — alongside 90 others — read 14 August 2026
Яндекс Образование
@Education_Yandex · 38,277
Telegram ranks this channel #19 of 96 here — alongside 95 others — read 31 August 2026
Альфа-Будущее
@alfafuture · 52,333
Telegram ranks this channel #23 of 99 here — alongside 98 others — read 26 August 2026
Young Стажёр - стажировки ИТ
@young_intern · 47,203
Telegram ranks this channel #34 of 94 here — alongside 93 others — read 29 August 2026
Школа 21
@school21sber · 53,265
Telegram ranks this channel #42 of 94 here — alongside 93 others — read 19 August 2026
8БИТ. Журнал Яндекс Образования
@journal_yandex_education · 18,781
Telegram ranks this channel #45 of 97 here — alongside 96 others — read 4 October 2026
Ozon Camp
@ozoncamp · 28,772
Telegram ranks this channel #49 of 97 here — alongside 96 others — read 10 September 2026
Grand Exam - Арсений Филин
@grandexam_ege · 47,463
Telegram ranks this channel #65 of 82 here — alongside 81 others — read 25 August 2026
Codeforces Official
@codeforces_official · 71,497
Telegram ranks this channel #72 of 78 here — alongside 77 others — read 20 August 2026
Глеб Соломин 🚀 24.05.2025
@gleb_solomin · 61,904
Telegram ranks this channel #75 of 77 here — alongside 76 others — read 22 August 2026

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

“Поступач” (@postypashki_mems), 5,874 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/postypashki_mems.

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.