Telegram RegisterThe public register of Telegram
Telegram profile photo for ЧП Нижневартовск. Происшествия

Channel

ЧП Нижневартовск. Происшествия

@nizhnevartovsk_chp

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

63,390subscribers

-198 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-1001408433856
TypeChannel
Username@nizhnevartovsk_chp
Description✅ Официальный канал ЧП Нижневартовск ❗️По всем вопросам 👉 @chp_86 ЧП Сургут - @surgut_chp ЧП Когалым - @kogalim_chp ЧП Ханты-Мансийск - @hanti_mansiysk_chp Реклама: https://telega.in/c/nizhnevartovsk_chp № 4923301287 #JSM0Y
Created7 January 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/nizhnevartovsk_chp

Topic

Local community — 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 21 August 2026 and assigned it the closest of 31 fixed categories, at 72% 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.

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 in near-verbatim form on 3 other registered channels. 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
@nizhnevartovsk_chp/71917 · this entry10 Oct 2026, 17:00 UTC@surgut_chp/5312910 Oct 2026, 17:02 UTC0.9772 seconds
@nizhnevartovsk_chp/73222 · this entry16 Nov 2026, 13:20 UTC@surgut_chp/5444816 Nov 2026, 13:21 UTC0.9572 seconds
@nizhnevartovsk_chp/70457 · this entry31 Aug 2026, 17:30 UTC@surgut_chp/5129831 Aug 2026, 17:31 UTC0.95under a minute
@nizhnevartovsk_chp/73143 · this entry15 Nov 2026, 04:59 UTC@surgut_chp/5438915 Nov 2026, 05:08 UTC0.959 minutes
@nizhnevartovsk_chp/72254 · this entry20 Oct 2026, 10:48 UTC@surgut_chp/5350921 Oct 2026, 04:24 UTC0.9518 hours
@nizhnevartovsk_chp/72319 · this entry22 Oct 2026, 10:24 UTC@surgut_chp/5363423 Oct 2026, 10:15 UTC0.9324 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@surgut_chp27 (8/8 hand-verifiable sample passed)0.942 minutesthis entry (17–10)
@accidents_in_nizhnevartovsk7 (7/7 hand-verifiable sample passed)0.912 minutes@accidents_in_nizhnevartovsk (6–1)
@chp_hmao_ugra8 (8/8 hand-verifiable sample passed)0.95under a minutethis entry (6–2)

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. 14 of the 14 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 1,338 comparable posts for this entry, running 5 August 2026 to 17 November 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).

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 18 November 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.

Growth

63,22463,71763,470.563,3906 August 202615 November 2026
66 measurements spanning 102 days, net -198. 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 63,150–63,791 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
15 Nov 2026, 23:5563,390-44
12 Nov 2026, 13:1063,434-10
10 Nov 2026, 07:1763,444+14
8 Nov 2026, 20:5563,430+34
7 Nov 2026, 13:4763,396-5
6 Nov 2026, 15:5163,401+23
5 Nov 2026, 19:0063,378+13
4 Nov 2026, 20:5063,365+19
3 Nov 2026, 22:5963,346+92
2 Nov 2026, 21:3563,254+30
1 Nov 2026, 23:4063,224-38
31 Oct 2026, 21:3763,262-17
30 Oct 2026, 20:2063,279-23
29 Oct 2026, 21:4663,302-26
28 Oct 2026, 22:4563,328-10
27 Oct 2026, 22:5963,338-16
27 Oct 2026, 00:2663,354-16
25 Oct 2026, 06:1763,370-9
24 Oct 2026, 08:4063,379-10
23 Oct 2026, 05:5963,389first reading

Engagement

1,741 posts held, back to 5 August 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 217 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.25%
avg views ÷ 63,390 subscribers
Avg views / post
3,330
499 posts measured
Reaction rate
0.552%
reactions ÷ views · ER floor
Posts in window
499
of 1,741 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 418 of 499 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 18 November 2026
Posts held1,741 (5 August 2026 – 18 November 2026)
Views total1,661,127
Reactions total7,693
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 07:59 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
≈38,600
Videos
≈12,200
Links
≈2,590

Lifetime counters from Telegram’s own channel header, read 18 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
2h 14m
Average length
41s

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

15,996 reactions across 769 posts, in 9 distinct kinds. The most used accounts for 35.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬5,59935.0%
👍2,72017.0%
😁2,26714.2%
🙏1,71710.7%
😢1,2167.60%
👏9525.95%
💯7344.59%
😐4492.81%
🤔3422.14%

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 771 of the 1,000 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 15,996 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 22 September 2026 to 18 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.

Telegram Stars

