Telegram RegisterThe public register of Telegram

Channel

Вакансии в iGaming: Сербия и удалёнка. LENKEP

@igaming_lenkep

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

2,396subscribers

+34 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003395657531
TypeChannel
Username@igaming_lenkep
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/igaming_lenkep

Topic

Job listings — 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 3 other registered channels. They sit inside a group of 8 channels that share the same post bodies with each other. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@igaming_lenkep/135 · this entry22 Jul 2026, 10:19 UTC@opento_igaming/9816 Aug 2026, 12:01 UTC1.0015 days
@opento_igaming/9611 Aug 2026, 10:00 UTC@igaming_lenkep/147 · this entry1 Aug 2026, 11:03 UTC1.0062 minutes
@igaming_lenkep/152 · this entry4 Aug 2026, 13:01 UTC@opento_igaming/9694 Aug 2026, 13:01 UTC1.00under a minute
@opento_igaming/9664 Aug 2026, 11:03 UTC@igaming_lenkep/153 · this entry5 Aug 2026, 09:01 UTC1.0022 hours
@opento_igaming/9745 Aug 2026, 13:00 UTC@igaming_lenkep/154 · this entry6 Aug 2026, 09:02 UTC1.0020 hours
@opento_igaming/9826 Aug 2026, 13:54 UTC@igaming_lenkep/155 · this entry7 Aug 2026, 09:03 UTC1.0019 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@opento_igaming6 (6/6 hand-verifiable sample passed)1.0020 hours@opento_igaming (51)
@IT_iGaming6 (6/6 hand-verifiable sample passed)1.0072 secondsthis entry (42)
@youritjob5 (5/5 hand-verifiable sample passed)1.0049 minutes@youritjob (32)

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. 3 of the 9 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 21 comparable posts for this entry, running 21 July 2026 to 7 August 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 8, the earliest publisher we hold is @igaming_lenkep — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 8 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 7 other registered channels, 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

2,3622,3962,3796 August 2026 — 2,362 subscribers7 August 2026 — 2,368 subscribers10 August 2026 — 2,378 subscribers13 August 2026 — 2,396 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +34. 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 2,357–2,401 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:582,396+18
10 Aug 2026, 13:332,378+10
7 Aug 2026, 13:382,368+6
6 Aug 2026, 16:062,362first reading

Engagement

21 posts held, back to 21 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
37.1%
avg views ÷ 2,396 subscribers
Avg views / post
888
21 posts measured
Reaction rate
0.125%
reactions ÷ views · ER floor
Posts in window
21
of 21 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. It is computed over the 15 of 21 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held21 (21 July 20267 August 2026)
Views total18,655
Reactions total17
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:37 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.

Reaction mix

17 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 70.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1270.6%
🔥423.5%
👍15.88%

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 21 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 17reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 21 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.

Recent posts

7 Aug 2026, 09:03 UTC339 views2 reactionsread 7 August 2026

Привет! Мы снова в поиске Sales Manager в нашу команду LENKEP Recruitment 💖 Мы — международное рекрутинговое агентство, которое помогает компаниям из сфер Crypto, FinTech, iGaming, Affiliate и High-Risk находить лучших специалистов по всему миру. Сейчас мы ищем человека, который поможет нам развивать новые партнерства, выстраивать долгосрочные отношения с клиентами и масштабировать бизнес. 📌 Что будет входить в тв

1🔥1

6 Aug 2026, 09:02 UTC483 viewsread 7 August 2026

CMO / Head of Marketing in iGaming Ищем сильного CMO / Head of Marketing с подтвержденным опытом в iGaming и работой на зарубежных гео. 🟣Основные задачи: — Разработка и реализация маркетинговой стратегии по целевым GEO; — Управление репутацией бренда, работа с негативом и кризисными ситуациями; — Поиск, тестирование и внедрение нестандартных каналов привлечения трафика; — Планирование, контроль и оптимизация маркет

5 Aug 2026, 09:01 UTC584 views0 reactionsread 7 August 2026

Alfaleads Network ищет Senior Business Development Manager Чем предстоит заниматься: — Развивать и расширять текущую базу рекламодателей — Выполнять план продаж и увеличивать объемы сотрудничества с партнерами — Анализировать рынок и находить новые возможности для развития бизнеса Ключевые требования: — Опыт работы в вертикали iGaming от 2 лет — Опыт работы с международным рынком и уверенный английский язык — Опыт

4 Aug 2026, 13:01 UTC625 views2 reactionsread 7 August 2026
Photo

🔔 Важно: войс-чат с Сашей Флинтом переносится К сожалению, гость нашего эфира заболел. Мы желаем Саше как можно скорее восстановиться и вернуться в строй! Войс-чат не отменяем — просто переносим на другую дату, которую обязательно анонсируем позже. Следите за обновлениями 💚

