Telegram RegisterThe public register of Telegram

Channel

Цікаве IT

@tsikave_it

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,426subscribers

-6 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001849046720
TypeChannel
Username@tsikave_it
DescriptionЦікавий канал про нейромережі та штучний інтелект. Слідкуй за всіма новинками у прогресі людства разом із нами! Founders: @dlnsky17 | @potseluykooo
CreatedBetween 1 October 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/tsikave_it

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@tsikave_it/139 · this entry4 Mar 2025, 10:00 UTC@it_techgen/10434 Mar 2025, 10:00 UTC1.00under a minute
@it_techgen/104811 Sept 2025, 15:31 UTC@tsikave_it/147 · this entry11 Sept 2025, 15:31 UTC1.00under a minute
@it_techgen/105124 Nov 2025, 14:03 UTC@tsikave_it/150 · this entry24 Nov 2025, 14:03 UTC1.00under a minute
@tsikave_it/152 · this entry14 Apr 2026, 08:01 UTC@it_techgen/105614 Apr 2026, 08:02 UTC1.00under a minute
@it_techgen/104612 Jun 2025, 11:02 UTC@tsikave_it/144 · this entry12 Jun 2025, 11:06 UTC0.964 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@it_techgen8 (8/8 hand-verifiable sample passed)0.98under a minute@it_techgen (71)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 14 September 2024 to 30 June 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @it_techgen. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

7,4267,4327,4297 August 2026 — 7,432 subscribers7 August 2026 — 7,431 subscribers10 August 2026 — 7,426 subscribers7 August 202610 August 2026
3 measurements spanning 4 days, net -6. 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 7,425–7,433 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:387,426-5
7 Aug 2026, 11:327,431-1
7 Aug 2026, 07:027,432first reading

Engagement

20 posts held, back to 14 September 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof 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 30 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
41
Videos
54
Links
60

Lifetime counters from Telegram’s own channel header, read 12 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 42s
Average length
1m 42s

Measured directly from 1 video 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.

Reaction mix

52 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 53.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2853.8%
👍1325.0%
🔥611.5%
🤯23.85%
😁11.92%
😍11.92%
🤔11.92%

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 19 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 52reactions 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 14 September 2024 to 30 June 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.

Recent posts

30 Jun 2026, 09:03 UTC831 views1 reactionsread 12 August 2026
Photo

GitHub Copilot Unpacked: Features & Cost Control 📅02 липня 2026, 11:00-12:00 (Kyiv time) 📌Teams Townhall, online | free Мова вебінара: англійська Запрошуємо вас на зустріч, на якій розглянемо, як організації можуть придбати GitHub та GitHub Copilot і керувати ними через Azure, зокрема плани, ліцензування, оплату за фактичне використання та виставлення рахунків. Ми також розглянемо перехід від Premium Request Units

1

29 Jun 2026, 10:02 UTC913 views1 reactionsread 12 August 2026
Photo

Ера Agenting: від Vertex AI до Agent Platfrom 📅30 червня 2026, 11:00-12:00 (Kyiv time) 📌Google Meet, online | free Gemini Enterprise Agent Platform — це новий підхід Google до побудови AI-рішень, у центрі якого знаходяться не моделі, а агенти. На зустрічі розглянемо, як еволюціонувала платформа Vertex AI, які можливості з'явилися для створення та управління агентами, та як організації можуть використовувати їх для а

👍1

14 Apr 2026, 08:01 UTC≈1,570 views2 reactionsread 12 August 2026
Photo

Вебінар: Економіка використання Google Workspace: від оптимізації витрат до бізнес-результатів 📅 16 квітня 2026, 11:00 (Kyiv time) 📌 Google Meet, online | free Мова вебінару: англійська Багато компаній продовжують ліцензії на свій робочий інструментарій «за замовчуванням», не переглядаючи, чи відповідають їхня вартість і можливості поточним потребам бізнесу. Оптимізуйте ІТ-бюджет разом із Google Workspace. На вебін

🤯2

25 Feb 2026, 11:01 UTC≈1,950 views2 reactionsread 12 August 2026
Photo

Вебінар: GenAI, що окупається: впровадження Gemini для Google Workspace 📅 26 лютого 2026, 11:00-12:00 (Kyiv time) 📌 Google Meet, онлайн | безкоштовно ➡️ Мова вебінару: англійська GenAI обіцяє підвищення продуктивності, але справжня цінність відчутна лише за правильного підходу. Запрошуємо подивитися, як Gemini для Google Workspace перетворюється з гучної обіцянки на практичний інструмент — через бізнес-контекст, пр

1👍1

24 Nov 2025, 14:03 UTC≈2,290 views5 reactionsread 12 August 2026
Photo

