Telegram RegisterThe public register of Telegram
Telegram profile photo for Евгений Моисеев

Channel

Евгений Моисеев

@moiseev_eugene

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

17,141subscribers

-207 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-1001527341237
TypeChannel
Username@moiseev_eugene
DescriptionЛичный блог #FNNYX
Created27 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/moiseev_eugene

Topic

National news — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 2 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@moiseev_eugene/33381 · this entry7 Aug 2026, 10:05 UTC@tipich_kislovodck_oficial/96577 Aug 2026, 10:07 UTC1.002 minutes
@moiseev_eugene/33753 · this entry17 Aug 2026, 10:43 UTC@tipich_kislovodck_oficial/967917 Aug 2026, 11:10 UTC1.0027 minutes
@moiseev_eugene/34103 · this entry31 Aug 2026, 11:06 UTC@tipich_kislovodck_oficial/970031 Aug 2026, 11:43 UTC1.0037 minutes
@moiseev_eugene/36004 · this entry7 Nov 2026, 07:31 UTC@tipich_kislovodck_oficial/98107 Nov 2026, 10:55 UTC1.003.4 hours
@moiseev_eugene/36030 · this entry10 Nov 2026, 09:26 UTC@tipich_kislovodck_oficial/981110 Nov 2026, 11:06 UTC1.001.7 hours
@moiseev_eugene/35713 · this entry3 Nov 2026, 13:33 UTC@kisgazetaofficial/624913 Nov 2026, 13:57 UTC1.0024 minutes
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
@tipich_kislovodck_oficial5 (5/5 hand-verifiable sample passed)1.0037 minutesthis entry (5–0)
@kisgazetaofficial7 (7/7 hand-verifiable sample passed)1.0043 minutes@kisgazetaofficial (4–3)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 204 comparable posts for this entry, running 5 August 2026 to 11 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @moiseev_eugene — which is this entry. That is a statement about our reading window, not a claim of authorship.

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

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

17,14117,37617,258.56 August 202612 November 2026
63 measurements spanning 98 days, net -207. 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 17,106–17,411 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
12 Nov 2026, 09:5117,141-3
10 Nov 2026, 05:2017,144+1
8 Nov 2026, 15:0217,143-2
7 Nov 2026, 05:4717,145-3
6 Nov 2026, 06:2017,148-2
5 Nov 2026, 04:4817,150-1
4 Nov 2026, 07:1717,151+4
3 Nov 2026, 04:3117,147-3
2 Nov 2026, 03:1017,150-10
1 Nov 2026, 01:3717,160-7
31 Oct 2026, 01:3717,167-13
30 Oct 2026, 03:2817,180-4
29 Oct 2026, 06:4917,184-6
28 Oct 2026, 04:5717,190-3
27 Oct 2026, 02:2717,193-2
26 Oct 2026, 02:3917,195-3
25 Oct 2026, 01:4717,198+4
24 Oct 2026, 00:3617,194-2
22 Oct 2026, 23:2717,196-2
21 Oct 2026, 20:2917,198first reading

Engagement

220 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 74 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.11%
avg views ÷ 17,141 subscribers
Avg views / post
1,050
59 posts measured
Reaction rate
1.61%
reactions ÷ views · ER floor
Posts in window
59
of 220 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 56 of 59 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 12 November 2026
Posts held220 (5 August 2026 – 12 November 2026)
Views total61,829
Reactions total984
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 17:10 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
≈24,800
Videos
≈8,000
Links
≈1,550

Lifetime counters from Telegram’s own channel header, read 12 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
47m 48s
Average length
31s

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

4,237 reactions across 215 posts, in 40 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,06125.0%
❤1,02324.1%
💩1,01924.1%
🤡4079.61%
🔥1493.52%
🙏1012.38%
👎952.24%
🤮882.08%
😱741.75%
👏350.826%
🤣270.637%
😁220.519%
😢170.401%
❤‍🔥150.354%
🥰120.283%
🖕110.26%
🎉80.189%
🤔70.165%
😐60.142%
🤬60.142%
20 further kinds541.27%

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

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

Advertising

Ad load
0.455%
1 of 220 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,120
over 1 measured post
Median views · rest
1,140
over 218 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
2VtzqxLF91815 November 20265 November 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 220 most recent posts we hold, published 5 August 2026 to 12 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: 2 of 59 posts held from the last 30 days (3.39%) 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).

12 Nov 2026, 08:12 UTC865 views15 reactionsread 12 November 2026
Photo

