Telegram RegisterThe public register of Telegram

Channel

Parzival

@Parzival_INFMS

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

661subscribers

+13 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-1002321563544
TypeChannel
Username@Parzival_INFMS
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/Parzival_INFMS

Growth

648661654.57 Aug 2026, 19:03 — 648 subscribers8 Aug 2026, 02:47 — 648 subscribers8 Aug 2026, 06:05 — 661 subscribers7 Aug 2026, 19:038 Aug 2026, 06:05
3 measurements taken within a single day, net +13. 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 646–663 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 06:05661+13
8 Aug 2026, 02:47648no change
7 Aug 2026, 19:03648first reading

Engagement

13 posts held, back to 30 May 2026the 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
159.7%
avg views ÷ 661 subscribers
Avg views / post
1,060
7 posts measured
Reaction rate
0.866%
reactions ÷ views · ER floor
Posts in window
7
of 13 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 7 August 2026
Posts held13 (30 May 20267 August 2026)
Views total7,389
Reactions total64
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:47 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

109 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 41.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4541.3%
🙏2422.0%
1211.0%
🔥1110.1%
🤡54.59%
😱43.67%
🏆32.75%
👍21.83%
👎21.83%
😁10.917%

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

Measured over the 13 most recent posts we hold, published 30 May 2026 to 7 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

7 Aug 2026, 22:01 UTC871 views27 reactionsread 8 August 2026
Photo

Хотелось бы поговорить про баг связанный с Golden Goose Egg. После предыдущего поста, уже успел увидеть некоторые фейки. В том числе saintmxsm aka Scrooge McSim, главная скряга Deadlock, решил воспользоваться ситуацией и используя своё бизнес образование полученное в IESE Business School, где он по совместительству изучал иностранные языки. Максим отвечая на вопрос связанный с багом Golden Goose Egg, сказал зрителю,

🙏24😱21

6 Aug 2026, 19:28 UTC509 views14 reactionsread 8 August 2026

Максим выпустил видео с множеством полезной информации для игроков, которые играют или хотят играть на саппортах. Видео ориентировано на новичков и игроков среднего уровня. Единственное, что хотел бы отметить, Максим забыл упомянуть (или решил утаить) про силу яйца (Golden goose egg) в текущей мете, потому что оно до сих пор с багом. С ним нужно учиться играть и абузить при возможности, особенно в паблике, потому чт

12🤡1😁1

5 Aug 2026, 04:40 UTC≈2,300 views13 reactionsread 8 August 2026
Photo

Сегодня в 23.00 🌙 по Московскому времени стартует юбилейный 50-ый Deadlock Night Shift 😄 Мы с командой не участвуем на этой неделе, потому что даже не приняли участие в квалификации, в связи с тем что команду покинули 3 игрока и состав будет пересобираться. Об изменениях в составе сообщу ближе к следующему DLNS 🗓 Данный Deadlock Night Shift будем смотреть/комментировать с Озесом. Причём смотреть будем и EU и NA. Фи

10😱2🤡1

1 Aug 2026, 17:29 UTC791 views1 reactionsread 8 August 2026
Photo

Играем 💀Deadchaps Gauntlet Day 2 Официальная трансляция: twitch.tv/deadchaps 🙂

🤡1

31 Jul 2026, 13:43 UTC826 views1 reactionsread 8 August 2026
Photo

Играем 💀Deadchaps Gauntlet Официальная трансляция: twitch.tv/deadchaps 🙂

🤡1

29 Jul 2026, 01:52 UTC962 views1 reactionsread 8 August 2026
Photo

Через 3 дня стартует 💀Deadchaps Gauntlet на 5000€, а пока что можете поиграть в кликер от организаторов турнира, пока 👁 готовит патч Играть тут deadchaps.gg/soul-clicker

🤡1

22 Jul 2026, 03:23 UTC≈1,130 views7 reactionsread 8 August 2026
Photo

Привет. Месяц без постов, потому что особо и не было новостей, собственно как и от разработчиков 👁 Многие могли уже слышать, что наша команда была приглашена на Третий сезон R1 tourney, который по итогу был перенесён за день до начала турнира, а может и вовсе отменён, узнаем через месяц 🫠 Помимо этого мы планировали и собираемся сыграть, на грядущем 💀Deadchaps Gauntlet на 5000€, который пройдёт с 31 июля по 2 Авгус

7

23 Jun 2026, 04:41 UTC≈1,470 views25 reactionsread 8 August 2026
Photo

Game 1 - 89994629 | vs Slice 'n Dice | 1/4 Final | BO1 | R1 Tourney DeadLock 02 Open Qualifiers Game 2 - 90008241 | vs trashcan | 1/2 Final | BO1 | R1 Tourney DeadLock 02 Open Qualifiers Game 3 - 90023543 | vs leftlovers |Final | BO3 | Game 1 | R1 Tourney DeadLock 02 Open Qualifiers Game 4 - 90031378 | vs leftlovers |Final | BO3 | Game 2 | R1 Tourney DeadLock 02 Open Qualifiers Game 5 - 90186663 | vs Leviathan |

24👍1

12 Jun 2026, 07:08 UTC≈1,600 views15 reactionsread 8 August 2026
Photo

Сделал ночью Tier List игроков (с уклоном в компетитив) на стриме. Потратил порядка пяти часов на расстановку и корректировку положения игроков по тирам. Пытался оценивать объективно, насколько это возможно, беря в учёт всю имеющуюся у меня информацию, а также такие факторы как, механический и макро скилл, лидерские качества, способность к ин-гейм лидерству, стрессоустойчивость, работа в команде, возраст, опыт в ком

🔥11👎21👍1

11 Jun 2026, 21:29 UTC≈1,200 viewsread 8 August 2026

Включил стрим https://www.twitch.tv/parzival_infms

31 May 2026, 16:35 UTC≈1,560 views2 reactionsread 8 August 2026
Photo

Через 30 минут стартует финальный игровой день Night Shift Open 😄 Все матчи BO3. Первыми играем мы, потом играют Lowkey W vs Melee Creeps, потом финал. Официальная трансляция: twitch.tv/deadlocknightshift

🏆2

Showing the 12 most recent of 13 posts we hold for @Parzival_INFMS. 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 — 130,283 of 1,478,351entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“Parzival” (@Parzival_INFMS), 661 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Parzival_INFMS.

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.