Stars received
10
across the posts below
Posts paid on
7
of 1,000 we hold a reading for · 0.7%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nizhnevartovsk_chp. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 22 September 2026 to 18 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
3.10%
31 of 1,000 posts carry an ad marker
Regulatory tokens
28
posts carrying an erid · 28 distinct tokens
Median views · ads
3,260
over 31 measured posts
Median views · rest
3,420
over 969 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFG9CCXK18 October 20268 October 2026
2W5zFGJDsWR124 October 202624 October 2026
2W5zFGVwhbX116 October 202616 October 2026
2W5zFGYmcq7124 October 202624 October 2026
2W5zFGbjbPo125 October 202625 October 2026
2W5zFGtbiBT125 October 202625 October 2026
2W5zFGwEXzR122 October 202622 October 2026
2W5zFGyxjf7119 October 202619 October 2026
2W5zFH6BMZL117 November 202617 November 2026
2W5zFHDXiHo110 October 202610 October 2026
2W5zFHGpNkA112 November 202612 November 2026
2W5zFHXPbkm114 October 202614 October 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. 16 further tokens are held for this entry and not listed here.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 22 September 2026 to 18 November 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

Telegram’s own ‘edited’ marker: 9 of 499 posts held from the last 30 days (1.80%) 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).

18 Nov 2026, 06:48 UTC≈1,370 views22 reactionsread 18 November 2026

⚡️К делу с младенцем в мусоре подключился Бастрыкин. Он потребовал доложить ему детали расследования. Прислать новость - @chp_86 Подписаться на ЧП Нижневартовск - @nizhnevartovsk_chp

👍15🙏6😢1

17 Nov 2026, 13:15 UTC≈3,990 views20 reactionsread 18 November 2026

⚡️Пьяный башкортостанец устроил суету в самолёте, который летел из Нижневартовска в Тюмень 43-летний пассажир перебрал со спиртным, которое заказывал во время полёта. В какой-то момент он решил, что его очередной заказ несут слишком долго и начал требовать от бортпроводника поторопиться, сопровождая всё это отборным матом. В тюменском аэропорту башкортостанца встречали полицейские. На дебошира составили протокол, е…

👍19😁1

17 Nov 2026, 11:44 UTC≈4,100 views22 reactionsread 18 November 2026
Photo

«Ремонт по подписке»: УФАС приостановило скандальную закупку мэрии Нижневартовска на обслуживание иномарок Закупка мэрии Нижневартовска на ремонт служебного автопарка, о которой мы писали ранее, приостановлена. В Ханты-Мансийское УФАС поступила жалоба от автосервиса ООО «Регион-Трейд» (компания из Мегиона, которая по документам уже обслуживает автопарк мэрии по контракту 2026 года). Компания считает, что нашла в жал…

👍19😁2🤬1

17 Nov 2026, 10:28 UTC≈3,800 views7 reactionsread 18 November 2026
Photo

🚨 Жалоба на работу РНУ ЖКХ и ЖЭУ «Центральный». Снег лежит с первого снегопада, а ЖЭУ бездействует! С самого первого снега придомовую территорию ни разу не почистили. Пройти к детской площадке — почти экспедиция. Колея растёт, лёд нарастает, каждый шаг — риск. Звоню в ЖЭУ: в первый раз ответили, что «техники нет, ждите, пока появится». Сегодня (17.11) снова дозвонился до мастера — в ответ: «Мы не успеваем, ждите». На…

👍7

17 Nov 2026, 07:03 UTC906 viewsread 17 November 2026
Advertisementerid 2W5zFH6BMZLPhoto

Кто сегодня за рулём? Заказываешь такси, смотришь на машину, рейтинг водителя и время подачи. А кто приедет за тобой? Давай познакомимся чуть ближе. Drivee провёл исследование пользователей по всей стране. Оказалось, что чаще всего за рулём мужчина около 42 лет на Hyundai Solaris. Поездку делают люди, а не алгоритмы. Листай карточки, вдруг узнаешь знакомого водителя 👉 Реклама. ООО "ИН14". ИНН 1435308804. erid: …

17 Nov 2026, 06:23 UTC≈1,560 views12 reactionsread 17 November 2026
Photo

В Ханты-Мансийске почти достроили единственный в Югре храм в честь пророка защитника ВДВ. Митрополит Павел освятил его купола и кресты В Ханты-Мансийске митрополит Павел освятил купола и кресты строящегося храма в честь пророка Илии. Строительство объекта ведется по инициативе и на средства ктитора, руководителя ООО «Квартал» Василия Балесного. Во временном помещении храма ежедневно идут молебны о военнослужащих, зн…

🙏7👏2😐2🤬1

17 Nov 2026, 05:57 UTC≈1,950 views45 reactionsread 17 November 2026
Photo

