Telegram RegisterThe public register of Telegram
Telegram profile photo for Поиск | NGS.RU | Работа Новосибирск

Channel

Поиск | NGS.RU | Работа Новосибирск

@poisk_nsk

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry

10,012subscribers

-106 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002448240382
TypeChannel
Username@poisk_nsk
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/poisk_nsk

Topic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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

10,01210,11810,0656 August 2026 — 10,118 subscribers6 August 2026 — 10,118 subscribers7 August 2026 — 10,112 subscribers8 August 2026 — 10,106 subscribers9 August 2026 — 10,097 subscribers11 August 2026 — 10,094 subscribers13 August 2026 — 10,093 subscribers15 August 2026 — 10,086 subscribers16 August 2026 — 10,084 subscribers19 August 2026 — 10,087 subscribers21 August 2026 — 10,086 subscribers24 August 2026 — 10,080 subscribers25 August 2026 — 10,071 subscribers26 August 2026 — 10,065 subscribers27 August 2026 — 10,058 subscribers28 August 2026 — 10,062 subscribers29 August 2026 — 10,056 subscribers30 August 2026 — 10,057 subscribers1 September 2026 — 10,049 subscribers3 September 2026 — 10,055 subscribers5 September 2026 — 10,054 subscribers8 September 2026 — 10,042 subscribers11 September 2026 — 10,032 subscribers13 September 2026 — 10,026 subscribers14 September 2026 — 10,021 subscribers18 September 2026 — 10,012 subscribers6 August 202618 September 2026
26 measurements spanning 43 days, net -106. 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 9,996–10,134 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
18 Sept 2026, 18:1810,012-9
14 Sept 2026, 17:3910,021-5
13 Sept 2026, 06:1610,026-6
11 Sept 2026, 06:3710,032-10
8 Sept 2026, 13:1710,042-12
5 Sept 2026, 05:5710,054-1
3 Sept 2026, 09:2310,055+6
1 Sept 2026, 05:5510,049-8
30 Aug 2026, 07:3310,057+1
29 Aug 2026, 05:1210,056-6
28 Aug 2026, 02:2410,062+4
27 Aug 2026, 03:0810,058-7
26 Aug 2026, 05:0410,065-6
25 Aug 2026, 06:4210,071-9
24 Aug 2026, 04:1810,080-6
21 Aug 2026, 00:5410,086-1
19 Aug 2026, 22:3810,087+3
16 Aug 2026, 15:1410,084-2
15 Aug 2026, 01:5510,086-7
13 Aug 2026, 16:0610,093first reading

Engagement

201 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.57%
avg views ÷ 10,012 subscribers
Avg views / post
558
33 posts measured
Reaction rate
0.169%
reactions ÷ views · ER floor
Posts in window
33
of 201 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 8 of 33 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 29 August 2026
Posts held201 (5 August 202629 August 2026)
Views total18,412
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 04:06 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

Video runtime
18m 28s
Average length
1m 09s

Measured directly from 16 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

112 reactions across 46 posts, in 18 distinct kinds. The most used accounts for 38.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4338.4%
👍1412.5%
👀98.04%
🤩76.25%
👎54.46%
🔥43.57%
🤡43.57%
👏32.68%
💔32.68%
😁32.68%
🙈32.68%
🤣32.68%
🤯32.68%
😐21.79%
😢21.79%
😭21.79%
💯10.893%
🤔10.893%

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

Measured over the 201 most recent posts we hold, published 5 August 2026 to 29 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.

Advertising

Ad load
0.498%
1 of 201 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
310
over 1 measured post
Median views · rest
287
over 200 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2SDnjeffurs113 August 202613 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 201 most recent posts we hold, published 5 August 2026 to 29 August 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

29 Aug 2026, 03:01 UTC60 viewsread 29 August 2026
Photo