Рубрика «Ремонт дорог» - ремонт Крутой дороги. Работы идут активно. Установили бордюры, переделали лестницу, уложили трубы ливнёвки. Теперь ремонт освещения и устройство асфальта. Одновременно направил обращение в Теплоэнерго Кисловодск для восстановления изоляции воздушной теплотрассы, ремонта и покраски опор. К концу года должно быть всё закончено. Всем хорошего дня.

👍8💩4❤2😁1

Signed Евгений Моисеев

12 Nov 2026, 07:05 UTC889 views17 reactionsread 12 November 2026
Photo

Более 1000 тонн соли заготовили в Кисловодске для обработки дорог зимой. Используем технологию превентивной обработки дорожного покрытия жидким солевым раствором. Во время снегопадов дороги дополнительно обрабатываем смоченной рассолом чистой пищевой солью. К предстоящему сезону переоборудовали и подготовили более 20 единиц коммунальной техники, которая будет задействована в уборке снега и обработке улично-дорожно…

👍13🤡4

Signed Евгений Моисеев

12 Nov 2026, 06:46 UTC785 views8 reactionsread 12 November 2026
Forwarded from @oficial_kislovodskPhoto

Доброе утро, Кисловодск 🍁! Сегодня город встречает нас облачным небом, а температура стала немного выше. Пусть погода не помешает прогулкам и хорошему настроению — одевайтесь по сезону и наслаждайтесь осенним днём. 12 ноября в России отмечают Синичкин день — экологический праздник, который напоминает о зимующих птицах и о том, как важно заботиться о них в холодное время года. Пусть день будет добрым, спокойным и н…

👍6❤2

Signed Евгений Моисеев

11 Nov 2026, 07:47 UTC≈1,440 views38 reactionsread 12 November 2026
Photo

Спортсмен из Кисловодска стал чемпионом мира по кикбоксингу. Воспитанник спортивной школы № 1 Кисловодска Эдуард Давидян завоевал золотую медаль чемпионата мира по кикбоксингу, который прошёл в Картахене (Колумбия). Спортсмен выступал в составе сборной России в разделе фулл-контакт в весовой категории до 86 кг. Эдуард начинал свой спортивный путь в Кисловодске, занимался в спортивной школе № 1, окончил гимназию № …

🔥23👍13❤2

Signed Евгений Моисеев

11 Nov 2026, 07:44 UTC≈1,390 views10 reactionsread 12 November 2026
Photo

Уважаемые экономисты, поздравляю вас с профессиональным праздником! Экономика города складывается из ежедневной работы многих людей. Это расчёты, планирование, поиск решений и задач, от которых зависит развитие Кисловодска. Наш город развивается как современный курорт, привлекает туристов и инвесторов, расширяет возможности для бизнеса. Появляются новые возможности для бизнеса, растёт туристический поток, реализу…

❤8👍1🤡1

Signed Евгений Моисеев

11 Nov 2026, 05:33 UTC≈1,500 views16 reactionsread 12 November 2026
Photo

Первый молодежный фиджитал-турнир по тактической стрельбе стартует в Кисловодске. 14 ноября в Кисловодске впервые состоится турнир по фиджитал спорту в дисциплине «тактическая стрельба». Соревнования объединят два этапа: виртуальный бой в компьютерной игре Counter-Strike и физический раунд на площадке с использованием оборудования для лазертага. Турнир пройдет в единственном на Ставрополье фиджитал-центре в Кислов…

🤡7👍3💩3❤2👎1

Signed Евгений Моисеев

10 Nov 2026, 15:19 UTC≈1,690 views26 reactionsread 12 November 2026

Уважаемые жители и гости Кисловодска! По информации ООО "Теплоэнерго-Кисловодск" завтра, 11.11.2026г., в рамках подготовки к ОЗП 2026-2027 будет произведена остановка подачи центрального отопления от ЦТП Велинградская 8, для переврезки, а также ввода в эксплуатацию нового пластинчатого водоподогревателя отключение планируется с 11:00 примерно на 3 часа. Адреса, попадающие под отключение: Велинградская 5,8,19,22 Дзе…

👎16💩5👍3❤1😡1

Signed Евгений Моисеев

10 Nov 2026, 13:35 UTC≈1,730 views19 reactionsread 12 November 2026
Video

Вот мы все ругаем теплосети за то, что центральная система теплоснабжения не работает так, как надо. А как же она будет работать, если каждый считает себя вправе вносить свои вольные изменения? Управляющие компании обратку выводят в канализацию или на улицу, чтобы увеличить подачу горячей воды. И за всё это, за такие потери воды, мы сами, как абоненты, платим все вместе. Так никакая система работать нормально не…

