Рассказываем про работу и культуру КРОК изнутри — через опыт людей, процессы и решения. Проверишь на мэтч?
Вакансии: careers.croc.ru/vacancies
Программы для студентов: @brainzbycroc
Created
Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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 the other topics.
Growth
26 measurements spanning 95 days, net -906. 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 6,996–8,461 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
8 Nov 2026, 23:16
7,165
-7
5 Nov 2026, 07:31
7,172
-10
2 Nov 2026, 10:11
7,182
-576
30 Oct 2026, 00:16
7,758
-534
27 Oct 2026, 01:26
8,292
+1,073
23 Oct 2026, 22:29
7,219
+6
20 Oct 2026, 15:59
7,213
+1
17 Oct 2026, 13:28
7,212
-65
14 Oct 2026, 09:04
7,277
-6
10 Oct 2026, 22:20
7,283
-18
4 Oct 2026, 19:19
7,301
-93
24 Sept 2026, 22:41
7,394
-44
17 Sept 2026, 04:39
7,438
-12
13 Sept 2026, 01:59
7,450
-15
9 Sept 2026, 12:19
7,465
-119
4 Sept 2026, 06:41
7,584
-45
31 Aug 2026, 16:16
7,629
-21
28 Aug 2026, 12:43
7,650
-98
25 Aug 2026, 21:43
7,748
-108
22 Aug 2026, 12:17
7,856
first reading
Engagement
29 posts held, back to 16 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 35 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
24.0%
avg views ÷ 7,165 subscribers
Avg views / post
1,720
10 posts measured
Reaction rate
2.29%
reactions ÷ views · ER floor
Posts in window
10
of 29 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 9 November 2026
Posts held
29 (16 July 2026 – 9 November 2026)
Views total
17,169
Reactions total
393
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 17:48 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.
What this channel posts
Photos
≈1,580
Videos
≈84
Links
≈409
Lifetime counters from Telegram’s own channel header, read 11 November 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.
Video runtime
4m 44s
Average length
41s
Measured directly from 7 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.
Reaction mix
1,153 reactions across 27 posts, in 21 distinct kinds. The most used accounts for 31.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
361
31.3%
❤🔥
263
22.8%
❤
173
15.0%
😍
94
8.15%
😁
57
4.94%
custom 5260663973514072822
52
4.51%
💘
35
3.04%
🥰
21
1.82%
💅
19
1.65%
🤯
12
1.04%
🫡
12
1.04%
👍
11
0.954%
⚡
10
0.867%
👨💻
10
0.867%
🎄
7
0.607%
👀
5
0.434%
👏
4
0.347%
🤣
3
0.26%
🗿
2
0.173%
👎
1
0.087%
1 further kind
1
0.087%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 28 of the 29 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 1,153 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 16 July 2026 to 9 November 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
Telegram’s own ‘edited’ marker: 2 of 10 posts held from the last 30 days (20.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Last call на сердечки
Можем бесконечно рассказывать, за что любим КРОК. Задачи, путешествия, спорт, коллеги, с которыми не страшно и в поход, и на важную презентацию...
😉 В двух словах и не опишешь, а одним голосом — проще. До 14 ноября еще можно проголосовать за КРОК в рейтинге работодателей HeadHunter.
Вы нам сердечко, а мы вам💚
Мы не слышим хруста безе осенних листьев 😔
Значит, продлеваем осень, несмотря на снег за окном!
Делимся, как прошел HalloWin/Win: в этот день проверяли магию миндальной связи между кроковцами и атмосферно избавлялись от страхов и сомнений, ныряя в детокс-бассейн 🎃
Готовы оценить самые эффектные прыжки?
❤️🔥 — 10/10 за артистизм и технику
🙈 Для тех, кого не съела тыква
Перекличка тех, кто готов к новым челленджам — например, проектам, задачам со звездочкой и будням с драйвовыми коллегами.
Собрали топ вакансий КРОК этого месяца 👇
Аналитика
➡️ Руководитель команды аналитиков
➡️ Ведущий аналитик 1C:ЗУП
➡️ Ведущий аналитик по внедрению (BPM, CRM)
Бизнес-приложения
➡️ Функциональный архитектор 1C:ЗУП
➡️ Руководитель проектов 1С
➡️ Технический менеджер п…
🤩#пятничные_котики расширяют штат?
Перемены, которые мы одобряем: сегодня забываем про мурчание — и снимаем стресс собачьей непосредственностью.
По традиции ждем фото твоего пушистого коллеги в комментах 👇
🗒 Меняем хандру на журналы
Нашли способ пережить серые дни: ищем краски в запылившемся глянце и собираем из него личные истории — в коллажах.
Маша, контент-лид команды бренда работодателя, провела мастер-класс для коллег. Пара часов, ножницы, клей — и все с головой ушли в креатив.
Что у нас получилось — смотри в видео.
💚 — если теперь знаешь, чем займешься вечером.
⌨️ Объявляем всеобщий дебаг литературы
23–24 октября везем комьюнити Read IT Club на HolyJS 2026 Autumn. Если тоже будешь на конференции, заглядывай на наш стенд:
🟢 проверить, насколько глаз наметан на баги в переводах
🟢 узнать, как (и зачем) айтишники становятся рецензентами ИТ-литературы
🟢 сделать прогноз о будущем разработки — и свериться с коллегами
А в пятницу проведем опен-толк «ИИ: конкурент или коллега? Вз…
⚡️Видеть за задачами больше — тоже скилл
В КРОК есть департамент внутренней автоматизации — наш мозг и помощник во всех процессах. Коллеги знают, как сократить рутину и сделать работу над проектами быстрее и проще с помощью технологий.
❤️❤️❤️❤️
❤️❤️❤️❤️Сегодня в
❤️❤️❤️❤️#random_coffee —
❤️❤️❤️ Марина Конова
Обсудили с нашим ИТ-директором:
🟢как не делать автоматизацию ради автоматизации
🟢что помогает команде …
❤️ А смысл жда-а-а-а-а-а-а-а-а-ть
...повода зайти в бар Вани Дмитриенко?
Летом у КРОК появилась своя точка притяжения вне офиса — законнектились с Орбитой в честь ДР компании.
Как родилась наша звездная коллаба с вечеринками и даже собственным спешл-меню — рассказываем в карточках⬆️
А попробовать КРОК на вкус в Орбите можно до декабря. Ни на что не намекаем...
👀Давайте не будем им мешать — и просто понаблюдаем...
В мире отдыхающих можно встретить множество видов: от цифровых детоксеров до тех, кто ловко жонглирует открытыми вкладками не отходя от бассейна.
Самых распространенных собрали в одном ролике⬆️
😁9❤🔥5🤣3
Showing the 12 most recent of 29 posts we hold for @crocteam. 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.
Posts edited after publishing
@crocteam edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
10 November 2026
Most recent edit
10 November 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 4 registered channels — 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.
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.
Appears in Telegram’s recommendations for other channels
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.
2ГИС Команда @team2gis · 43,085 Telegram ranks this channel #23 of 90 here — alongside 89 others — read 27 August 2026
ИТ-Пикник @IT_picnic · 22,795 Telegram ranks this channel #34 of 94 here — alongside 93 others — read 18 September 2026
Школа 21 @school21sber · 53,416 Telegram ranks this channel #52 of 94 here — alongside 93 others — read 19 August 2026
Альфа-Будущее @alfafuture · 52,252 Telegram ranks this channel #60 of 99 here — alongside 98 others — read 26 August 2026
Карьера в Альфа-Банке @alfabank_career · 24,936 Telegram ranks this channel #62 of 95 here — alongside 94 others — read 15 September 2026
Ozon Team @ozonteam · 23,488 Telegram ranks this channel #74 of 89 here — alongside 88 others — read 19 September 2026
Карьера в ВТБ @vtb_career · 80,377 Telegram ranks this channel #76 of 93 here — alongside 92 others — read 23 August 2026
Карьера в Сбере! @careersber · 134,122 Telegram ranks this channel #78 of 96 here — alongside 95 others — read 13 August 2026
МТС Банк | Карьера @mtsbankcareer · 30,395 Telegram ranks this channel #79 of 99 here — alongside 98 others — read 7 September 2026
Changellenge >> @changellenge · 48,961 Telegram ranks this channel #79 of 99 here — alongside 98 others — read 29 August 2026
Ozon Camp @ozoncamp · 28,776 Telegram ranks this channel #81 of 97 here — alongside 96 others — read 10 September 2026
Ozon Tech @ozon_tech · 30,189 Telegram ranks this channel #86 of 98 here — alongside 97 others — read 8 September 2026
FutureToday @futru · 36,467 Telegram ranks this channel #93 of 99 here — alongside 98 others — read 2 September 2026
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 November 2026 — this
entry's latest reading, not the date you are reading this.
“CROC Team” (@crocteam), 7,165 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/crocteam.
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.