Telegram RegisterThe public register of Telegram
Telegram profile photo for Phantom Visuals - Делай правильный выбор!

Channel

Phantom Visuals - Делай правильный выбор!

@phantomvisual

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

12,565subscribers

+5,941 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002310051297
TypeChannel
Username@phantomvisual
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 November 2026
Measurements held44
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/phantomvisual

Topic

Gaming — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Growth

6,62412,5709,59710 August 2026 — 6,624 subscribers11 August 2026 — 6,675 subscribers14 August 2026 — 7,035 subscribers17 August 2026 — 7,208 subscribers21 August 2026 — 7,362 subscribers24 August 2026 — 7,606 subscribers27 August 2026 — 7,801 subscribers30 August 2026 — 8,010 subscribers2 September 2026 — 8,240 subscribers6 September 2026 — 8,488 subscribers11 September 2026 — 8,614 subscribers14 September 2026 — 8,768 subscribers19 September 2026 — 9,029 subscribers29 September 2026 — 10,565 subscribers5 October 2026 — 10,816 subscribers9 October 2026 — 10,910 subscribers13 October 2026 — 10,984 subscribers14 October 2026 — 10,987 subscribers15 October 2026 — 11,009 subscribers17 October 2026 — 11,014 subscribers18 October 2026 — 11,040 subscribers19 October 2026 — 11,074 subscribers20 October 2026 — 11,168 subscribers21 October 2026 — 11,288 subscribers22 October 2026 — 11,423 subscribers23 October 2026 — 11,527 subscribers24 October 2026 — 11,645 subscribers25 October 2026 — 11,747 subscribers26 October 2026 — 11,845 subscribers27 October 2026 — 11,896 subscribers28 October 2026 — 11,969 subscribers29 October 2026 — 12,021 subscribers30 October 2026 — 12,116 subscribers31 October 2026 — 12,219 subscribers1 November 2026 — 12,277 subscribers2 November 2026 — 12,374 subscribers3 November 2026 — 12,401 subscribers4 November 2026 — 12,397 subscribers6 November 2026 — 12,443 subscribers6 November 2026 — 12,498 subscribers8 November 2026 — 12,524 subscribers9 November 2026 — 12,560 subscribers11 November 2026 — 12,570 subscribers13 November 2026 — 12,565 subscribers12,56510 August 202613 November 2026
44 measurements spanning 95 days, net +5,941. 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 5,732–13,462 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 44
Measured (UTC)SubscribersChange
13 Nov 2026, 23:4712,565-5
11 Nov 2026, 08:2112,570+10
9 Nov 2026, 14:5612,560+36
8 Nov 2026, 07:2012,524+26
6 Nov 2026, 23:4012,498+55
6 Nov 2026, 00:1612,443+46
4 Nov 2026, 23:2012,397-4
3 Nov 2026, 22:2112,401+27
2 Nov 2026, 22:3712,374+97
1 Nov 2026, 21:0112,277+58
31 Oct 2026, 23:5812,219+103
30 Oct 2026, 21:5812,116+95
29 Oct 2026, 20:4612,021+52
28 Oct 2026, 19:0811,969+73
27 Oct 2026, 19:0011,896+51
26 Oct 2026, 19:4811,845+98
25 Oct 2026, 23:0811,747+102
24 Oct 2026, 22:0811,645+118
23 Oct 2026, 20:1911,527+104
22 Oct 2026, 17:3611,423first reading

Engagement

67 posts held, back to 26 July 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 34 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
73.9%
avg views ÷ 12,565 subscribers
Avg views / post
9,280
19 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
19
of 67 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 5 of 19 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 13 November 2026
Posts held67 (26 July 2026 – 13 November 2026)
Views total176,390
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 22:01 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

1,063 reactions across 23 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52089638029046717091,063100.0%

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 is Telegram’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 32 of the 67 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 1,063 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 67 most recent posts we hold, published 26 July 2026 to 13 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
123
across the posts below
Posts paid on
21
of 67 we hold a reading for · 31%
Most on one post
50
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @phantomvisual. 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 67 most recent posts we hold for this entry, published 26 July 2026 to 13 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.

Recent posts

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

13 Nov 2026, 14:31 UTC≈1,150 viewsread 13 November 2026

@devblogphantom это нужно посмотреть

Signed kide

10 Nov 2026, 16:35 UTC≈3,120 viewsread 13 November 2026

👀 Бот работает до 19 ноября, я найду деньги чтоб продлить хостинг и он дальше будет работать пока бот не будет доступен версии выложу сюда а пока скачивать здесь ⬇️ @phantomvisbot

Signed kide

9 Nov 2026, 16:26 UTC≈4,900 views0 reactions1 Starread 13 November 2026

Я короче вышел с запоя просто было лень делать, но я взял не большую паузу и я теперь сильно настроен делать UPDATE!!

Signed kidcade.

7 Nov 2026, 17:54 UTC≈6,060 viewsread 13 November 2026

Обновление не требует повод обновлятся это всего лишь фикс у кого на аукционе пропадают вещи

Signed kidcade.

7 Nov 2026, 17:53 UTC≈5,790 viewsread 13 November 2026

Залил в бота обновление✔️ @phantomvisbot

Signed kidcade.

7 Nov 2026, 17:48 UTC≈5,620 viewsread 13 November 2026

Нужен вам срочный фикс проблем с аукционом то что предметы пропадают

Signed kidcade.

4 Nov 2026, 13:10 UTC≈7,240 viewsread 13 November 2026

Что бы вы хотели видеть в 26.3 напишите в комментариях

Signed kidcade.

3 Nov 2026, 19:55 UTC≈7,760 viewsread 13 November 2026

Постоянно вижу комментарии как скачать❓ Все довольно просто👀 1.Скачиваете файл для нужной вам версии с @phantomvisbot бот официальный так что не сыте ✔️ 2. Скачиваете Fabric api нужной версии тоже 3. Кидаете все в папку “mods” 4. Наслаждаетесь игрой⭐️

Signed kidcade.

3 Nov 2026, 19:48 UTC≈7,610 viewsread 13 November 2026

Скоро пойдут спойлеры на 26.3

Signed kidcade.

30 Oct 2026, 16:15 UTC≈10,400 views0 reactions1 Starread 13 November 2026

😁 PhantomVisuals 5.1 FIX FIX Изменения для Minecraft 1.21.4 и 1.21.11: • Добавлен Fast Use и сохранение биндов в обеях версиях. • Пофикшено не сколько багов. Скачать можно в боте ✔️ Бот запущен ⚙️ Бот: @phantomvisbot

Signed kidcade.

29 Oct 2026, 14:26 UTC≈10,200 viewsread 13 November 2026

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

Signed kidcade.

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

Posts edited after publishing

@phantomvisual 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
11 November 2026
Most recent edit
11 November 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @phantomvisual 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
12 August 2026
Most recent seen missing
11 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
2

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.

18 Sept 2026, 19:08 UTCAnonymous Poll1,460 voters approx.

🔥 Ждёте релиз?

  1. ✔️92%
  2. ❌11%

The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 67 most recent posts we hold, published 26 July 2026 to 13 November 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.

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 6 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“Phantom Visuals - Делай правильный выбор!” (@phantomvisual), 12,565 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/phantomvisual.

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.