Telegram RegisterThe public register of Telegram
Telegram profile photo for Вартовск RP DINE

Channel

Вартовск RP DINE

@Wartovsk

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry

120subscribers

+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-1002395779143
TypeChannel
Username@Wartovsk
DescriptionМеня зовут DINE - [Дайн]. Канал - моё продолжение легендарной карты Вартовск RP😊 Канал родителя карты👾: https://t.me/Ph0bb
CreatedBetween 1 September 2024 and 28 January 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/Wartovsk

Growth

1207 August 2026 — 120 subscribers9 August 2026 — 120 subscribers7 August 20269 August 2026
2 measurements spanning 2 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 119–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 04:02120no change
7 Aug 2026, 13:05120first reading

Engagement

20 posts held, back to 28 January 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 20 posts for this entry, the most recent from 9 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
27
Videos
1
Links
13

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.

Video runtime
2m 51s
Average length
2m 51s

Measured directly from 1 video 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

59 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 39.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53167278051263849322339.0%
custom 53550880478325724401932.2%
custom 53393921413889478801525.4%
custom 533921426102341643423.39%

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

Measured over the 20 most recent posts we hold, published 28 January 2025 to 9 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Wartovsk. 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 20 most recent posts we hold for this entry, published 28 January 2025 to 9 June 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.

Recent posts

9 Jun 2026, 10:10 UTC139 viewsread 9 August 2026

Продолжение Вартовска «Вартовск Town» сейчас на версии 3.3.1. уже добавили новые нововведения и механики

15 Mar 2026, 21:06 UTC281 viewsread 9 August 2026
Photo

Моей первой работой станет… Вартовск RP — возрождение легендарной карты, которая была заброшена примерно год назад, а достойное обновление 3.4 так и не вышло. Пришло время исправить эту ситуацию и наконец-то выпустить глобальное обновление, о котором так долго говорили, но так и не смогли реализовать ( ཀ ʖ‌ ཀ) Дань и почтение им: Оригинальная версия – Вартовск RP🌿 Фан версии: Wartovsk RP fantasy✨, Вартовск RP D

30 Apr 2025, 06:13 UTC≈1,180 views0 reactions1 Starread 9 August 2026

Продолжение Вартовск RP DINE! от другого создателя! https://t.me/wartowsk_fantasy

9 Feb 2025, 15:02 UTC≈1,570 viewsread 9 August 2026
Video

✨Пляж✨ в DineVille❤️,кому интересно сюда👉@DINEVILLE

5 Feb 2025, 19:50 UTC≈1,590 views25 reactionsread 9 August 2026
Photo

Вот и пришёл конец Вартовск РП DINE. Для кого-то это печально), но лично для меня нет. Пришло осознание того, что я не сделаю больше ни одного хорошего обновления, по причине того что у меня больше нет мотивации. Пора добиваться новых высот! https://t.me/DINEVILLE

custom 531672780512638493219custom 53393921413889478803custom 53550880478325724403

5 Feb 2025, 17:34 UTC≈1,320 viewsread 9 August 2026

Вайп на сервере!, вышло обновление!

5 Feb 2025, 17:27 UTC≈1,300 views13 reactionsread 9 August 2026
Photo

⬆️ARMY UPDATE⬆️ | V3.2.7 Добавлено: -Армия -Снова доступна панель управления

custom 535508804783257244011custom 53392142610234164342

1 Feb 2025, 14:57 UTC≈1,040 views7 reactionsread 9 August 2026

Если да то после последней обновы начну делать)

custom 53393921413889478806custom 53550880478325724401

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

1 Feb 2025, 14:55 UTCAnonymous Poll101 voters

Как вы думаете?)

  1. Да, хотелось бы видеть твой собственный проэкт.66%
  2. Нет, продолжай делать Вартовск.34%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 28 January 2025 to 9 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 749,590 of 1,565,402entries 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.

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.

“Вартовск RP DINE” (@Wartovsk), 120 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Wartovsk.

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.