Ми раді запросити вас на нашу майбутню серію вебінарів, присвячену Microsoft Copilot, де ми детально розглянемо, як інструменти на базі штучного інтелекту можуть змінити вашу повсякденну роботу! 25 листопада 2025: Copilot Chat — розкажемо, як Copilot Chat робить спілкування з ШІ інтуїтивним, простим та інтегрованим у Microsoft 365. 02 грудня 2025: M365 Copilot for Power Users — дізнайтеся, як досвідчені користувачі

2👍1🤔1😁1

7 Nov 2025, 09:01 UTC≈2,030 views2 reactionsread 12 August 2026
Photo

✨ 21 листопада на SEO-конференції Collaborator.pro отримайте потужний заряд бадьорості та нові корисні знання, що дозволять ефективно просуватись у світі, де панує AI У програмі: ► Sitemap.xml: технічні трюки, що дають результат Анна Матвієнко, технічна SEO-спеціалістка, SEO-консультантка ► Лінкбілдинг в епоху AI SEO disruption. Як змінювати поточні тактики Ігор Рудник, Founder Collaborator.pro та Referr ► Тема-с

2

20 Oct 2025, 11:03 UTC≈1,970 views4 reactionsread 12 August 2026
Photo

🔥SEO-конференція Collaborator.pro👉21 листопада о 9:00 Не втрачайте шанс отримати цінні знання та перейняти досвід у найкращих з кращих У програмі: • 10 доповідей топових спікерів • лише актуальні теми, практичні знання та реальні кейси • збір коштів для ЗСУ • розіграш подарунків від спонсорів і партнерів конференції 🐹Цієї осені за традицією говоримо про просування на світовій SEO-арені Приєднуйтесь, це безкоштовн

3🔥1

11 Sept 2025, 15:31 UTC≈2,420 viewsread 12 August 2026
Photo

Як рітейлу та e-commerce створювати персоналізований досвід з AWS Gen AI та Nova Canvas Приєднуйтесь до вебінару Crayon, щоб дізнатися, як інструменти AWS допомагають поєднувати роботу з даними та креативні можливості в єдину екосистему. Ви побачите, як компанії можуть створювати більш залучаючий та персоналізований досвід для покупців. На вебінарі спікери розкажуть: • Чому важливі коректні джерела та суміжні техно

28 Aug 2025, 10:02 UTC≈2,440 views3 reactionsread 12 August 2026
Photo

SEO-просмажка з Олександрою Хіловою Від якості ваших посилань залежить видимість у пошуку. Чи впевнені ви, що ваш беклінк-профіль достатньо сильний? 4 вересня з 11:00 до 22:00 у SEO-чаті Collaborator.pro пройде SEO-просмажка. Ставте питання експертці щодо перевірки донорів, оптимізації анкорного профілю, уникнення токсичних посилань. Отримуйте цінні поради та корисні лайфхаки ⚡Гілка залишатиметься відкритою лише д

🔥3

1 Jul 2025, 07:05 UTC≈2,820 views3 reactionsread 12 August 2026
Video

Collaborator святкує 8️⃣ річницю З цієї нагоди запускаємо конкурс корисних AI-рішень для SEO. Показуйте свої круті промпти, агентів чи методики і вигравайте головний приз — Lenovo IdeaPad 💡 Надсилайте своє рішення з хештегом #наконкурс у гілку AI SEO Telegram-чату Collaborator 🎥 У прямому етері 29 липня Сергій Кокшаров обере переможця Доєднуйтеся до Telegram-чату Collaborator вже зараз та діліться своїми ідеями

3

12 Jun 2025, 11:06 UTC≈2,910 views0 reactionsread 12 August 2026
Photo

Генеративний ШІ від AWS для рітейлу: Amazon Q & Bedrock в дії 📅 19 червня 2025 | 11:00 📌 Teams Town Hall, участь безкоштовна Цей вебінар занурить вас у практичне застосування провідних сервісів AWS, таких як Amazon Q та Amazon Bedrock, що розкривають безпрецедентні можливості для оптимізації операцій, персоналізації взаємодії з клієнтами та інновацій у рітейлі. Дізнайтесь, як використовувати потужність Generative A

11 Jun 2025, 08:03 UTC≈2,200 views4 reactionsread 12 August 2026
Photo

🔥Сьогодні — просмажка контенту від Анастасії Крижановської Вже о 10:00 експертка почала відповідати в гілці на запитання й розбирати ваші тексти Це можливість отримати рекомендації від людини, яка в контенті вже понад 15 років 👉Зустрічаємося в гілці «Просмажка контенту з Анастасією Крижановською» в SEO-комʼюніті Collaborator Важливо: після 12 годин доступ буде закрито — гілка зникне 12 червня о 10:00

4

Showing the 12 most recent of 20 posts we hold for @tsikave_it. 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.

Citation-graph rank

Citation-graph rank — 47,568 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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.

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Цікаве IT” (@tsikave_it), 7,426 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/tsikave_it.

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.