Telegram RegisterThe public register of Telegram
Telegram profile photo for А нефиг высокомерить пикмиятка

Channel

А нефиг высокомерить пикмиятка

@medkhadi

Has discussion group

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

1,727subscribers

+663 since we began measuring on 11 September 2026

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

Register entry

Telegram ID-1002241596950
TypeChannel
Username@medkhadi
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live12 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/medkhadi

Topic

Other / unclassifiable — 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 7 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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.

Growth

1,0641,7271,395.511 September 2026 — 1,064 subscribers16 September 2026 — 1,066 subscribers25 September 2026 — 1,069 subscribers5 October 2026 — 1,093 subscribers7 October 2026 — 1,093 subscribers12 October 2026 — 1,727 subscribers11 September 202612 October 2026
6 measurements spanning 31 days, net +663. 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 965–1,826 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 02:421,727+634
7 Oct 2026, 03:311,093no change
5 Oct 2026, 02:371,093+24
25 Sept 2026, 23:591,069+3
16 Sept 2026, 23:361,066+2
11 Sept 2026, 09:471,064first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.

Анатомия человека | Медицина
@humananatomy_web · 38,568
Telegram ranks this channel #26 of 62 here — alongside 61 others — read 11 September 2026
ikhazin
@ikhazin · 32,987
Telegram ranks this channel #27 of 64 here — alongside 63 others — read 16 September 2026
MedVaKs
@medvaks · 20,782
Telegram ranks this channel #63 of 77 here — alongside 76 others — read 26 September 2026

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

“А нефиг высокомерить пикмиятка” (@medkhadi), 1,727 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/medkhadi.

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.