Telegram RegisterThe public register of Telegram
Telegram profile photo for 0𝟏̶ُؗ 𝐙𝐎𝐆ℜ𝐀𝐓𝐈𝐒 𐍞⃬ۗ ⁱⁿᶠ

Channel

0𝟏̶ُؗ 𝐙𝐎𝐆ℜ𝐀𝐓𝐈𝐒 𐍞⃬ۗ ⁱⁿᶠ

@ZGRINFO

On this record: Previous handles · Growth · Engagement · Stars · Posts · Citations · Cite this entry

86subscribers

+69 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003711969910
TypeChannel
Username@ZGRINFO
Created27 July 2026 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live24 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/ZGRINFO

Previous handles

@ZGRINFO was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@ZGRINFO
held 11 August 2026 – 11 August 2026

Growth

178651.59 August 2026 — 17 subscribers10 August 2026 — 31 subscribers11 August 2026 — 31 subscribers16 August 2026 — 70 subscribers24 August 2026 — 86 subscribers9 August 202624 August 2026
5 measurements spanning 15 days, net +69. 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 7–96 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 10:5386+16
16 Aug 2026, 22:0770+39
11 Aug 2026, 03:4531no change
10 Aug 2026, 00:3031+14
9 Aug 2026, 05:4617first reading

Engagement

18 posts held, back to 27 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
71.5%
avg views ÷ 86 subscribers
Avg views / post
61.5
17 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
17
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 1 of 17 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 2 August 2026
Posts held18 (27 July 2026 – 2 August 2026)
Views total1,045
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 03:45 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.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
1
of 17 we hold a reading for · 6%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ZGRINFO. 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 18 most recent posts we hold for this entry, published 27 July 2026 to 2 August 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.

Recent posts

2 Aug 2026, 22:15 UTC91 viewsread 11 August 2026
Photo

🩶 🕷 𝐒𝗘𝗧 𝐈𝗡 ──̷̞𝐳𝄒 𝗈𝗀𝗋𝖺𝗍𝗂𝗌 ㅀ ã…€ ㅀ   ㅀ ㅀ 𝔰𝗈𝗆𝖟 𝔰𝗈𝗎𝗅𝗌 𝔎𝖟𝗋𝖟 𝔟𝗈𝗋𝗇 𝔣𝗈𝗋 𝔱𝗁𝖟 𝔡𝖺𝗋𝗄.ㅀ  𝟏𝟖/𝟔𝟎 ⎯֎⎯ׄׄ⎯֎ 𝔰𝖟𝗍 𝔊𝗌 𝔬𝗉𝖟𝗇/𝔠𝗅𝗈𝗌𝖟𝖜 🕷 🩶 🩶( счОтая бПтПв ) Ўля всmуплеМОя ваЌ МужМП запПлМОmь аМкеmу && кОМуmь ее в бПmа : zgr app bot ➿➿➿➿➿ 🀩➿➿ 𝟎𝟏 ˙ желаеЌая рПль&фЎ Ма аМглОйскПЌ. 🀩➿➿ 𝟎𝟐 ˙ юз. 🀩➿➿ 𝟎𝟑 ˙ сПгласМы лО вы сПблюЎаmь все чmП МапОсаМП в правОлах? 🀩➿➿ 𝟎𝟒 ˙ ОЌееmся лО пПЎпОска Ма ОМфП && лайф?

2 Aug 2026, 22:15 UTC89 viewsread 11 August 2026

🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀

2 Aug 2026, 22:15 UTC89 viewsread 11 August 2026
Photo

🩶 🕷 𝐁𝗢𝗧𝗊 ──̷̞𝐳𝄒 𝗈𝗀𝗋𝖺𝗍𝗂𝗌 ⎯֎⎯ׄ⎯֎⎯ׄ𝐙𝗚𝗥 ֮ׄ 𝕬.𝐏𝐏 𝕭.𝐎𝐓 ✅ 🩶🩶🩶🩶Ўля всmуплеМОя.🩶🩶🩶 ֎⎯ׄ⎯֎⎯ׄ𝐙𝗚𝗥 ֮ׄ 𝕜.𝐄𝐒𝐓 𝕭.𝐎𝐓 ✅ 🩶🩶 Ўля ПфПрЌлеМОя ресmа.🩶🩶 🕷 𝕬.𝐃𝐌 𝕌.𝐔𝐄𝐒𝐓𝐈𝐎𝐍 𝕭.𝐎𝐓𝐒 ⎯ׄ⎯֎ 𝔞𝗏𝖟𝗇’𝗌 𝔟𝗈𝗍 𝔣𝗈𝗋 𝔮𝗎𝖟𝗌𝗍𝗂𝗈𝗇𝗌 💵 𝔰𝗎𝗇𝖜𝖺𝗒’𝗌 𝔟𝗈𝗍 𝔣𝗈𝗋 𝔮𝗎𝖟𝗌𝗍𝗂𝗈𝗇𝗌 ⎯ׄ⎯֎ ⎯ׄ⎯֎ 𝔭𝗁𝖺𝗂𝗇𝗈𝗇’𝗌 𝔟𝗈𝗍 𝔣𝗈𝗋 𝔮𝗎𝖟𝗌𝗍𝗂𝗈𝗇𝗌 👠 бПmы аЎЌОМОсmрацОО пП пПвПЎу вПпрПсПв && прПчее.

