Channel
@infotez
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
224subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001476000680 |
|---|---|
| Type | Channel |
| Username | @infotez |
| Description | Для любителей информатики: https://www.youtube.com/@infup КЕГЭ по информатике @kegeinf Для связи и предложений: @Kulukulyu |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/infotez |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:30 | 224 | no change |
| 7 Aug 2026, 16:23 | 224 | first reading |
8 posts held, back to 25 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 1 pageof 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. It is computed over the 3 of 8 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 8 (25 July 2026 – 7 August 2026) |
| Views total | 507 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:30 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 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 2 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.
5 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 40.0% | |
| ❤ | 1 | 20.0% | |
| 🤓 | 1 | 20.0% | |
| 🤩 | 1 | 20.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 3 of the 8 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 25 July 2026 to 7 August 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.
📡 Задача Radar с IOAI Сейчас в Астане проходит международная олимпиада по ИИ для школьников, участвуют почти 500 человек из 103 стран. Россию представляют 8 школьников из Москвы, Санкт-Петербурга, Новосибирска, Сочи, Ижевска и Волгограда. Следим за развитием событий и разбираем одну из тренировочных задач прошлого года. Разработать ИИ-модель для семантической сегментации данных радара. Нужно определять, что находи…
Photo, posted without a caption
👍2❤1🤓1
⚫️счезнуть и это возможно? Искусство испаряться: в Японии набирает популярность бизнес по полному стиранию личности Японское общество вывело право на жизнь с чистого листа на профессиональный и законодательный уровень. В стране набирает популярность услуга «дзёхацу» (в буквальном переводе — «испарение»), с помощью которой человек может полностью оборвать связи с прошлым и бесследно исчезнуть из поля зрения близких,…
Школа Информатики Физики и Технологии (сокр. ШИФТ). Как VK вовлекает школьников в образовательные проекты.
В 1502 году Леонардо да Винчи сделал то, что даже сегодня кажется невозможным. Имея под рукой лишь линейки, компасы и транспортиры, он создал карту итальянского города Имолы — такую точную, что она почти не отличается от современных спутниковых снимков Google Maps. Леонардо измерял углы улиц, расстояния между домами, направление дорог — всё вручную, шагами, наблюдением и чистой математикой. Никаких дронов. Никаких …
Превращаем свой почерк в устанавливаемый шрифт — для Claude Code сделали навык, который собирает полноценный TTF по фотографии. Достаточно написать алфавит на листе бумаги, сфотографировать его и загрузить снимок в Claude. Нейросеть сама распознает буквы, очистит изображение и соберет готовый шрифт. Если какая-то буква получилась неудачно, Claude заметит это и предложит переписать символ перед финальной сборкой. h…
🤩1
⚫️огда картина слишком реалистична ⚫️ Мексике автоледи врезалась в стену из-за тоннеля из мультфильма ⚫️евушка приняла нарисованный тоннель за настоящий. На стене эстакады была изображена сцена из серии мультфильмов, где Койот пытается обмануть Дорожного бегуна, рисуя фальшивый асфальт на скале. В реальности же эта хитрость сработала и на человеке: автомобилистка увидела в рисунке настоящий проезд и врезалась в ст…
❗️ Эти профессии уже исчезли и надо заметить, что все они были простые и с функциональной точки зрения легко заменяемые. ИИ меняет нашу жизнь, а как вы думаете какие специалисты исчезнут в ближайшее время?
Showing the 8 most recent of 8 posts we hold for @infotez. 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Информатика и не только!” (@infotez), 224 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/infotez.
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.