Telegram RegisterThe public register of Telegram

Channel

Nevermore: Санкт-Петербург

@nevermorequestionspb

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

648subscribers

+4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002164166002
TypeChannel
Username@nevermorequestionspb
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/nevermorequestionspb

Growth

6446486466 August 2026 — 644 subscribers7 August 2026 — 644 subscribers14 August 2026 — 648 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net +4. 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 643–649 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 12:57648+4
7 Aug 2026, 12:23644no change
6 Aug 2026, 18:46644first reading

Engagement

10 posts held, back to 15 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
150.6%
avg views ÷ 648 subscribers
Avg views / post
976
5 posts measured
Reaction rate
2.58%
reactions ÷ views · ER floor
Posts in window
5
of 10 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held10 (15 September 20255 August 2026)
Views total4,879
Reactions total126
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:46 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

451 reactions across 10 posts, in 14 distinct kinds. The most used accounts for 46.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
20946.3%
🔥13329.5%
custom 5271935247599044204429.31%
custom 5467497886113626882286.21%
👍143.10%
🥰61.33%
👨‍💻51.11%
🎉30.665%
🏆30.665%
💩30.665%
💔20.443%
😭10.222%
🤔10.222%
🤩10.222%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 10 most recent posts we hold, published 15 September 2025 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

5 Aug 2026, 17:37 UTC543 views25 reactionsread 6 August 2026
Photo

Дорогие друзья! В таблице со списком заявившихся команд появился лист «Предварительный список». Там вы можете увидеть список из 77 команд, которые прошли бы по состоянию на сегодня, и потенциальный лист ожидания (об изменениях в порядке приёма команд на фестиваль мы писали ранее в этом посте). Оргкомитет ещё не раздал свои 10 wildcard. Если вы считаете, что его должна получить именно ваша команда, то напишите нам,

13👍6🔥3custom 52719352475990442042😭1

29 Jul 2026, 14:30 UTC566 views21 reactionsread 6 August 2026
Forwarded from @ruchamp_intgames

12–13 сентября в Санкт-Петербурге пройдёт фестиваль Nevermore. Он получил предварительный статус отборочного турнира. Информацию о фестивале можно найти в его телеграм-канале, а также на турнирном сайте (альтернатива раз, альтернатива два). За другими выводящими турнирами можно следить с помощью нашего календаря. О том, что означает предварительный статус и как он может стать окончательным, читайте тут, более подр

custom 54674978861136268828🔥7custom 527193524759904420451

25 Jul 2026, 11:20 UTC≈1,300 views18 reactionsread 6 August 2026
Photo

Дорогие друзья! В этом году «Nevermore–6» в Санкт-Петербурге пройдёт в конференц-залах отеля «Московские ворота». Для гостей фестиваля доступна специальная цена на проживание с 10 по 15 сентября по промокоду NVRMR26 (оформление и оплата на сайте отеля). 🪶5200 рублей за номер категорий стандарт SGL/DBL (1 двуспальная кровать) или стандарт TWIN (2 раздельные кровати). 🪶7200 рублей за номер категории делюкс (1 двуспа

🔥153

24 Jul 2026, 16:00 UTC≈1,270 views17 reactionsread 6 August 2026
Photo

Дорогие друзья! Открыта регистрация на очный турнир «Nevermore–6», который состоится 12–13 сентября 2026 года в конференц-зале отеля «Московские Ворота» (Санкт-Петербург, Московский пр-т., 97а). Мы готовы принять не менее 87 команд, порядок принятия поданных заявок подробно расписан в регламенте. В программе: 90 вопросов основной дисциплины, эрудит-квартет, раздаточные конкурсы и другие развлекательные дисциплины.

12👨‍💻5

23 Jul 2026, 17:38 UTC≈1,200 views45 reactionsread 6 August 2026
Photo

Дорогие друзья! Рады пригласить вас на фестиваль «Nevermore–6», который пройдёт 12–13 сентября 2026 года в Санкт-Петербурге. Приём заявок будет открыт в пятницу, 24 июля в 19:00 по петербуржскому времени. Заявки как и в прошлые разы будут приниматься через гугл-форму. Оргкомитет планирует получить для фестиваля статус выводящего на III ЧР. Решение о том, хотите ли вы играть в выводящий зачёт, будет в форме окончат

🔥2113custom 52719352475990442047custom 54674978861136268822💔1🤔1

25 Sept 2025, 16:01 UTC≈1,780 views133 reactionsread 6 August 2026
Photo

Дорогие друзья! Фестиваль случился уже больше недели назад. Все вопросы отыграны, частично даже обсуждены (про обратную связь подробнее можно прочитать здесь), однако осталась ещё одна важная деталь — поблагодарить тех, без кого ничего бы не получилось. 🪶 Спасибо нашим чудесным редакторам, которые наполнили выходные загадками и решениями! Основной дисциплины — Диме Стальнухину, Артёму Колесову, Алексею Бороненко,

82🔥28custom 527193524759904420418👍4🤩1

22 Sept 2025, 12:47 UTC≈1,850 views46 reactionsread 6 August 2026
Photo

Дорогие друзья! На яндекс-диске появились фотографии. Если у вас тоже есть фото с фестиваля, квеста, муз.квиза — присылайте их ворону Эдгару, мы с удовольствием выложим их. Огромное спасибо Тане Козляковой, Георгию Антонову и Саше Килановой за фотографии!

26custom 527193524759904420410🥰6🎉3💔1

16 Sept 2025, 09:17 UTC≈1,640 views27 reactionsread 6 August 2026
Forwarded from @ruchamp_intgames

Фестиваль Nevermore, который проходил 13–14 сентября в Санкт-Петербурге, подтвердил статус отборочного турнира. В его выводящем зачёте участвовало 54 команды. Все его результаты можно найти на турнирном сайте, отборочные баллы — в листе ожидания. На всякий случай напомним, что в лист ожидания включаются не абсолютно все команды, а лишь те, которые получили отборочные баллы. Подробнее о том, как эти баллы начисляютс

custom 5467497886113626882166👍4💩1

15 Sept 2025, 17:08 UTC≈1,780 views66 reactionsread 6 August 2026
Photo

И, конечно, поздравляем победителей и призёров медальных дисциплин фестиваля! Эрудит-квартет 🪶 🥉 Рабочее название 🥈 Запахулья 🥇 Борский корабел MVP — Иван Семушин Основная дисциплина. Отметим, что судьба бронзовых медалей решилась в перестрелке на 19 (!) вопросах! 🍂 🥉 Призраки Коши 🥈 Рабочее название 🥇 Борский корабел На фотографиях победители в указанном выше порядке.

🔥5113🏆1💩1

15 Sept 2025, 16:48 UTC≈1,330 views53 reactionsread 6 August 2026
Photo

Дорогие друзья! Поздравляем победителей и призёров дополнительных дисциплин! Пешеходный квест 🪶 🥇 Я просто медленно пишу Дау 🪶 🥇 Белый шум Авторский дизайн блокнотов 🪶 🥇 Ксения Егорова Музыкальный квиз 🪶 🥉 Мантисса 🥈 Симба-гой 🥇 Говорят, запретят целоваться На фотографиях победители в указанном порядке. В комментариях выложены ответы на Дау.

40🔥8🏆2custom 54674978861136268822💩1

Showing the 10 most recent of 10 posts we hold for @nevermorequestionspb. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 779,145 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Nevermore: Санкт-Петербург” (@nevermorequestionspb), 648 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/nevermorequestionspb.

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.