2 measurements taken within a single day. 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 60â62 and does not start at zero.
Measurement log â every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Sept 2026, 14:22
61
no change
16 Sept 2026, 13:47
61
first reading
Engagement
16 posts held, back to 26 August 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 page of Telegramâs post history, 20 posts per page.
ERR · 30 days
101.0%
avg views ÷ 61 subscribers
Avg views / post
61.6
16 posts measured
Reaction rate
33.0%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 12 of 16 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 16 September 2026
Posts held
16 (26 August 2026 â 16 September 2026)
Views total
986
Reactions total
270
Forwards / comments
not exposed by the public surface â not measured, not estimated
Readings taken
16 Sept 2026, 14:22 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
Photos
54
Links
47
Lifetime counters from Telegramâs own channel header, read 16 September 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.
Reaction mix
270 reactions across 12 posts, in 25 distinct kinds. The most used accounts for 12.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5429512125900950993
34
12.6%
custom 5433848500976645638
17
6.30%
custom 5326029634842687131
16
5.93%
custom 5314563979127846651
14
5.19%
custom 5426969793024526319
14
5.19%
custom 5429378067086737541
14
5.19%
custom 5314399619319362323
13
4.81%
custom 5314679225985300528
13
4.81%
custom 5314704742386005394
13
4.81%
custom 5429235740460487118
10
3.70%
custom 5429309377674774470
10
3.70%
custom 5433813496993181991
10
3.70%
custom 5314778628708395958
9
3.33%
custom 5429466015132061315
9
3.33%
custom 5314374223177741629
8
2.96%
custom 5427158011376336524
8
2.96%
custom 5211033697968483228
7
2.59%
custom 5427262018304377608
7
2.59%
custom 5429350690965199274
7
2.59%
custom 5429607147757407411
7
2.59%
5 further kinds
30
11.1%
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 are 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 12 of the 16 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 270 reactions in total: the kind of figure the paragraph above means by âa reaction total printed elsewhere on the pageâ.
Measured over the 16 most recent posts we hold, published 26 August 2026 to 16 September 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
56
across the posts below
Posts paid on
3
of 16 we hold a reading for · 19%
Most on one post
50
single highest reading
A paid reaction is a reader spending Telegram Stars â bought with money â on a post by @PortExe. 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 16 most recent posts we hold for this entry, published 26 August 2026 to 16 September 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.
Showing the 12 most recent of 16 posts we hold for @PortExe. 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.
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 2 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.
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 16 September 2026 â this
entry's latest reading, not the date you are reading this.
âðð«ðð¥.m ððð ç¥â (@PortExe), 61 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/PortExe.
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.
