Telegram RegisterThe public register of Telegram
Telegram profile photo for PAC Protocol Portal

Channel

PAC Protocol Portal

@PACProtocol_chat

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

324subscribers

-9 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-1001530043866
TypeChannel
Username@PACProtocol_chat
Created2 September 2021measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/PACProtocol_chat

Growth

324333328.57 August 2026 — 333 subscribers8 August 2026 — 333 subscribers15 August 2026 — 332 subscribers22 August 2026 — 324 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net -9. 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 323–334 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 13:13324-8
15 Aug 2026, 00:43332-1
8 Aug 2026, 07:15333no change
7 Aug 2026, 22:53333first reading

Engagement

7 posts held, back to 2 September 2021the 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
14.5%
avg views ÷ 324 subscribers
Avg views / post
47.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 7 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 29 July 2026
Posts held7 (2 September 202129 July 2026)
Views total47
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:15 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.

Recent posts

29 Jul 2026, 12:36 UTC47 viewsread 8 August 2026
Forwarded from @DeFCoN_Network_NewsPhoto

🚀 DeFCoN Core v22.1.4 has been released This is a mandatory network upgrade for all participants. Wallets, masternodes and other services must upgrade before block 113,117. Why upgrade: • Deterministic recovery from the July 2026 chain split • Stronger chain validation and safer node behavior • Improved ChainLock signing and BLS security • Hardened bootstrap seed infrastructure • Dedicated Multisig GUI • Final rele

12 Jun 2026, 12:38 UTC111 viewsread 8 August 2026
Forwarded from @DeFCoN_Network_NewsPhoto

🚀 DeFCoN Core v22.1.3 Release A new DeFCoN Core version (v22.1.3) is now available on GitHub. Upgrading is recommended for all masternode operators to benefit from the latest stability and performance improvements, but it is NOT a mandatory protocol upgrade. 🔧 Masternode Update Helper For an easy and streamlined masternode upgrade, you can use the community Masternode Update Helper: https://github.com/MrMarsellus/d

26 Mar 2026, 12:26 UTCviews —

PAC Protocol Portal pinned «Hey everyone 👋 PAC Protocol has been abandoned by its original operators for a long time – but the idea is not dead. DeFCoN (DFCN) is the community‑driven successor project that picks up PAC’s original vision, massively improves it, and gives PAC holders…»

26 Mar 2026, 12:26 UTC207 viewsread 8 August 2026

Hey everyone 👋 PAC Protocol has been abandoned by its original operators for a long time – but the idea is not dead. DeFCoN (DFCN) is the community‑driven successor project that picks up PAC’s original vision, massively improves it, and gives PAC holders a new path forward. DeFCoN is built and run by former PAC community members who refused to accept that PAC would simply disappear. Our goal is to continue and evol

24 Jan 2022, 16:45 UTC≈7,390 viewsread 8 August 2026

Welcome to the PAC Protocol portal channel. This portal is here to protect the PAC Protocol community from bad actors. Make sure to solve the CAPTCHA below and gain access to our telegram. Kind Regards, PAC Protocol team

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

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.

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

“PAC Protocol Portal” (@PACProtocol_chat), 324 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/PACProtocol_chat.

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.