13 Aug 2026, 15:07 UTC1 viewsread 15 August 2026
tg://proxy?server=telegram.api.gemera.one&port=443&secret=e528623a8c18740415ab203788a7def0
Channel
python yandex notes
@mightypython
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001983038753 |
|---|---|
| Type | Channel |
| Username | @mightypython |
| Description | print('ну приплыли') |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mightypython |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 00:46 | 1 | no change |
| 7 Aug 2026, 19:40 | 1 | first reading |
Engagement
17 posts held, back to 26 May 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 1 page of 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 17 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 71
- Videos
- 7
- Links
- 166
Lifetime counters from Telegram’s own channel header, read 15 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.
- Video runtime
- 1m 29s
- Average length
- 30s
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.
Recent posts
4 Aug 2026, 15:31 UTC3 viewsread 15 August 2026
Photo
Photo, posted without a caption
30 Jul 2026, 10:09 UTC6 viewsread 15 August 2026
Photo
Очень крутой состав напротив, неубиваемые…
27 Jul 2026, 11:34 UTC6 viewsread 15 August 2026
https://t.me/proxy?server=192.168.10.55&port=1443&secret=dd944c6fe62743b9ec860fea84c30da251
17 Jul 2026, 10:54 UTC7 viewsread 15 August 2026
Forwarded from @nigat1vePhoto
Извините, это повторится ☕️ #всякре
8 Jul 2026, 12:39 UTC5 viewsread 15 August 2026
Photo
Photo, posted without a caption
5 Jul 2026, 22:33 UTC3 viewsread 15 August 2026
Forwarded from @nocrimeVideo
В сети хайпит сочнейший ИИ-тизер матча Норвегия – Бразилия. Драккары, трубки с ядом кураре и максимально аутентичный Винисиус в роли бойца племени ваямпи (или типа того). Короче, всем вальгалла, пацаны. 🤩 Подпишись на Ноу криминалити
4 Jul 2026, 15:22 UTC92 viewsread 15 August 2026
Куриное филе Фарш говядовый Картофель килополтаратый Консерв ананастый Овош разновый Гавай смешной Чето ещё Сельд вкусновая как вчера Красень плюс желтень
3 Jul 2026, 16:29 UTC4 viewsread 15 August 2026
Киви сельд лук Колбаса огурец сыр Лосось огурец сыр Кр палки яйцо сыр Паштет Два хлеба Лисон сок
22 Jun 2026, 13:01 UTC7 viewsread 15 August 2026
Ну, если сатори поднять, то 3 пачки почти готовые. Давай по основам распределим: 1)Лектра Айрис Темпус 2)Ясмин Данте Октавия 3)Сатори Бирна Фолик Поларис Фобос Миу ЛЕВ Корвус Сомна Дориан - прикинуть кого в основу больше хочется и поднимать. Кейла Эйден очень неплохо бы зашли так же ко второй пачке.
15 Jun 2026, 13:38 UTC8 viewsread 15 August 2026
https://t.me/proxy?server=192.168.10.55&port=1443&secret=dd168883b430a426e6850a2f6becebd9f2
15 Jun 2026, 07:52 UTC8 viewsread 15 August 2026
https://t.me/proxy?server=62.84.117.91&port=443&secret=dd47954b1fb7d92faf4a3cf615cae206ae
Showing the 12 most recent of 17 posts we hold for @mightypython. 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
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.
Mentions
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“python yandex notes” (@mightypython), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/mightypython.
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.