1👍1

4 Aug 2026, 10:52 UTC634 views4 reactionsread 7 August 2026

Executive Assistant для CEO | Белград Мы — LENKEP, рекрутинговое агентство с 7+ годами опыта в подборе специалистов в iGaming, Fintech, Crypto и Gamedev. Сейчас мы растём и ищем Executive Assistant для нашей CEO — ищем надёжного человека, который освободит руководителя от рутинных задачек. Чем предстоит заниматься: 🌸Вести календарь, фильтровать входящие сообщения, держать приоритеты 🌸Брать на себя личные и семейны

4

3 Aug 2026, 10:47 UTC552 viewsread 7 August 2026
Forwarded from @IT_iGaming

Senior Backend Developer Spinsoft Gaming, Remote or hybrid Belgrade We are developing online slot games and table casino games similar to the market leaders in the industry. We are looking for an experienced Senior Backend Developer to design and build the back-office platform that powers our games. Responsibilities: — Design and develop a backend platform for game administration — Build and maintain an admin pane

1 Aug 2026, 11:03 UTC807 views2 reactionsread 7 August 2026
Photo

⚡️ Разговор без NDA: Саша Флинт про SEO, AI и найм ⚡️ LENKEP продолжает говорить с людьми, которые строят индустрию изнутри. На этот раз разбираем SEO, AI, найм и развитие команд вместе с одним из самых известных экспертов рынка. 4 августа в 17:00 CET / 18:00 GMT+3 у нас в эфире — Саша Флинт, CEO Flint Group 🔥 На войс-чате в канале «Арбитраж. Все вакансии в одном месте» обсудим: 🟥 Как Саша пришел в SEO и почему у

🔥2

31 Jul 2026, 09:00 UTC864 viewsread 7 August 2026

Business Development Manager (Middle+/Senior) Мы — международный iGaming Game Provider. Сейчас активно масштабирует коммерческое направление: уже разработано 20+ игр и есть интеграции с крупными игроками рынка! Чем предстоит заниматься? — Поиск потенциальных партнеров; — Холодный аутрич; — Проведение переговоров; — Проведение демо продукта; — Согласование коммерческих условий; — Подписание договора; — Сопровождени

30 Jul 2026, 11:38 UTC846 views1 reactionsread 7 August 2026

Chief Marketing Officer Remote Мы — международная продуктовая IT-компания, которая создает технологические решения в сфере автоматизированной торговли на финансовых рынках. Наши продукты помогают пользователям автоматизировать процесс трейдинга, используя алгоритмы, аналитику и современные технологии. Мы ищем CMO, который возглавит маркетинговое направление компании, будет отвечать за рост ключевых бизнес-метрик и

1

29 Jul 2026, 09:00 UTC961 views1 reactionsread 7 August 2026

Менеджер службы поддержки (iGaming) | Удаленная работа Хотите работать в международной компании и стать частью одной из самых динамичных отраслей? Тогда мы ищем именно вас! Мы ищем менеджера службы поддержки, который станет надежной опорой для наших пользователей и поможет создать сервис высочайшего уровня. Ваши обязанности: — Общение с пользователями в онлайн-чате и по электронной почте. — Помощь с регистрацией,

1

28 Jul 2026, 15:05 UTC943 views0 reactionsread 7 August 2026
Photo

🔥 Сербия — мощный хаб для iGaming, FinTech и Affiliate В Белграде активно развиваются арбитражные команды, но ими все не ограничивается: Сербию также выбирают Яндекс, Plata и другие крупные компании. Сегодня это одно из главных направлений для бизнеса, который хочет развиваться на международном рынке и при этом сохранять адекватный уровень расходов. Но остается ключевой вопрос: Насколько Сербия подходит IT-, iGami

28 Jul 2026, 09:04 UTC943 views0 reactionsread 7 August 2026

Ищем Senior Customer Support Team Lead 📍 Локация: Белград, Сербия (гибридный формат работы) В международную iGaming-команду ищем опытного Senior Customer Support Team Lead, который сможет эффективно управлять командой, развивать сотрудников и обеспечивать высокий уровень клиентского сервиса. Что предстоит делать: — Руководить командой Customer Support Agents — Развивать и мотивировать сотрудников, проводить 1:1 и

Showing the 12 most recent of 21 posts we hold for @igaming_lenkep. 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 — 1,326,976 of 1,480,688entries 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 2 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.

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

“Вакансии в iGaming: Сербия и удалёнка. LENKEP” (@igaming_lenkep), 2,396 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/igaming_lenkep.

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.