Telegram RegisterThe public register of Telegram

Channel

OwpenGram

@owpengram

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

618subscribers

+16 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-1003809842885
TypeChannel
Username@owpengram
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/owpengram

Growth

6026186107 Aug 2026, 18:56 — 602 subscribers8 Aug 2026, 03:05 — 602 subscribers8 Aug 2026, 09:34 — 618 subscribers7 Aug 2026, 18:568 Aug 2026, 09:34
3 measurements taken within a single day, net +16. 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 600–620 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 09:34618+16
8 Aug 2026, 03:05602no change
7 Aug 2026, 18:56602first reading

Engagement

20 posts held, back to 20 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
201.6%
avg views ÷ 618 subscribers
Avg views / post
1,250
20 posts measured
Reaction rate
0.423%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 14 of 20 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 7 August 2026
Posts held20 (20 July 20267 August 2026)
Views total24,916
Reactions total76
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:05 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

Video runtime
32s
Average length
32s

Measured directly from 1 video 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.

Reaction mix

76 reactions across 13 posts, in 11 distinct kinds. The most used accounts for 43.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3343.4%
😢1621.1%
👍1215.8%
👎56.58%
🥰33.95%
🔥22.63%
❤‍🔥11.32%
👏11.32%
💘11.32%
🖕11.32%
😎11.32%

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

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

7 Aug 2026, 10:06 UTC357 views5 reactionsread 8 August 2026

Also join our channel on OwpenGram! https://me.owpengram.org/owpengramchannel ———————— 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

4👎1

7 Aug 2026, 09:32 UTC386 views4 reactionsread 8 August 2026
Video

📹 Video Guide: Here is how the server registration works — simply enter your email address, put in the verification code you receive, and pick your desired name. 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

4

7 Aug 2026, 09:31 UTC393 viewsread 8 August 2026

🚀 New Client Releases & Server Back Online! Hey everyone! The server is fully up and running again! You can now log in using your email address or connect using the standard Telegram client. ⚠️ Note: To connect to the new server, please make sure to update your client to the latest version (vO6). Older versions will no longer work. Download the Latest Releases (vO6) We’ve released updated versions for both Deskt

7 Aug 2026, 07:18 UTC414 views13 reactionsread 8 August 2026
Photo

📝 Server and admin panel get changed a lot, that`s will be a huge release! 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

8👍2🥰2💘1

7 Aug 2026, 00:31 UTC488 views12 reactionsread 8 August 2026

📌 Important Announcement: A New Direction for the Project Hello everyone! 👋 We’ve made an important strategic decision regarding the future of the project, and we want to share the details with you. From a Full Telegram Clone to a Pure Communication Our initial goal of replicating every single Telegram feature showed us that the platform was becoming bloated with mechanics that have nothing to do with core commun

👍5👎41🖕1🥰1

6 Aug 2026, 19:16 UTC658 views18 reactionsread 8 August 2026

⚠️ Important Announcement: Test Server Shutdown Hello everyone, Please be advised that the test server will be turned off today at 24:00 (UTC+3). Unfortunately, we had to make this decision due to persistent technical issues combined with a high volume of rule violations by users on the server. We apologize for the inconvenience and appreciate your understanding as we focus on stabilizing our infrastructure and p

😢16❤‍🔥1👏1

31 Jul 2026, 13:38 UTC≈2,250 views4 reactionsread 8 August 2026

✅ Security Patch Deployed The issue with the email registration system has been fully resolved, and the fix is now live on the public test server. For those running your own instances, the fix is also available in the dev branch of the server repository on GitHub. Please update your servers accordingly! 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

4

31 Jul 2026, 12:44 UTC≈2,140 views0 reactionsread 8 August 2026

🔄 Server Restart Notice Please be advised that the public test server will be restarted shortly to apply the fix for the recent email registration vulnerability. We will notify you as soon as the services are back online. Thank you for your patience! 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

31 Jul 2026, 12:27 UTC≈1,910 viewsread 8 August 2026

🚨 Critical Security Notice: Email Registration Bug We have identified a critical bug in the email registration system. While our team is actively working on a permanent fix, we strongly advise all server administrators to take immediate action to secure their instances. Action Required: Please update your configuration files immediately. Change the default development authentication code (12345) in your .env file f

30 Jul 2026, 08:24 UTC≈1,650 viewsread 8 August 2026

📝 Server is back! 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

30 Jul 2026, 06:15 UTC≈1,600 views1 reactionsread 8 August 2026

📝 Happy Thursday, y'all! Hope you're all doing well. Unfortunately, we have a power outage in the region where our server is located, so our public test server is currently unreachable. We will inform you about power restoration with another post as soon as possible. Stay tuned! 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

1

25 Jul 2026, 12:36 UTC≈2,160 views2 reactionsread 8 August 2026

Quickfix for Desktop client! https://github.com/owpengram/owpengram-desktop-client/releases/tag/O5_1 📢 Channel: t.me/owpengram 💬 Chat: t.me/+TxE_kSBMxz0wZTgy

2

Showing the 12 most recent of 20 posts we hold for @owpengram. 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 — 1,148,093 of 1,345,403entries 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.

Mentions

Named by 1 registered channel — 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“OwpenGram” (@owpengram), 618 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/owpengram.

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.