Channel
@IT_Tsaritsy
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
453subscribers
+14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002532165427 |
|---|---|
| Type | Channel |
| Username | @IT_Tsaritsy |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/IT_Tsaritsy |
Job listings — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 07:37 | 453 | +1 |
| 9 Sept 2026, 13:58 | 452 | -1 |
| 30 Aug 2026, 07:26 | 453 | -2 |
| 22 Aug 2026, 16:46 | 455 | +3 |
| 15 Aug 2026, 17:33 | 452 | +12 |
| 8 Aug 2026, 05:05 | 440 | no change |
| 7 Aug 2026, 11:55 | 440 | +1 |
| 7 Aug 2026, 08:48 | 439 | first reading |
4 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 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 4 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
70 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 40 | 57.1% | |
| 🔥 | 15 | 21.4% | |
| 😇 | 7 | 10.0% | |
| ✍ | 3 | 4.29% | |
| 🙏 | 3 | 4.29% | |
| 🍾 | 2 | 2.86% |
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 4 of the 4 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 70 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 24 July 2026 to 3 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.
Царицы 🖤 Кажется, сейчас не самые простые времена для поиска работы. Конкуренция растет, вакансий становится меньше, а хорошее резюме часто решает, позовут ли вас на собеседование. У нас появилась идея! 💡 Как многие знают, Полина — HR, и она готова помочь с вашими резюме. Если вы сейчас в поиске работы или просто хотите привести резюме в порядок, она готова посмотреть его и дать рекомендации. Это бесплатно и по-ч…
❤🔥22😇7🙏3
Царицы! 🖤 Рубрика #Молвила_Царица возвращается, и у нас новая гостья 😯 Знакомьтесь — Евгения Дашкевич, квалифицированный юрист, эксперт в сфере комплексной юридической поддержки IT-бизнеса и ко-фаундер агентства BETOBELEGAL, которое помогает IT-компаниям получать льготы, заводить софт в реестр отечественного ПО и не тонуть в бумажках вроде политик и договоров 💼 Евгения каждый день разгребает с клиентами то, что мно…
❤🔥7🔥5🍾2
ИИ-агенты в разработке — это удобно, но не безопасно «по умолчанию» Собрали шпаргалку: как не слить секреты, не сломать репозиторий и не дать агенту лишних прав. Все правила — это здравый смысл + старые добрые практики разработки. 1. Конфиденциальные данные — вне папки проекта Агент читает контекст своей рабочей папки, поэтому: 🔗 Не храните там NDA, паспорта, телефоны и прочую чувствительную инфу — заведите для это…
❤🔥4🔥4✍3
Лето — пора отпусков, и кажется, оно пролетает слишком быстро! ☀️ Август уже совсем близко, а значит, и осень не за горами. У Ани отпуск уже позади (фотографии прилагаются 🎞), а Полина только собирается в Батуми 🇬🇪 — так что скоро будет новая порция красивых кадров. Аня в этом году никуда не летала, но отпуск получился насыщенным: отдых в Завидово, соревнования по фридайвингу, две фотосессии, съемки для "утреннего…
❤🔥7🔥6
Showing the 4 most recent of 4 posts we hold for @IT_Tsaritsy. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“IT Царицы” (@IT_Tsaritsy), 453 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/IT_Tsaritsy.
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.