Telegram RegisterThe public register of Telegram

Channel

cover group: «NABI🦋»

@cgnabi

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

128subscribers

+0 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-1001912369716
TypeChannel
Username@cgnabi
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/cgnabi

Growth

1289 Aug 2026, 17:15 — 128 subscribers9 Aug 2026, 23:37 — 128 subscribers9 Aug 2026, 17:159 Aug 2026, 23:37
2 measurements taken within a single day. 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 127–129 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 23:37128no change
9 Aug 2026, 17:15128first reading

Engagement

11 posts held, back to 25 June 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
87.6%
avg views ÷ 128 subscribers
Avg views / post
112
6 posts measured
Reaction rate
20.2%
reactions ÷ views · ER floor
Posts in window
6
of 11 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 held11 (25 June 202629 July 2026)
Views total673
Reactions total136
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 17: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.

Reaction mix

223 reactions across 11 posts, in 22 distinct kinds. The most used accounts for 19.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4419.7%
custom 53075029541089729753415.2%
custom 5440627415363625916198.52%
💘146.28%
custom 5407064079896430001135.83%
custom 5440487880466115757125.38%
🍓125.38%
🔥125.38%
👎114.93%
🆒73.14%
🌭73.14%
custom 544063769751533527162.69%
👾52.24%
💯52.24%
💋41.79%
😍41.79%
❤‍🔥31.35%
🐳31.35%
😱31.35%
🥰31.35%
2 further kinds20.897%

Custom emoji. 5 of the rows above are 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 11 of the 11 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 223reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

29 Jul 2026, 09:00 UTC178 views18 reactionsread 9 August 2026

⬜⬜⬜⬜#NABI🦋 ⚪️🧨⬜ 🌾 📛 🌏📛 🔡🔡🔡🔡🔡 🔡🔡🟥 🔡🔡🔡🔡🔡🔡 📛 🌾 ✝️ 🧨 🟥🌏🌏 🌏📛 [перед тем,как приступить к просмотру,рекомендуем включить VPN] 💥https://youtu.be/t-xJrx9U4TQ 💥https://youtu.be/t-xJrx9U4TQ

custom 530750295410897297552💘2🔥2😍2🍓1🐳1custom 54404878804661157571

28 Jul 2026, 14:00 UTC71 views18 reactionsread 9 August 2026
Photo

⬜⬜⬜ #NABI🦋 🧨 🟥 📛📛 📛 🔡🔡🔡 🟥 🧨 🔡🔡🔡🔡🔡🔡 🔣KAORI🔣 ⚪️📛 🟥🧨 🟥 🟥 😂 ✝️ 💜 🌾🌾 🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏 editing by @stormacam

custom 53075029541089729754👎32🍓2💋2🆒2💘1custom 54404878804661157571

28 Jul 2026, 13:45 UTC151 views25 reactionsread 9 August 2026
Photo

⬜⬜⬜ #NABI🦋 🧨 🟥 📛📛 📛 🔡🔡🔡 🟥 🧨 🔡🔡🔡🔡🔡🔡 🔣LINA🔣 ⚪️📛 🟥🧨 🟥 🟥 😂 ✝️ 🦴 🌾🌾 🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏 editing by @stormacam

custom 53075029541089729755🆒43🍓3❤‍🔥2👎2💯2👾1

28 Jul 2026, 13:30 UTC61 views26 reactionsread 9 August 2026
Photo

⬜⬜⬜ #NABI🦋 🧨 🟥 📛📛 📛 🔡🔡🔡 🟥 🧨 🔡🔡🔡🔡🔡🔡 🔣YANIK🔣 ⚪️📛 🟥🧨 🟥 🟥 😂 ✝️ 💚 🌾🌾 🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏 editing by @stormacam

custom 53075029541089729757custom 544062741536362591643👎2👾2💘2custom 54404878804661157572❤‍🔥1

28 Jul 2026, 13:15 UTC117 views22 reactionsread 9 August 2026
Photo

