Telegram RegisterThe public register of Telegram

Channel

𝓷𝓪𝓫𝓲 - 𝓬𝓱♡𝓷. 🐈‍⬛

@nabi4chan

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

9subscribers

+1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003708934467
TypeChannel
Username@nabi4chan
CreatedBetween 1 February 2026 and 5 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/nabi4chan

Growth

898.512 Aug 2026, 03:47 — 8 subscribers12 Aug 2026, 15:47 — 8 subscribers12 Aug 2026, 18:54 — 9 subscribers12 Aug 2026, 03:4712 Aug 2026, 18:54
3 measurements taken within a single day, net +1. 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 8–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 18:549+1
12 Aug 2026, 15:478no change
12 Aug 2026, 03:478first reading

Engagement

11 posts held, back to 5 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
385.2%
avg views ÷ 9 subscribers
Avg views / post
34.7
3 posts measured
Reaction rate
18.4%
reactions ÷ views · ER floor
Posts in window
3
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. It is computed over the 2 of 3 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 11 August 2026
Posts held11 (5 June 202611 August 2026)
Views total104
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 15:47 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

50 reactions across 6 posts, in 13 distinct kinds. The most used accounts for 22.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53123519507113206361122.0%
custom 5019499171841836094510.0%
custom 5188612516984429097510.0%
custom 518844792524770723448.00%
custom 533699055029587850948.00%
custom 534399035485089513948.00%
custom 540674843415991595348.00%
custom 547458042891865397648.00%
custom 533707282039443214336.00%
custom 540710835671428790336.00%
custom 518832740846538333012.00%
custom 520870675770196498312.00%
🙏12.00%

Custom emoji. 12 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 6 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 50reactions 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 5 June 2026 to 11 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

11 Aug 2026, 22:48 UTC17 viewsread 12 August 2026
Forwarded from @admJSFPIARPhoto

🍡✨🔅🔅🔅🔅 ᛝ 🔅🔅🔅✨🍡 𝜗ৎ───💋💋💋── 𝜗ৎ 𑣲 Ищешь мью или вп? Ааа, или ты хочешь пропиарить себя? Тогда заходи к нам!! Здесь ты сможешь найти себе бесплатный пиар, может быть еще и друзей ꉂ(˵˃ ᗜ ˂˵) Наши другие каналы: @nishajsf и @ocenkijsf 🩷 Целую, милашка!

11 Aug 2026, 22:47 UTC50 views8 reactionsread 12 August 2026
Photo

𖹭 ニャー 𖹭

custom 51886125169844290973custom 51884479252477072342custom 54745804289186539762custom 51883274084653833301

8 Aug 2026, 20:51 UTC37 views8 reactionsread 12 August 2026
Photo

🤩 i survived bitch 🎀🎀🎀🎀🎀🎀🎀🎀 soooo да я пропала на месяц простите 😫 мотивация никогда не была чем-то чем я могла похвалиться, и я думаю оно заметно.. + этот месяц выдался не самым лучшим, что тоже сказалось на моей активности. надеюсь такое не будет случаться часто, а тут фотка с моего дня рождения (22.07), и ещё я постриглась как вам ✨

custom 53439903548508951394custom 51886125169844290972custom 54745804289186539762

3 Jul 2026, 16:37 UTC42 views8 reactionsread 12 August 2026
Forwarded from @jiraikeiryousancfPhoto

себе же ₍ᐢ..ᐢ₎ #ассоциации ♡ @jiraikeiryousancf #тейк ♡ @jirai_cf_bot

custom 53123519507113206364custom 51884479252477072342custom 53369905502958785091custom 54067484341599159531

12 Jun 2026, 01:21 UTC55 viewsread 12 August 2026
Forwarded from @admJSFPIARPhoto

🍡✨🔅🔅🔅🔅 ᛝ 🔅🔅🔅✨🍡 𝜗ৎ───💋💋💋── 𝜗ৎ 𑣲 Ищешь мью или вп? Ааа, или ты хочешь пропиарить себя? Тогда заходи к нам!! Здесь ты сможешь найти себе бесплатный пиар, может быть еще и друзей ꉂ(˵˃ ᗜ ˂˵) Наши другие каналы: @nishajsf и @ocenkijsf 🩷 Целую, милашка!

9 Jun 2026, 18:50 UTC65 views8 reactionsread 12 August 2026
Photo

🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 𝒚𝒐𝒖'𝒓𝒆 𝒕𝒉𝒆 𝒐𝒏𝒍𝒚 𝒐𝒏𝒆 𝒘𝒉𝒐'𝒔 𝒎𝒂𝒌𝒊𝒏𝒈 𝒎𝒆 𝒄𝒐𝒎𝒆 𝒕𝒐 𝒎𝒚 𝒔𝒊𝒏𝒇𝒖𝒍 𝒔𝒆𝒏𝒔𝒆𝒔 𝒊'𝒍𝒍 𝒏𝒆𝒗𝒆𝒓 𝒍𝒐𝒗𝒆 𝒂𝒏𝒚𝒐𝒏𝒆 𝒕𝒉𝒆 𝒔𝒂𝒎𝒆 𝒊'𝒍𝒍 𝒏𝒆𝒗𝒆𝒓 𝒇𝒆𝒆𝒍 𝒂𝒔𝒉𝒂𝒎𝒆𝒅 𝒐𝒇 𝒖𝒔𝒊𝒏𝒈 𝒚𝒐𝒖 𝒇𝒐𝒓 𝒑𝒍𝒆𝒂𝒔𝒖𝒓𝒆 🎀🎀 — старые фоьки 🎀

custom 50194991718418360943custom 53123519507113206363custom 54067484341599159532

5 Jun 2026, 20:50 UTC102 views9 reactionsread 12 August 2026
Photo

😀𝓜𝓪𝓽𝓬𝓱𝓲𝓷𝓰 ~ ♡ 𝔀𝓲𝓽𝓱 𝓱𝓸𝓼𝓱𝓲 🎀

custom 54071083567142879033custom 53369905502958785092custom 53370728203944321432🙏1custom 52087067577019649831

5 Jun 2026, 20:30 UTC135 views9 reactionsread 12 August 2026
Photo

🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 だってアナタ頭良いし (うん?) 変わらないし 足長いし (はい。) 面白いし (も~!) 顔も可愛いし さり気ないし 仕方ないし 溢れるオーラはまるで 🎀🎀

custom 53123519507113206364custom 50194991718418360942custom 53369905502958785091custom 53370728203944321431custom 54067484341599159531

Showing the 11 most recent of 11 posts we hold for @nabi4chan. 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,034,587 of 1,480,688entries 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.

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

“𝓷𝓪𝓫𝓲 - 𝓬𝓱♡𝓷. 🐈‍⬛” (@nabi4chan), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/nabi4chan.

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.