Даже если действительно любишь свою работу, что-то в ней всегда будет раздражать. Представьте: вы разработали уникальный маршрут по городу, отказались от других заказов, а за день до старта группа «сливается». Или приходят 50 человек вместо 20. Вот экскурсоводу из Самары даже не нужно представлять. О сложностях своей работы он рассказал нашим коллегам из @news63ru. Узнали себя в рассказе гида? ❤️— да, стало стыдн

28 Aug 2026, 17:01 UTC155 viewsread 29 August 2026
Video

А ты всего лишь заходил за кофе… ⏹️ Больше про работу здесь

28 Aug 2026, 09:04 UTC234 viewsread 29 August 2026
Photo

Подборка вакансий для водителей ⤵️ Водитель дальнобойщик 150 000 — 220 000 ₽ Водитель категории С 100 000 – 113 000 ₽ за месяц, до вычета налогов Водитель-экспедитор категории Е 80 000 – 140 000 ₽ за месяц, на руки Водитель категории С, Е 180 000 – 300 000 ₽ за месяц, до вычета налогов Водитель на бензовоз График 4/4. Работа по городу От 100 000 ₽ Водитель категории С 150 000 ₽ за месяц, на руки Водитель-экспе

28 Aug 2026, 06:21 UTC262 views2 reactionsread 29 August 2026
Photo

Вакансия с бесплатным просмотром кино 😺 Контролера билетов ищут в «Побeде». Зарплата от 30 000 ₽. Но на совмещение с учебой никого не возьмут. Час работы стоит 130₽ чaс + прeмия за пocещaeмоcть, в сpeднем выходит 150 чaсов в меcяц. Гpафик cмeнный, плавaющий, пo 10-12 чаcoв в дeнь (у вcех еcть утpeнние, дневныe и нoчные смeны). Помимо контроля билетов, надо будет помогать гостям размещаться в залы, контролировать

2

28 Aug 2026, 05:03 UTC219 views3 reactionsread 29 August 2026
Photo

У вас есть на работе КЭДО? 👍 — Да 👀 — Нет У многих сейчас практикуют электронный документооборот, но не все знают, как это работает на практике. Разбираем в карточках все нюансы КЭДО: как его внедрять, какие документы можно подписывать электронно, а какие требуют бумажной версии и многое другое. ⏹️ Подпишись на @poisk_nsk

👍3

28 Aug 2026, 04:02 UTC215 viewsread 28 August 2026
Photo

Подборка вакансий для админов 📋 Администратор в автосервис 🚩50 000 – 55 000 ₽ за месяц Администратор зала в суши-бар Рыба.Рис 🚩от 48 000 ₽ за месяц, на руки Администратор салона красоты 🚩85 000 – 95 000 ₽ за месяц, на руки Администратор в магазин одежды (ТЦ Сан Сити) 🚩79 000 — 90 000 ₽ Администратор-управляющий сменой в топовые салоны 🚩45 000 — 65 000 ₽ на руки Администратор в салон красоты 🚩50 000 — 100 000 ₽

28 Aug 2026, 01:33 UTC247 views1 reactionsread 28 August 2026
Photo

Когда нервы к концу рабочей недели уже на пределе, а Excel решил тебя добить... 😭 — Да, было ⏹️ Подпишись на @poisk_nsk

😭1

27 Aug 2026, 17:02 UTC281 viewsread 28 August 2026
Photo

Вакансии для крутых удаленщиков в Санкт-Петербурге ❤️ ▫️HR-менеджер Зарплата: от 70 000 до 90 000 ₽ за месяц 🚩Опыт работы: 1–3 года ▫️Тимлид команды писателей базы знаний Зарплата: от 120 000 ₽ за месяц 🚩Опыт работы: 1–3 года ▫️Дизайнер инфографики Зарплата: от 70 000 до 100 000 ₽ за месяц 🚩Опыт работы: 1–3 года ▫️Архитектор-проектировщик Зарплата: от 100 000 ₽ за месяц 🚩Опыт работы: 3–6 лет ▫️Python-разработчик

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

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.

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

“Поиск | NGS.RU | Работа Новосибирск” (@poisk_nsk), 10,012 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/poisk_nsk.

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.