Младенца выкинули в мусорку в Нижневартовске😱😱😱 Тело ребёнка примерно 5-9 месяцев нашли на контейнерной ленте в мусорном сортировочном центре. Об этом рассказал инсайдер в правоохранительных органах. Предварительно, у пока что неустановленной вартовчанки случились преждевременные роды и она решила избавиться от новорождённого младенца. Причину смерти ребёнка и другие обстоятельства происшествия устанавливают силови…

🤬33😢5👍4😁2👏1

16 Nov 2026, 22:50 UTC≈3,610 views91 reactionsread 17 November 2026
Video

Опубликуй пжл. Молодожь поёт в автобусе👍😁 Прислать новость - @chp_86 Подписаться на ЧП Нижневартовск - @nizhnevartovsk_chp

👍81😁6🙏3😐1

16 Nov 2026, 22:22 UTC≈3,440 views12 reactionsread 17 November 2026
Video

Добрый вечер Конечно, это не ЧП, но все же грустно смотреть, насколько злые сейчас дети: то морковку съедят и глаза выколют, то «лишних» дырок наделают или вообще голову снеговику снесут Прислать новость - @chp_86 Подписаться на ЧП Нижневартовск - @nizhnevartovsk_chp

😢9😁2🤔1

Showing the 12 most recent of 1,741 posts we hold for @nizhnevartovsk_chp. 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

@nizhnevartovsk_chp 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
15 October 2026
Most recent edit
15 October 2026

Posts recorded as deleted after publishing

We recorded 9 posts on @nizhnevartovsk_chp as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
4 September 2026
Most recent seen missing
12 November 2026
Median time before seen missing
16 hours
Seen missing in the last 30 days
5

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 9 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.

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.

Нижневартовск. Происшествия
@chp_nv_86 · 43,025
#1
Инцидент Нижневартовск ХМАО
@incidentnv · 8,900
#2
ЧП В Нижневартовске.
@accidents_in_nizhnevartovsk · 12,954
#3
Нижневартовск ⚡️ инцидент
@nizhnevartovsk_novosti · 5,344
#4
Нижневартовск | Официально
@adm_nvartovsk · 2,713
#5
NV86.ru • Нижневартовск
@nv86_me · 3,506
#6
Типичный краб Нижневартовск
@nv86_crab · 12,811
#7
N1 • Первый Нижневартовский
@n1_tv · 14,918
#8
ВПШ
@pravdadirty · 1,389,578
#9
LAGUNA
@lagunanv · 1,105
#10
НВГУ | Первый в Югре
@nvsunv · 1,938
#11
Сейчас | Нижневартовск
@justnow_nv · 1,836
#12
Мегаполис ЮГРА
@megapolis_ugra · 14,729
#13
Типичный Нижневартовск
@typical_nizhnevartovsk · 2,070
#14
Самотлор
@tv_samotlornv · 1,256
#15
Ханты, деньги, нефтевышки | URA.RU
@HantyMoney · 20,463
#16
Муксун.ФМ | Новости ХМАО и ЯНАО
@muksun_fm · 9,956
#17
t.ss
@mysechka05 · 547 (as read 8 September 2026)
#18
Эдмонд Игошин
@edmondigoshin · 2,186
#19
TREF.NAILS.EKB
@trefnailsnv · 342
#20
Работа Нижневартовск Вакансии
@nizhnevartovsk_rabota_vakansii · 4,999
#21
Bratishkinsk VIBE
@bratishkinsk_vibe · 167 (as read 8 September 2026)
#22
ВК "Югра-Самотлор"
@ugrasamotlor · 1,233
#23

Read from Telegram’s recommendation API, most recently 8 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.

Нижневартовск. Происшествия
@chp_nv_86 · 43,025
Telegram ranks this channel #1 of 26 here — alongside 25 others — read 8 September 2026
ЧП Сургут
@surgut_chp · 27,342
Telegram ranks this channel #21 of 53 here — alongside 52 others — read 11 September 2026
Новости Сургута и ХМАО
@surgut_smi · 29,427
Telegram ranks this channel #26 of 61 here — alongside 60 others — read 8 September 2026
Ханты, деньги, нефтевышки | URA.RU
@HantyMoney · 20,463
Telegram ranks this channel #65 of 95 here — alongside 94 others — read 26 September 2026
Югра, Сургут и все все все!
@surgutugra · 19,260
Telegram ranks this channel #71 of 91 here — alongside 90 others — read 2 October 2026

This channel appears in 5 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“ЧП Нижневартовск. Происшествия” (@nizhnevartovsk_chp), 63,390 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/nizhnevartovsk_chp.

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.