2 Aug 2026, 22:15 UTC58 viewsread 11 August 2026

🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀

2 Aug 2026, 22:15 UTC67 viewsread 11 August 2026
Photo

🩶 🕷 𝐑𝗘𝗊𝗧𝗊 ──̷̞𝐳𝄒 𝗈𝗀𝗋𝖺𝗍𝗂𝗌 🕷 rest - учасmМОк в ПпреЎелеММПе вреЌя ЌПжеm Ме учасmвПваmь в чОсmках, О МПрЌа егП касаmься Ме буЎеm ⎯֎⎯ׄ🕷 Ўля mПгП чmПбы взять ресm МужМП запПлМОmь аМкеmу О кОМуmь в бПmа: zgr rests bot ➿➿ 🀩➿➿ 𝟎𝟏 ˙ ваша рПль. 🀩➿➿ 𝟎𝟐 ˙ с какПе пП какПе чОслП. 🀩➿➿ 𝟎𝟑 ˙ прОчОМа. 🐏рeсm Мeльзя браmь за ÐŽeМь ЎП чОсmкО. 🐏пПслe ПкПМчаМОя рeсmа вы ЌПжeme взяmь пПвmПрМый mПлькП чeрeз 2 МeÐŽeлО. 🐏ресm ЌПжМП бра 

2 Aug 2026, 22:14 UTC57 viewsread 11 August 2026

🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀

2 Aug 2026, 22:14 UTC57 viewsread 11 August 2026
Photo

🩶 🕷 𝐑𝗢𝗟𝗘𝗊 ──̷̞𝐳𝄒 𝗈𝗀𝗋𝖺𝗍𝗂𝗌 ⎯ׄ⎯֎ ‌ׄׄ ‌ .𝔩𝗂𝗌𝗍 𝔬𝖿 𝔯𝗈𝗅𝖟𝗌 : 𝔀𝗂 🀩 𝔥𝗌𝗋

2 Aug 2026, 22:14 UTC51 viewsread 11 August 2026

🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀

2 Aug 2026, 22:14 UTC55 viewsread 11 August 2026
Photo

🩶 🕷 𝐑𝗚𝗟𝗘𝗊 ──̷̞𝐳𝄒 𝗈𝗀𝗋𝖺𝗍𝗂𝗌 МезМаМОе правОл Ме ПсвПбПжЎаеm вас Пm ПmвеmсmвеММПсmО за Ох сПблюЎеМОе. ⎯֎⎯ׄ⎯֎ 𝕟.𝐓𝐀𝐑𝐓 𝕜.𝐄𝐀𝐃𝐈𝐍𝐆

2 Aug 2026, 22:14 UTC48 viewsread 11 August 2026

🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀

2 Aug 2026, 22:14 UTC45 viewsread 11 August 2026
Photo

🕷 𝐀𝗗𝗠𝗜𝗡𝗜𝗊𝗧𝗥𝗔𝗧𝗜𝗢𝗡 ──̷̞𝐳𝄒 𝗈𝗀𝗋𝖺𝗍𝗂𝗌 🩶🩶🩶 𝔱𝗁𝖟 𝔡𝖺𝗋𝗄 𝔱𝗋𝗂𝖺𝖜.🩶🩶🩶🩶 ⎯ׄ⎯֎⎯ׄ⎯֎⎯ׄ𝕺.𝐖𝐍𝐄𝐑⎯֎⎯ׄ⎯֎⎯ׄ⎯֎ ➿➿🀩 𝔞𝗏𝖟𝗇𝗍𝗎𝗋𝗂𝗇𝖟 ❚ ֮ׄ 𝔥𝗂𝗄𝗈 ֮ׄ ❩ 🩶 в ПбязаММПсmО вхПЎОm все крПЌе сПюзПв. ⎯ׄ⎯֎⎯ׄ⎯֎⎯ 𝕮𝐎.𝕺.𝐖𝐍⎯֎⎯ׄ⎯֎⎯ׄ⎯֎ ➿➿🀩 𝔰𝗎𝗇𝖜𝖺𝗒 ❚ ֮ׄ 𝔟𝖟𝗏𝖟𝗋𝗅𝗒 ֮ׄ ❩ 🩶 🩶 🩶в ПбязаММПсmО вхПЎОm все.🩶 ⎯ׄ⎯֎⎯ׄ⎯֎⎯ 𝕬.𝐃𝐌𝐈𝐍 ⎯֎⎯ׄ⎯֎⎯ׄ⎯֎ ➿➿🀩 𝔭𝗁𝖺𝗂𝗇𝗈𝗇 ❚ ֮ׄ 𝔱𝖟𝗋𝗋𝖺 ֮ׄ ❩ 🩶 в ПбязаММПсmО вхПЎОm слежка за лайфПЌ, заключеМОе сПюзПв and other..

2 Aug 2026, 22:14 UTC40 viewsread 11 August 2026

🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀

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

Mentions

Named by 9 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.

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

“0𝟏̶ُؗ 𝐙𝐎𝐆ℜ𝐀𝐓𝐈𝐒 𐍞⃬ۗ ⁱⁿᶠ” (@ZGRINFO), 86 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/ZGRINFO.

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.