Telegram RegisterThe public register of Telegram
Telegram profile photo for GO SToRE

Channel

GO SToRE

@PGXPstore

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

319subscribers

+3 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-1003008424829
TypeChannel
Username@PGXPstore
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/PGXPstore

Growth

3163203187 August 2026 — 316 subscribers7 August 2026 — 317 subscribers15 August 2026 — 320 subscribers21 August 2026 — 319 subscribers3197 August 202621 August 2026
4 measurements spanning 14 days, net +3. 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 315–321 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 15:18319-1
15 Aug 2026, 00:59320+3
7 Aug 2026, 18:50317+1
7 Aug 2026, 07:32316first reading

Engagement

18 posts held, back to 19 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
44.6%
avg views ÷ 319 subscribers
Avg views / post
142
10 posts measured
Reaction rate
2.40%
reactions ÷ views · ER floor
Posts in window
11
of 18 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 4 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held18 (19 July 20266 August 2026)
Views total1,424
Reactions total17
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 07:32 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

29 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 34.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 63256852916212876571034.5%
custom 5954257078208958451724.1%
custom 6213026899287871477620.7%
custom 5445315294857819326310.3%
custom 617898489830546573926.90%
custom 520874831580549940013.45%

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

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

6 Aug 2026, 08:58 UTC79 viewsread 7 August 2026

Play store 25k loaded available just loaded fresh 20% off fixed Usdt only 100/$ Dm - @fr0ntm4n

Signed 𝐅𝐑𝟎𝐍𝐓𝐌𝐀𝐍

5 Aug 2026, 08:03 UTC43 viewsread 7 August 2026
Forwarded from @PokemonGo_Event

Buying 1 SHINY LEGENDARY MINI PTC ACCOUNTS Price - 110 Rs Per Account DM - @X_BadBoy

Signed 𝙓_𝘽𝙖𝙙𝘽𝙤𝙮

4 Aug 2026, 08:47 UTC117 views2 reactionsread 7 August 2026

Lf museum pika /excavator pika ~ @D78785

custom 54453152948578193262

2 Aug 2026, 07:32 UTC172 views6 reactionsread 7 August 2026

Happy frimdship day 😅

custom 62130268992878714776

29 Jul 2026, 09:32 UTC150 viewsread 7 August 2026
Forwarded from @pokemongoshop69

Lucario Hat Pikachu Available Via Trade Only @RISHIPvP

Signed R I S H I

28 Jul 2026, 18:50 UTC112 viewsread 7 August 2026
Forwarded from @PokemonGo_Event

➡️Buying 🤑 1 SL MINI PTC ACCOUNTS Price - @80-90 depending on SL Dm - @X_BadBoy

Signed 𝙓_𝘽𝙖𝙙𝘽𝙤𝙮

28 Jul 2026, 14:47 UTC204 viewsread 7 August 2026

2x sold last available ✅

Signed 𝐅𝐑𝟎𝐍𝐓𝐌𝐀𝐍

28 Jul 2026, 14:37 UTC206 views3 reactionsread 7 August 2026

1K REDEEM CODE AVAILABLE IN CHEAP ✅ PRICE :- 800 /- ( FIX ) DM :- @FR0NTM4N 💖

custom 59542570782089584513

Signed 𝐅𝐑𝟎𝐍𝐓𝐌𝐀𝐍

27 Jul 2026, 16:37 UTC213 views6 reactionsread 7 August 2026

This channel is only for content related to Pokémon GO, and any other content will be deleted to avoid any misunderstanding. If there is still any problem, discuss with @PanzerXZ_860✅ Appropriate posts by admins will be appreciated. ~ @PanzerXZ_860✅

custom 63256852916212876573custom 61789848983054657392custom 52087483158054994001

26 Jul 2026, 16:08 UTC128 viewsread 7 August 2026
Forwarded from @TheSellingHubPhoto

Available via paid trade Dm @D78785 for information 🥲😎

Signed D.

26 Jul 2026, 03:39 UTC170 views1 reactionsread 7 August 2026
Forwarded from @PGxJMSTORE

Koi key dedo 1 m 2d urgent

custom 54453152948578193261

Signed MEW RDX

Showing the 12 most recent of 18 posts we hold for @PGXPstore. 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 — 180,779 of 1,602,822entries 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

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

“GO SToRE” (@PGXPstore), 319 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/PGXPstore.

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.