Telegram RegisterThe public register of Telegram

Channel

ДОДО ПРИНЦА

@PR1NC3channel

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

303subscribers

+6 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-1001436139209
TypeChannel
Username@PR1NC3channel
CreatedBetween 1 April 2019 and 30 September 2021— 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/PR1NC3channel

Growth

2973033007 Aug 2026, 15:31 — 297 subscribers8 Aug 2026, 08:04 — 297 subscribers8 Aug 2026, 12:43 — 303 subscribers7 Aug 2026, 15:318 Aug 2026, 12:43
3 measurements taken within a single day, net +6. 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 296–304 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:43303+6
8 Aug 2026, 08:04297no change
7 Aug 2026, 15:31297first reading

Engagement

19 posts held, back to 23 July 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
74.1%
avg views ÷ 303 subscribers
Avg views / post
224
19 posts measured
Reaction rate
9.47%
reactions ÷ views · ER floor
Posts in window
19
of 19 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 8 August 2026
Posts held19 (23 July 20268 August 2026)
Views total4,265
Reactions total404
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 08:04 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.

What this channel posts

Video runtime
5s
Average length
5s

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

404 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 523356391958225446711929.5%
custom 52086145919987431249824.3%
custom 53417659053889592896215.3%
custom 52064192065804905944310.6%
custom 5341278289161912341338.17%
custom 5341672000224001468338.17%
custom 5341436489987291366122.97%
custom 534174839910226134140.99%

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

Measured over the 19 most recent posts we hold, published 23 July 2026 to 8 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

8 Aug 2026, 04:16 UTC45 views12 reactionsread 8 August 2026

Так скажите, а Конвей говорил, что я пиявка? Говорил, да?..

custom 52086145919987431245custom 52335639195822544674custom 52064192065804905943

7 Aug 2026, 21:05 UTC74 views20 reactionsread 8 August 2026
Photo

СТРИМЫ на сегодня УСЁ 🍭 ОГРОМНОЕ СПАСИБО КАРТОШКА ЗА СТРИМ. Очень картошка посидели Потом ещё картошка и посидели у меня чуть-чуть (сорян, что не мог на долго подрубить, мой комп картошка и сильно лагал уже и грелся) НО Я НАШЁЛ КАК ЭТО ИСПРАВИТЬ. На некст стриме всё будет картошка. Всех жду (пн-вт) P.S. БВС иди на картошка. Люблю

custom 523356391958225446711custom 52086145919987431245custom 53417659053889592894

7 Aug 2026, 14:56 UTC105 views23 reactionsread 8 August 2026
Photo

Я ещё может быть после стрима с БВСом устрою микроподруб. Посидим, поболтаем, расскажу свои впечатления 😗

custom 534176590538895928911custom 52335639195822544677custom 52086145919987431245

7 Aug 2026, 11:39 UTC104 views17 reactionsread 8 August 2026
Video

А про это BVS знает? ТИШЕ, ТИШЕ, ТИШЕ.... 📩 Из предложки

custom 52064192065804905949custom 53414364899872913664custom 53417483991022613414

7 Aug 2026, 10:50 UTC82 views18 reactionsread 8 August 2026
Forwarded from @bvsytPhoto

Сегодня в 20:00 по МСК на твиче буду кашлять с Принцом и Лера Атак Состояние у меня всё ещё не ахти, но благо уже нет хотя бы жёсткого жара, попробую вам завести побольше гыгы гага🌟 А завтра стрим с шапкой, кстати, ещё. Весь месяц будет забит прикольным коллабами, которых вы не ожидали🥺

custom 52335639195822544678custom 52086145919987431245custom 53417659053889592895

6 Aug 2026, 14:49 UTC132 views17 reactionsread 8 August 2026
Photo

БУ! ИСПУГАЛИСЬ? Тише, тише не бойтесь Я если что не забыл пароль от аккаунта, я просто уже принялся за новый ролик 🍭 Решил провести эксперимент – за сколько я смогу сделать видео, если сильно постараюсь. Так что ждите Завтра хочу постримить (меня там один малютка умоляет с ним постримить, я не смог отказать…). После совместного стрима ещё соло подрублю поболтать 🤍

custom 523356391958225446710custom 53417659053889592895custom 52086145919987431242

2 Aug 2026, 20:03 UTC243 views21 reactionsread 8 August 2026
Photo

ОТЧЁТ ПО СТРИМУ: 📍 Построил наишикарнейший дом в Майне 📍 Сделал самую красивую тачку в NFS:MW 📍 Немного постримил настройки 📍 Послушал про какашки и словил рейд от Лагоды (жду ЗП за YepShop) 🍭 📍 Мистер BVS заглянул (а мы потом и ещё его видос глянули) Четыре часа стрима... Алло, иди постримь хотя бы два часа сначала...

custom 520861459199874312413custom 52335639195822544674custom 53417659053889592894

2 Aug 2026, 11:12 UTC240 views17 reactionsread 8 August 2026
Photo

К СТРИМУ ГОТОВ, ВРОДЕ ВСЁ НОРМ 🐈 Крч, сидел я часов до 4 утра всё настраивал... Вроде как всё норм работает. Стабильно Ещё щас сижу приколы некоторые доделываю На стриме всё расскажу Жду всех сегодня в 17:00 по МСК

custom 52335639195822544679custom 52086145919987431245custom 52064192065804905943

1 Aug 2026, 18:13 UTC241 views15 reactionsread 8 August 2026
Photo

Спасибо великим алгоритмам ютуба за еще одного бро с клевыми видосами и прикольным маскотом, которого я могу нарисовать У меня еще тгк есть: https://t.me/witch_of_flame Ахуеть, почему я криворукий, а вы нет... 📩 Из предложки · Отправил: kira_razgrom

custom 52086145919987431248custom 53417659053889592894custom 52335639195822544673

1 Aug 2026, 08:29 UTC203 views24 reactionsread 8 August 2026
Photo

СТРИМ завтра Надеюсь, он не пройдёт как прошлый – меня покусал Пихта, и был стрим настроек (он ещё и в конце стрима моему провайдеру провода перегрыз, и стрим вообще упал 😩) НО Я усердно готовлюсь к завтрашнему стриму. Хочу доделать то, что не завелось на прошлом, и попробую запустить одну игру (но это пока секрет... надеюсь, комп не взорвётся 😳) Прошлый стрим был короткий, так что постарюсь в этот раз посидеть с

custom 523356391958225446714custom 52086145919987431245custom 53417659053889592895

31 Jul 2026, 17:39 UTC216 views31 reactionsread 8 August 2026
Photo

😩

custom 534167200022400146821custom 52086145919987431245custom 53414364899872913665

31 Jul 2026, 08:58 UTC431 views23 reactionsread 8 August 2026

ВЫШЛО, ВЫШЛО ✌ https://youtu.be/jBFAyVDgvTg ДОЕДАЮ ЗА CONWAY Ну вот не мог он один день подождать?… Крч, видео на Ютубе. Кто не пишет комментарии, тот лох, а кто не ставит лайки – ещё и воняет В ВОСКРЕСЕНЬЕ СТРИМ, ВСЕХ ЖДУ!

custom 523356391958225446712custom 52086145919987431246custom 53417659053889592895

Showing the 12 most recent of 19 posts we hold for @PR1NC3channel. 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,231,380 of 1,345,403entries 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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

“ДОДО ПРИНЦА” (@PR1NC3channel), 303 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/PR1NC3channel.

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.