Channel
@P0RTALT
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
247subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003124857483 |
|---|---|
| Type | Channel |
| Username | @P0RTALT |
| Description | лс — @nierklein я рыдал от боли трусы были в крови |
| Created | Between 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/P0RTALT |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 22:45 | 247 | no change |
| 11 Aug 2026, 22:32 | 247 | first reading |
17 posts held, back to 22 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 1 pageof Telegram’s post history, 20 posts per page.
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 8 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 17 (22 July 2026 – 11 August 2026) |
| Views total | 3,105 |
| Reactions total | 333 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 22:45 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.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 2 videos 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.
333 reactions across 8 posts, in 12 distinct kinds. The most used accounts for 27.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🕊 | 91 | 27.3% | |
| 💘 | 66 | 19.8% | |
| 🍓 | 40 | 12.0% | |
| 🐳 | 35 | 10.5% | |
| custom 5330032789175704399 | 27 | 8.11% | |
| ☃ | 20 | 6.01% | |
| 👀 | 17 | 5.11% | |
| custom 5330351879475995710 | 8 | 2.40% | |
| custom 5330542614678640393 | 8 | 2.40% | |
| custom 5330175562478562830 | 7 | 2.10% | |
| custom 5330486457981247377 | 7 | 2.10% | |
| custom 5330541382023028557 | 7 | 2.10% |
Custom emoji. 6 of the rows above are 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 8 of the 17 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 333reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 22 July 2026 to 11 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @P0RTALT. 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 17 most recent posts we hold for this entry, published 22 July 2026 to 11 August 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.
🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🤨 ❤️Всем привет! этот коллаб на тематику "стили" в этом коллабе вы можете попробовать тот стиль в котором вы раньше хотели попрактиковаться либо же наоборот поработать в вашем любимом стиле! ваша задача взять то направление которые вы хотите и сделать с ним все что угодно,тут нет ограничений по выполнению работы ,главная чтоб ваша работа подходила под взятый "стиль" ❤️ что надо сделать чтоб поучавствова…
⠀⠀── ⠀NANALLY : Я РЫДАЛ ОТ БОЛИ! ТРУСЫ БЫЛИ В КРОВИ . . . НАГИЕВ : ПРАЙС ; #баннер ; #ава . ⠀⠀УВАЖАЕМЫЙ СУД! Они украли у нас ГОЛУБЯ! ──
🍓21💘21🕊21
Channel photo updated
Sticker, posted without a caption
( 🍇) 우리는 감정의 #баннер 바다이며, 사랑과 햇살의 축제입니다. осваиваю 2д/фигурный день 3
🍓19🕊14💘13🐳4
( ☔️) 사람들은 춤을 추고, 정신을 잃을 만큼 취해 있지만, #баннер 내일이면 다시 일상으로 돌아간다.
💘17🐳14🕊12
( 🩵 ) 당신은 새끼 #баннер 고양이와 순결만큼이나 귀엽습니다
🕊19🐳17💘15
( 🍬 ) 도움말 #banner 서비스의 새로운 시대 новая эра в анти хелпе 🖤
custom 533003278917570439912custom 53301755624785628307custom 53305413820230285577custom 53305426146786403936
( 🌊 ) 여름, #banner 태양, 더위 работа на какой-то летний конкурс я не помню уже
🕊11custom 533003278917570439910☃7👀4custom 53305426146786403932custom 53303518794759957101custom 53304864579812473771
🤩🤩🤩༓ — 🤩𝐂𝐎𝐌𝐏𝐄𝐓𝐈𝐓𝐈𝐎𝐍. ⌳ ▹ Тематический конкурс в честь новой эры и того, насколько мы всё-таки выросли. 🤩 Тематика: Китай, китайские вайбы. Канал, где вы можете найти пожелания к работе: @EVENTDESM К участию допускаются все работы, кроме стиля желе. 🤩🤩🤩🤩࿋ 𝐂𝐎𝐍𝐓𝐄𝐒𝐓 𝐓𝐄𝐑𝐌𝐒 🤩🤩🤩 🤩 Подписка на канал. 🤩🤩🤩 Пересыл этого поста в свой порт (для тех, у кого нет порта, — пересыл трём дизайнерам). Пересыл должен оставаться …
( 🪷 ) 비즈니스 비즈니스 #banner 비즈니스 заказ, но заказчик не был в сети больше недели, и не отвечал в течении двух🩵
☃5🕊4custom 53304864579812473773custom 53300327891757043992custom 53303518794759957102
Posted without readable text
Showing the 12 most recent of 17 posts we hold for @P0RTALT. 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.
Citation-graph rank — 597,799 of 1,183,361entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“PRESENCE ⋮ порт ниер ﹝🍇﹞” (@P0RTALT), 247 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/P0RTALT.
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.