❤10🤬4😱4👍1

Signed Евгений Моисеев

10 Nov 2026, 11:20 UTC≈1,600 views21 reactionsread 12 November 2026
Video

Ремонт дорог - улица Фоменко. Подрядчик работает активно. Срок выполнения работ - до конца текущего года. Всем хорошего дня.

👍14🤡4💩3

Signed Евгений Моисеев

10 Nov 2026, 09:26 UTC≈1,600 views20 reactionsread 12 November 2026
Photo

Кисловодск стал одним из самых востребованных городов для новогоднего отдыха. Кисловодск вошёл в десятку самых востребованных направлений для поездок на новогодние праздники в России. По данным сервиса Ostrovok, представленным РИА Недвижимость, курорт оказался в одном ряду с Москвой, Санкт-Петербургом, Казанью, Сочи и другими популярными туристическими городами. Кисловодск — прекрасное место для семейных путешеств…

❤7🤡4👍3💩3🖕2🤮1

Signed Евгений Моисеев

10 Nov 2026, 09:08 UTC≈1,560 views6 reactionsread 12 November 2026
Video

Избавляться от наркоспама можно только совместными усилиями. Каждый убранный с фасадов домов или объектов инфраструктуры след незаконной рекламы делает наш край чище и безопаснее. Борьба с визуальным мусором — это вклад каждого из нас в общее дело. Вместе мы можем создать пространство без наркорекламы и защитить будущее нашего города и страны. Источник: https://t.me/antinarkotik_sk/3595 #безопасныйКисловодск

❤3👍3

Signed Евгений Моисеев

10 Nov 2026, 06:32 UTC≈1,620 views29 reactionsread 12 November 2026
Photo

Уважаемые сотрудники органов внутренних дел! Поздравляю вас с профессиональным праздником! Наш город остается безопасным во многом благодаря вашей службе. Вы ежедневно стоите на страже общественного порядка, обеспечиваете безопасность жителей и гостей Кисловодска, помогаете людям и приходите на помощь в самых непростых ситуациях. За этой работой стоят большая ответственность, выдержка, мужество и верность своему …

👍18💩6❤5

Signed Евгений Моисеев

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

@moiseev_eugene 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
2 September 2026
Most recent edit
2 September 2026

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

Михаил Миненков
@maMinenkov · 24,730
Telegram ranks this channel #18 of 87 here — alongside 86 others — read 14 September 2026
Ворошилов
@voroshilov_dm · 33,381
Telegram ranks this channel #45 of 95 here — alongside 94 others — read 4 September 2026
GOVORUN26 Новости КМВ, Ставрополья и РФ
@govorun26 · 27,254
Telegram ranks this channel #55 of 90 here — alongside 89 others — read 10 September 2026
Пятигорск и мой КМВ
@MyKMV26 · 18,464
Telegram ranks this channel #63 of 89 here — alongside 88 others — read 5 October 2026
Владимир Владимиров
@VVV5807 · 146,195
Telegram ranks this channel #65 of 99 here — alongside 98 others — read 12 August 2026
Телеблог Ставрополь Пятигорск Кисловодск новости реклама афиша объявления
@Nevinomyssk_Essentuky · 30,245
Telegram ranks this channel #66 of 94 here — alongside 93 others — read 9 September 2026
Блокнот Ставрополь
@bloknot_stavropol · 58,829
Telegram ranks this channel #70 of 98 here — alongside 97 others — read 22 August 2026
ЧП Ставрополь | новости края
@chp26reg · 19,334
Telegram ranks this channel #75 of 85 here — alongside 84 others — read 1 October 2026
Пятигорск Онлайн
@ptgorsk · 26,080
Telegram ranks this channel #78 of 91 here — alongside 90 others — read 12 September 2026
Это Ставрополь, детка!
@this_is_stavropol · 19,275
Telegram ranks this channel #84 of 93 here — alongside 92 others — read 1 October 2026
1777 Новости | Ставрополь и Ставропольский край
@Stavropol1777 · 38,752
Telegram ranks this channel #84 of 93 here — alongside 92 others — read 30 August 2026
Ставрополье с огоньком
@stavropoltop · 26,883
Telegram ranks this channel #85 of 91 here — alongside 90 others — read 11 September 2026
Госавтоинспекция Ставрополья
@gibdd26 · 26,795
Telegram ranks this channel #92 of 97 here — alongside 96 others — read 11 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“Евгений Моисеев” (@moiseev_eugene), 17,141 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/moiseev_eugene.

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.