FRONTEND P.A.S.S. новый проект от команды INFLOW Закрытый канал с позициями для Frontend Developer 51 компания | Публикуется от 6 до 10 вакансий в день Публикуются запросы на удаленку BY/RU/EUR/GLOBAL Так же есть вакансии с релокацией в Европу / ЮВ Азию Вакансии для специалистов с грейдами MID/SENIOR В основном позиции по стеку для REACT/VUE/ANGULAR ПРИСОЕДИНИТЬСЯ ПО ПОДПИСКЕ

Channel
IT Relocation (Inflow)
@Relocats
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
32,912subscribers
+490 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001136736785 |
|---|---|
| Type | Channel |
| Username | @Relocats |
| Description | Канал с вакансиями от IT компаний предлагающих переезд и релокацию из России, Украины и стран СНГ за границу. ✅ По вопросам рекламы, вп и публикации вакансий: @courierus РКН: 5364819306 |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 36 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/Relocats |
Topic
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 9 September 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 13:38 | 32,912 | +133 |
| 19 Sept 2026, 04:39 | 32,779 | +25 |
| 16 Sept 2026, 20:40 | 32,754 | +35 |
| 14 Sept 2026, 20:01 | 32,719 | +15 |
| 13 Sept 2026, 09:57 | 32,704 | +10 |
| 11 Sept 2026, 14:58 | 32,694 | +46 |
| 9 Sept 2026, 01:40 | 32,648 | +7 |
| 5 Sept 2026, 19:38 | 32,641 | +10 |
| 3 Sept 2026, 15:21 | 32,631 | +23 |
| 2 Sept 2026, 07:04 | 32,608 | -7 |
| 1 Sept 2026, 07:59 | 32,615 | +15 |
| 31 Aug 2026, 05:55 | 32,600 | +1 |
| 30 Aug 2026, 06:23 | 32,599 | +5 |
| 29 Aug 2026, 05:13 | 32,594 | +21 |
| 28 Aug 2026, 05:04 | 32,573 | +9 |
| 27 Aug 2026, 05:24 | 32,564 | +8 |
| 26 Aug 2026, 08:43 | 32,556 | +8 |
| 25 Aug 2026, 07:42 | 32,548 | +2 |
| 24 Aug 2026, 04:58 | 32,546 | +5 |
| 22 Aug 2026, 10:13 | 32,541 | first reading |
Engagement
116 posts held, back to 30 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 103 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.07%
- avg views ÷ 32,912 subscribers
- Avg views / post
- 2,650
- 59 posts measured
- Reaction rate
- 0.019%
- reactions ÷ views · ER floor
- Posts in window
- 59
- of 116 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 11 of 59 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 116 (30 July 2026 – 27 September 2026) |
| Views total | 156,608 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 08:33 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
- ≈503
- Videos
- ≈16
- Links
- ≈4,360
Lifetime counters from Telegram’s own channel header, read 27 September 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
- 24s
- Average length
- 24s
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
43 reactions across 11 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 43 | 100.0% |
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 116 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 116 most recent posts we hold, published 30 July 2026 to 27 September 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.
Advertising
- Ad load
- 2.59%
- 3 of 116 posts carry an ad marker
- Regulatory tokens
- 3
- posts carrying an erid · 3 distinct tokens
- Median views · ads
- 2,390
- over 3 measured posts
- Median views · rest
- 2,710
- over 113 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFGjBVC5 | 1 | 24 August 2026 | 24 August 2026 |
| 2W5zFH3BnqX | 1 | 23 September 2026 | 23 September 2026 |
| 2W5zFH7o8eM | 1 | 18 August 2026 | 18 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 116 most recent posts we hold, published 30 July 2026 to 27 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
SENIOR SOFTWARE ENGINEER (PYTHON) | REMOTE GLOBAL OR RELOCATION TO KZ/GE/RS/CY | PLATA #remote #or #relocation #fulltime #itjob #python https://teletype.in/@remoteit/kcQACZQhmwz
AUTOMATION ENGINEER | RELOACTION TO MEXICO | PLATA CARD #relocation to #mexico #fulltime #itjob #automation https://teletype.in/@remoteit/8o-6iP25_B9
Posted without readable text
MIDDLE BUSINESS ANALYST | RELOCATION TO MEXICO | PLATA CARD #relocation to #mexico #fulltime #itjob #analyst #business https://telegra.ph/Business-Analyst-Middle-Compliance-09-25
Posted without readable text
Technical Business Assistant / R&D / Growth Operations | REMOTE GLOBAL | #remote #fulltime #itjob https://teletype.in/@remoteit/257yzMe8KFJ
FRONTEND P.A.S.S. новый проект от команды INFLOW Закрытый канал с позициями для Frontend Developer За несколько дней более 30 вакансий от 26 компаний Публикуются запросы на удаленку BY/RU/EUR/GLOBAL Так же есть вакансии с релокацией в Европу / ЮВ Азию Вакансии для специалистов с грейдами MID/SENIOR В основном позиции по стеку для REACT/VUE/ANGULAR ПРИСОЕДИНИТЬСЯ ПО ПОДПИСКЕ
SENIOR BACKEND DEVELOPER (GOLANG) | REMOTE GLOBAL OR RELOCATION TO AM/GE/PL/RS/SPAIN | TABBY #remote #relocation #fulltime #itjob #backend #golang https://teletype.in/@remoteit/qbsX0Y8Zgf2
SENIOR BACKEND DEVELOPER (PYTHON) | REMOTE EU/CY/CENTRAL ASIA OR RELOCATION TO UAE | ELIXI #remote or #relocation #fulltime #itjob #backend #python https://teletype.in/@remoteit/3F8q54lNqG2
Оффер 427 000₽ на руки в Сбер и отказались Оффер 380 000₽ на руки в банк Оффер 6 800$ net с релокацией на Кипр Оффер 4 500$ в американскую компанию 👆Это недавние результаты участников нашего комьюнити. Меня зовут Тихон - я действующий разработчик и ментор. Уже 2 года я развиваю комьюнити, где 300+ разработчиков, и вместе мы выжимаем из рынка максимум! В нашем канале много ценного для разработчиков по подготовке к …
SENIOR BACKEND DEVELOPER | RELOCATION TO CY/GE OR HYBRID THERE | TRADING VIEW #relocation to #cy #ge #fulltime #itjob #backend #go #java https://teletype.in/@remoteit/p46YiYcGEAF
Showing the 12 most recent of 116 posts we hold for @Relocats. 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.
Forward network
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.
Mentions
Named by 14 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.
@Cvflow · 6,9496 postsRemote IT (Inflow)
@Remoteit · 50,9764 postsJob Moscow it (Inflow)
@itmoscow · 2,6662 postsJob Nsk it (Inflow)
@nskoffice · 7972 postsRemote Junior (INFLOW)
@remotejun · 26,6172 postsAbout IT
@about_it_tg · 1321 postIT Личный Бренд | Денис Матвеев
@dmatew · 5431 postGamedev Jobs (Inflow)
@Gamedevjobs · 21,5791 postGlobal Outstaff (Inflow)
@goutstaff · 1,8811 postРаботница
@jobfeeds · 3,3091 postSilicon Bangalore
@silicon_bangalore · 1,2081 postJob SPB it (Inflow)
@spboffice · 2,0771 postWeb 3 games (Inflow)
@web33games · 1911 postWEB3 TECH | INFLOW
@WEB3OTECH · 6311 post
Names
Channels on the register whose handles appear in this channel's posts.
@tribute · 1,796,2954 postsIT CV (Inflow)
@Cvflow · 6,9492 postsD2C powered by Xsolla
@d2cgames · 1,4521 postКрасильников Данил
@danikrass · 9291 postFACTS RA
@factsra · 2251 postLink Jobs (Inflow)
@fromlinked · 1,1021 postGamedev Chat (inflow)
@gamedevchat · 1,5791 postGamedev Jobs (Inflow)
@Gamedevjobs · 21,5791 postGlobal Outstaff (Inflow)
@goutstaff · 1,8811 postJob Moscow it (Inflow)
@itmoscow · 2,6661 post1С Резюме и вакансии (inflow)
@job41c · 1901 postРаботница
@jobfeeds · 3,3091 postJob Nsk it (Inflow)
@nskoffice · 7971 postRemote IT (Inflow)
@Remoteit · 50,9761 postRemote Junior (INFLOW)
@remotejun · 26,6171 postJob SPB it (Inflow)
@spboffice · 2,0771 postWEB3 MARKETING|INFLOW
@web3marke · 1961 postWEB3 TECH | INFLOW
@WEB3OTECH · 6311 post
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@Remoteit · 50,976#1
@evacuatejobs · 135,997#2
@zarubezhom_jobs · 103,632#3
@young_relocate · 52,010#4
@remote_jobs_relocate · 33,002#5
@dev_connectablejobs · 27,959#6
@choicy_work · 27,100#7
@youritjob · 37,523#8
@opento_dev · 10,030#9
@web30job · 6,855#10
@it_vakansii_jobs · 95,470#11
@Cvflow · 6,949#12
@remotegeekjob · 25,220#13
@jobfeeds · 3,309#14
@jobs_abroad · 15,554#15
@e_ngineers · 3,688#16
@job_web3 · 10,789#17
@devs_it · 18,741#18
@jobfortm · 15,037#19
@relocationdev · 23,875#20
@hiddengurus · 8,830#21
@workingincrypto · 27,998#22
@Gamedevjobs · 21,579#23
@itmoscow · 2,666#24
@relocation_vacancies · 10,721#25
@spboffice · 2,077#26
@Getitrussia · 21,091#27
@remote · 17,993#28
@g_jobchannel · 18,874#29
@itjobs_nocode · 8,970#30
@hr_itwork · 11,053#31
@rusukrjobs · 25,643#32
@it_vacancy_relocation · 18,614#33
@top_rel · 2,299#34
@heddoworld · 5,138#35
@montenegro_it_jobs · 6,097#36
@jobs_in_it_remoute · 7,929#37
@job_for_relocation · 15,013#38
@yuniorapp · 61,784#39
@young_june · 74,485#40
@careerspace · 163,712#41
@jobbynimoff · 1,357#42
@ru_pythonjobs · 9,994#43
@cryptoDevJobs · 3,790#44
@agilefluent · 46,131#45
@putderzhim · 1,299#46
@hellonewjob · 13,919#47
@headzio · 4,621#48
@jc_it · 15,731#49
@DarikaINITVacancies · 7,546#50
@JScript_jobs · 12,418#51
@hrexpert63_vacancies · 3,578#52
@juniors_rabota_jobs · 68,152#53
@proglibrary · 78,288#54
@job_react · 16,169#55
@datajobschannel · 12,272#56
@uzdev_jobs · 26,052#57
@jsdevjob · 9,533#58
@datasciencejobs · 22,137#59
@cchellowork · 24,757#60
@remotejobss · 159,925#61
@geekjobs · 50,783#62
@remotejun · 26,617#63
@backend_frontend_jobs · 9,868#64
@indiehackers31337 · 2,163#65
@forfrontend · 13,450#66
@relocateme · 34,269#67
@forproducts · 69,619#68
@kyrillic · 60,982#69
@forchiefs · 38,424#70
@jobforjunior · 85,036#71
@remotejobshg · 33,019#72
@cryptoMjob · 3,767#73
@hrlunapark · 20,296#74
@across_english · 8,026#75
@habr_career · 33,171#76
@gdjobs · 15,888#77
@denissexy · 137,325#78
@tproger · 78,305#79
@vcnews · 112,033#80
@habr_com · 132,465#81
@jaabz_com · 14,200#82
@foranalysts · 36,643#83
@forpython · 7,356#84
@opento_data · 7,315#85
@Remote_Software_Developer_Jobs · 26,539#86
@products_jobs_projects · 7,596#87
@yurydud · 862,341#88
@addmeto · 71,835#89
@ProGeorgian · 118,706#90
@movetoeuropetech · 5,335#91
@forgoandrust · 4,409#92
Read from Telegram’s recommendation API, most recently 5 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@Remoteit · 50,976
Telegram ranks this channel #1 of 95 here — alongside 94 others — read 25 August 2026
@choicy_work · 27,100
Telegram ranks this channel #5 of 95 here — alongside 94 others — read 11 September 2026
@remote_jobs_relocate · 33,002
Telegram ranks this channel #5 of 95 here — alongside 94 others — read 5 September 2026
@Getitrussia · 21,091
Telegram ranks this channel #7 of 97 here — alongside 96 others — read 24 September 2026
@relocationdev · 23,875
Telegram ranks this channel #7 of 89 here — alongside 88 others — read 17 September 2026
@youritjob · 37,523
Telegram ranks this channel #7 of 86 here — alongside 85 others — read 1 September 2026
@young_relocate · 52,010
Telegram ranks this channel #8 of 97 here — alongside 96 others — read 25 August 2026
@evacuatejobs · 135,997
Telegram ranks this channel #11 of 93 here — alongside 92 others — read 13 August 2026
@remotegeekjob · 25,220
Telegram ranks this channel #17 of 97 here — alongside 96 others — read 14 September 2026
@workingincrypto · 27,998
Telegram ranks this channel #18 of 89 here — alongside 88 others — read 10 September 2026
@relocateme · 34,269
Telegram ranks this channel #21 of 89 here — alongside 88 others — read 3 September 2026
@cchellowork · 24,757
Telegram ranks this channel #25 of 92 here — alongside 91 others — read 15 September 2026
@rusukrjobs · 25,643
Telegram ranks this channel #25 of 95 here — alongside 94 others — read 14 September 2026
@Gamedevjobs · 21,579
Telegram ranks this channel #27 of 96 here — alongside 95 others — read 23 September 2026
@itfreelancers · 25,645
Telegram ranks this channel #30 of 92 here — alongside 91 others — read 14 September 2026
@zarubezhom_jobs · 103,632
Telegram ranks this channel #30 of 94 here — alongside 93 others — read 15 August 2026
@remotejobshg · 33,019
Telegram ranks this channel #32 of 83 here — alongside 82 others — read 4 September 2026
@agilefluent · 46,131
Telegram ranks this channel #32 of 95 here — alongside 94 others — read 28 August 2026
@dev_connectablejobs · 27,959
Telegram ranks this channel #36 of 94 here — alongside 93 others — read 10 September 2026
@remotejobss · 159,925
Telegram ranks this channel #36 of 98 here — alongside 97 others — read 12 August 2026
@vakansii_it · 27,497
Telegram ranks this channel #41 of 88 here — alongside 87 others — read 10 September 2026
@runello_rus_webdevelopment · 24,092
Telegram ranks this channel #42 of 93 here — alongside 92 others — read 17 September 2026
@remotejun · 26,617
Telegram ranks this channel #48 of 98 here — alongside 97 others — read 12 September 2026
@Remote_Software_Developer_Jobs · 26,539
Telegram ranks this channel #55 of 96 here — alongside 95 others — read 12 September 2026
This channel appears in 31 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“IT Relocation (Inflow)” (@Relocats), 32,912 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Relocats.
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.