Telegram RegisterThe public register of Telegram
Telegram profile photo for PUDEL Founders

Channel

PUDEL Founders

@PUDEL_Game

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

734subscribers

-8 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-1001622424458
TypeChannel
Username@PUDEL_Game
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/PUDEL_Game

Growth

7347427387 August 2026 — 742 subscribers8 August 2026 — 742 subscribers16 August 2026 — 736 subscribers24 August 2026 — 734 subscribers7 August 202624 August 2026
4 measurements spanning 17 days, net -8. 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 733–743 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 17:08734-2
16 Aug 2026, 15:48736-6
8 Aug 2026, 02:03742no change
7 Aug 2026, 23:08742first reading

Engagement

19 posts held, back to 25 May 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
5.50%
avg views ÷ 734 subscribers
Avg views / post
40.3
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
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 28 July 2026
Posts held19 (25 May 202628 July 2026)
Views total121
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:03 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

28 Jul 2026, 13:38 UTCviews —

PUDEL Founders pinned «Each critical change is inspected before implementation and verified again after deployment. This process protects the systems that matter most: user data, balances, rewards, inventory state, payment flows, and production infrastructure. --- PVERSE is being…»

28 Jul 2026, 13:37 UTC47 viewsread 8 August 2026

Each critical change is inspected before implementation and verified again after deployment. This process protects the systems that matter most: user data, balances, rewards, inventory state, payment flows, and production infrastructure. --- PVERSE is being built as one internally controlled architecture. Its account systems, authentication layer, game services, inventory, ledgers, real-time infrastructure, payme

Signed ZOHz Systems Builder

28 Jul 2026, 13:37 UTC37 viewsread 8 August 2026

# PVERSE Development Update PVERSE is being built as an integrated platform where game systems, identity, payments, real-time infrastructure, internal economies, and blockchain-based ownership operate as one connected architecture. Most of the development work has remained private while the core systems were being built. With a substantial part of the foundation now in place, this update provides a clearer view of

Signed ZOHz Systems Builder

28 Jul 2026, 13:37 UTC37 viewsread 8 August 2026

The platform currently includes or is being prepared for: * The official website * Game dashboard and lobby * Account and security settings * Inventory and equipment interfaces * Store and asset interfaces * Real-time game controls * Future market, guild, chat, mission, and seasonal systems The interface is being developed for both desktop and mobile environments. The broader platform handles navigation, identity,

Signed ZOHz Systems Builder

21 Jun 2026, 14:58 UTCviews —

PUDEL Founders pinned «• The core backend has been redesigned into separated system layers instead of one mixed backend. • The identity and account layer is being kept separate from the game and asset logic. • The game backend is being organized around command-style flows instead…»

21 Jun 2026, 14:58 UTCviews —

PUDEL Founders pinned «Hello everyone. I want to give a clear and honest update on the current state of PVERSE. First, PVERSE has not been abandoned. There has been a long period of silence, but that silence was not inactivity. I chose not to keep posting shallow updates just…»

21 Jun 2026, 14:58 UTCviews —

PUDEL Founders pinned «• Finalizing the presale and payment accounting flow • Completing the Genesis and Founders handling • Completing the shop and subscription purchase system • Connecting PCR payment flow into actual user-facing purchases • Connecting asset, inventory, item,…»

21 Jun 2026, 14:58 UTC63 viewsread 8 August 2026

Hello everyone. I want to give a clear and honest update on the current state of PVERSE. First, PVERSE has not been abandoned. There has been a long period of silence, but that silence was not inactivity. I chose not to keep posting shallow updates just to create noise. Instead, I focused on rebuilding the project at a deeper level, because PVERSE needs to become something that can actually operate, scale, and sur

Signed ZOHz Systems Builder

21 Jun 2026, 14:58 UTC82 viewsread 8 August 2026

• The core backend has been redesigned into separated system layers instead of one mixed backend. • The identity and account layer is being kept separate from the game and asset logic. • The game backend is being organized around command-style flows instead of random direct updates. • The ledger layer is becoming the source of truth for balances, rewards, and asset-related movements. • The event-outbox flow has been

Signed ZOHz Systems Builder

21 Jun 2026, 14:58 UTC121 viewsread 8 August 2026

• Finalizing the presale and payment accounting flow • Completing the Genesis and Founders handling • Completing the shop and subscription purchase system • Connecting PCR payment flow into actual user-facing purchases • Connecting asset, inventory, item, and reward logic into the user experience • Stabilizing the viewer layer so users can clearly see their balances, assets, inventory, and progress • Preparing the 10

Signed ZOHz Systems Builder

7 Jun 2026, 06:58 UTCviews —

PUDEL Founders pinned «PVERSE Genesis Closed Beta — Coming Soon We are preparing to open the first PVERSE Genesis Closed Beta for eligible Genesis Presale participants. The initial Closed Beta access will be available to Genesis Presale participants with a total purchase amount…»

7 Jun 2026, 06:58 UTC116 viewsread 8 August 2026

PVERSE Genesis Closed Beta — Coming Soon We are preparing to open the first PVERSE Genesis Closed Beta for eligible Genesis Presale participants. The initial Closed Beta access will be available to Genesis Presale participants with a total purchase amount of $30 or more. This phase is intended to validate the core gameplay flow, mining loop, account systems, balance, server stability, and early user experience bef

Signed ZOHz Systems Builder

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

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

“PUDEL Founders” (@PUDEL_Game), 734 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/PUDEL_Game.

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.