Telegram RegisterThe public register of Telegram

Channel

• Viktor Novgorod •

@viktornovgorodishere

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

85subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001642723664
TypeChannel
Username@viktornovgorodishere
Description✨Бесполый антропоморфный волчонок с рогами и птицами.✨
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/viktornovgorodishere

Growth

857 August 2026 — 85 subscribers9 August 2026 — 85 subscribers7 August 20269 August 2026
2 measurements spanning 3 days. 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 84–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 16:4685no change
7 Aug 2026, 04:0185first reading

Engagement

9 posts held, back to 5 December 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
927
Videos
27
Links
84

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

12 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 83.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1083.3%
custom 547428108687797469818.33%
🔥18.33%

Custom emoji. One row above is a 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 count beside it isTelegram’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 3 of the 9 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 12reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 5 December 2025 to 27 June 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

27 Jun 2026, 05:47 UTC28 views1 reactionsread 9 August 2026
Forwarded from @reddragon_kldPhoto

🎃 Мы готовы показать вам подарки к билетам 🎃 🍉 Купить билет можно тут 🍉 Скидки на спонсорский и вип билеты останутся до вечера, уже завтра мы поменяем цену на обычную!🧡 ∘₊✧──────✧₊∘ 🎪 Спонсорский | 13.00 🎃Подарки к билету: Двусторонний физический билет Открытка Коллекционная карточка Стикер 2 стикерпака Парные своп карты Парные своп карты 2 Брелок Брелок телевизор Брелок спиннер Брелок на красном акриле с глиттер

1

30 Apr 2026, 16:09 UTC60 views5 reactionsread 9 August 2026
Forwarded from @reddragon_kldPhoto

🎪 Мы готовы представить вам наших авторов!!! 🍉 бес-трава 🍉 вичка 🍉 дубасик 🍉 ква 🎃 Которая ✶ голубая 🎃 Лягушка в шапочке 🎃 миниманьяк 🎃 ✦ небесный прибой ✦ 🍉 орех 🍉 Платон 🍉 Поликлиника 🍉 пуф малякает 🎃 пшёнка тушёнка 🎃 рыжик 🎃 соня вор 🎃 Сульфит Калия ✦ K2So3 🍉 Сырник со сметаной 🍉 Твоя Линор 🍉 Фонарик 🍉 хиха 🎃 A. Lutrin 🎃 akirabe 🎃 B A R S U K 🎃 belayaiva 🍉 Biblically Accurate Inga 🍉 BW space 🍉 clara umbra 🍉

3🔥1custom 54742810868779746981

22 Apr 2026, 13:02 UTC133 viewsread 9 August 2026

Я знаю, что тут есть те, кто знает дискорд сервер и storiel, я лично оттуда узнала, так что держу в курсе дела. И да, не бейте тапками…

22 Apr 2026, 13:00 UTC122 viewsread 9 August 2026
Forwarded from @montycryveryloudPhoto

друзья, у стори (storiel) произошёл гигакринж с воровством почты и ХАКОМ БОЛЬШИНСТВА АККАУНТОВ СОЦСЕТЕЙ так что сейчас она не может зайти никуда, так как мамкины хацкеры везде поменяли доступы поэтому очень большая просьба кинуть репорт на аккаунты @storiel и @moorzeena , так как ими сейчас управляет не сторя, а мошенники в скринах лор самого мошенничества... вот ВСЕГДА ДУМАЕШЬ, ЧТО НУ ТЫ-ТО НЕ ПОПАДЁШЬСЯ, а пото

6 Dec 2025, 19:00 UTC194 viewsread 9 August 2026

🎉 Результаты розыгрыша: 🏆 Победитель: 1. Александр (@leBrainwash) ✔️Проверить результаты

Signed Randomize Bot 🎲 [Рандомайзер]

6 Dec 2025, 15:14 UTC181 viewsread 9 August 2026

Скидку 10% думаю разыграть отдельно, ввиде 1 вопрос - ответа, что думаете?

6 Dec 2025, 15:01 UTC185 viewsread 9 August 2026
Photo

Розыгрыш! На арт-маркет Red Dragon (7 декабря) разыграем 3 бесплатных прохода! • Условия билета: пройти возможно по ним только с 14:00, без подарочного мерча и участия в квесте. • Условия розыгрыша: 1) Быть подписанным на этот канал 2) Нажать кнопку «Участвую!» Разыгрываем до 22:00 по МСК! P.S.: Купить официальный мерч можно будет за столом организатора, бланк квеста тоже возможно приобрести отдельно.

Signed Randomize Bot 🎲 [Рандомайзер]

5 Dec 2025, 15:28 UTC150 views6 reactionsread 9 August 2026
Photo

Напоминаю про скидочные промокоды на 30% (билеты любой категории)! Также есть в наличии скидка в 10% и 3 бесплатные проходки на маркет (вход по ним с 14:00, без подарочного мерча и возможности участвовать в квесте), если нужно - можем разыграть между желающими.

6

Showing the 9 most recent of 9 posts we hold for @viktornovgorodishere. 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 — 1,116,149 of 1,169,250entries 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

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

“• Viktor Novgorod •” (@viktornovgorodishere), 85 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/viktornovgorodishere.

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.