⬜⬜⬜ #NABI🦋 🧨 🟥 📛📛 📛 🔡🔡🔡 🟥 🧨 🔡🔡🔡🔡🔡🔡 🔣ROXXY🔣 ⚪️📛 🕷🟥🧨 🟥 🟥 😂 ✝️ 🌾🌾 🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏 editing by @stormacam

5custom 53075029541089729754👎2👾2💘2custom 54406274153636259162🌭1🐳1

28 Jul 2026, 13:00 UTC95 views27 reactionsread 9 August 2026
Photo

⬜⬜⬜ #NABI🦋 🧨 🟥 📛📛 📛 🔡🔡🔡 🟥 🧨 🔡🔡🔡🔡🔡🔡 🔣STORMA🔣 ⚪️📛 🟥🧨 🟥 😭 🟥 😂 ✝️ 🌾🌾 🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏🌏 editing by @stormacam

custom 53075029541089729759🌭6😱3custom 544062741536362591621🍓1💋1💘1

27 Jun 2026, 15:47 UTC339 views16 reactionsread 9 August 2026

⬜⬜⬜ ⬜#NABI🦋 🤩🤩🤩🤩🤩 🤩🤩 🤩🤩🤩🤩🤩🤩 [перед тем,как приступить к просмотру,рекомендуем включить VPN] ⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://youtu.be/8aN2HvToLUA

custom 540706407989643000153🍓1💋1💘1🔥1😍1custom 54404878804661157571

25 Jun 2026, 11:30 UTC160 views24 reactionsread 9 August 2026
Photo

⬜⬜⬜⬜ #NABI🦋 ⬇️🔘🔘🔘🔘 CHOOSE YOUR CHARACTER 🔠🔠🔠🔠 🍁❤️ 🚗 S A N T O S B R A V O S ♥️LOADING…🐭 🌧️🌧️🌧️UJIN🌧️🌧️🌧️

8🔥5custom 54070640798964300014👎2💘1🤩1custom 54404878804661157571custom 54406274153636259161

25 Jun 2026, 11:25 UTC225 views14 reactionsread 9 August 2026
Photo

⬜⬜⬜⬜ #NABI🦋 ⬇️🔘🔘🔘🔘 CHOOSE YOUR CHARACTER 🔠🔠🔠🔠🔠🔠🔠 🍁❤️ 🚗 S A N T O S B R A V O S ♥️LOADING…🐭 🌧️🌧️🌧️ROXXY🌧️🌧️🌧️

5💘2custom 54406274153636259162🍓1🔥1custom 54070640798964300011custom 54404878804661157571custom 54406376975153352711

25 Jun 2026, 11:20 UTC125 views17 reactionsread 9 August 2026
Photo

⬜⬜⬜⬜ #NABI🦋 ⬇️🔘🔘🔘🔘 CHOOSE YOUR CHARACTER 🔠🔠🔠🔠 🍁❤️ 🚗 S A N T O S B R A V O S ♥️LOADING…🐭 🌧️🌧️🌧️YANIK🌧️🌧️🌧️

7custom 54406274153636259163custom 54070640798964300012🍓1💘1🥰1custom 54404878804661157571custom 54406376975153352711

25 Jun 2026, 11:15 UTC217 views16 reactionsread 9 August 2026
Photo

⬜⬜⬜⬜ #NABI🦋 ⬇️🔘🔘🔘🔘 CHOOSE YOUR CHARACTER 🔠🔠🔠🔠🔠🔠🔠🔠🔠 🍁❤️ 🚗 S A N T O S B R A V O S ♥️LOADING…🐭 🌧️🌧️🌧️LINA🌧️🌧️🌧️

5🔥3🥰2🍓1😍1custom 54070640798964300011custom 54404878804661157571custom 54406274153636259161

Showing the 11 most recent of 11 posts we hold for @cgnabi. 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 — 392,036 of 1,169,250entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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

“cover group: «NABI🦋»” (@cgnabi), 128 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/cgnabi.

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.