Channel
@tickettotender
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
1,411subscribers
+17 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001719981741 |
|---|---|
| Type | Channel |
| Username | @tickettotender |
| Created | 6 June 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/tickettotender |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 21:00 | 1,411 | +1 |
| 5 Sept 2026, 22:21 | 1,410 | +5 |
| 1 Sept 2026, 20:54 | 1,405 | -1 |
| 29 Aug 2026, 23:54 | 1,406 | +1 |
| 27 Aug 2026, 01:29 | 1,405 | -2 |
| 24 Aug 2026, 03:05 | 1,407 | +3 |
| 20 Aug 2026, 06:38 | 1,404 | +1 |
| 16 Aug 2026, 22:13 | 1,403 | -1 |
| 10 Aug 2026, 06:15 | 1,404 | +10 |
| 7 Aug 2026, 08:40 | 1,394 | no change |
| 6 Aug 2026, 20:04 | 1,394 | first reading |
20 posts held, back to 6 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 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
42 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 18 | 42.9% | |
| ❤ | 12 | 28.6% | |
| 👍 | 7 | 16.7% | |
| ✍ | 2 | 4.76% | |
| 🫡 | 2 | 4.76% | |
| ❤🔥 | 1 | 2.38% |
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 15 of the 20 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 6 July 2026 to 5 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tickettotender. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 6 July 2026 to 5 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
⚡️ Госзакупки захватывают маркетплейсы Привет, друзья! Свежее из Думы: 23 июля в третьем чтении приняли закон об эксперименте — с 1 октября 2026-го закупки «с полки» пустят через маркетплейсы, наряду с привычными ЭТП. Обкатали на школах и колледжах: 17 контрактов, от выбора до поставки 3–6 дней. Кто «полку» ещё не щупал: это витрина предварительных предложений, из которой заказчик сам выбирает товар. Без заявок и ком…
❤1
Posted without readable text
🔥7
Коллеги, нужна помощь. Есть ли среди вас специалисты, которые хорошо разбираются в GetCourse? Нужна консультация по нескольким техническим вопросам: настройка процессов, автоматизации и логика работы платформы. Если сможете помочь сами или можете порекомендовать человека с хорошим опытом — буду очень благодарен. Напишите, пожалуйста, в комментариях или в личные сообщения. Спасибо!
Posted without readable text
❤1🔥1
Привет, друзья! Я фанат тайм-менеджмента и статистических исследований — у меня даже пара патентов есть, связанных с анализом данных. Поэтому мимо свежего интервью Максима Дорофеева (того самого, «Джедайские техники») пройти не смог. Дорофеев сделал то, на что решится редкий автор методик: взял все практики из своих книг, набрал 260 участников и прогнал через корреляционный анализ с бутстреп-симуляцией. Проверил собс…
🔥6🫡2
Друзья, коррективы в расписание 👇 Сегодняшний воркшоп по ИИ для закупок переносится. Не рассчитал загрузку — лучше сделать нормально в среду, чем на бегу сегодня. Новая дата: среда, время то же. Извините за смещение, но так будет полезнее для всех 🤝 PS. Кто голосовал, что готовы стартовать - пишите в личку, есть предложение)
Posted without readable text
👍1
Привет, друзья! 🤝 Хочу похвалить Диму и его коллег. Ходили на все воркшопы и делали домашку. Иногда лениво, иногда одной левой, за полчаса до созвона — но делали. И вот результат: Дима с коллегами собрал себе сервис, который закрывает сразу несколько ёмких задач по закупкам. Отзыв — на видео 👆 Завтра, 27 июля в 18:00 МСК, — пятая и завершающая встреча первого блока. Идём в ЕИС и собираем скилл с инструментами по а…
👍1
Дайджест ИИ в госзакупках 20.07-26.07. 1. Бизнес пользуется ИИ в закупках, но выбор поставщика ему не отдаёт. Свежее исследование ЭТП «ТендерПро»: более 75% компаний не готовы доверить ИИ полный цикл закупки. Что пугает — потеря контроля (73%), юридические риски (62%), утечка данных (56%). Самое «неавтоматизируемое», по мнению 78% опрошенных, — анализ технических предложений и итоговое сравнение условий поставщиков. …
❤3
Дайджест: ИИ в госзакупках (неделя 13–19 июля 2026) 1. Правительство утвердило KPI по внедрению ИИ для 19 отраслей, включая госуправление. 16 июля вице-премьер Дмитрий Григоренко сообщил, что показатели эффективности внедрения ИИ разработаны для всех ключевых отраслей — от финансов и госуправления до сельского хозяйства, в обсуждении участвовали более 350 ведомств и организаций. Акцент — на измеримых эффектах; для к…
👍1
Привет, друзья! Знаете мем про «six seven»? Когда шесть или семь — «ну примерно одно и то же». Смешно ровно до тех пор, пока так не начинает думать ИИ, разбирая юридические документы. Сейчас копаю очень интересную задачу — научить ИИ прогнозировать решение ФАС по конкретной жалобе. Первая идея кажется очевидной: взять базу жалоб с решениями, загрузить в векторную базу и искать похожие кейсы. Классический RAG. Каза…
👍3
⛰ «А что за поход-то?» — рассказываю. Привет, друзья! После вчерашнего поста про поход в личку прилетело несколько вопросов: что за формат, кто едет, что там будет? Отвечаю всем сразу. Но сначала — почему я вообще считаю, что ехать надо именно сейчас. Время непростое, чего уж там. Ставки, урезанные бюджеты, заказчики переписывают планы на ходу. И в такие периоды многие совершают одну и ту же ошибку — вцепляются в раб…
👍1
Showing the 12 most recent of 20 posts we hold for @tickettotender. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 1 registered channel — 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.
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 1 seed channel's Telegram-generated recommendation list in total. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Тендеры и госзакупки | ИИ-инструменты” (@tickettotender), 1,411 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/tickettotender.
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.