Telegram RegisterThe public register of Telegram
Telegram profile photo for NeN2914¹⁸⁺

Channel

NeN2914¹⁸⁺

@nnnnnennnna

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

376subscribers

-12 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001941093758
TypeChannel
Username@nnnnnennnna
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/nnnnnennnna

Growth

3763883826 August 2026 — 388 subscribers6 August 2026 — 388 subscribers14 August 2026 — 376 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -12. 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 374–390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 17:07376-12
6 Aug 2026, 20:05388no change
6 Aug 2026, 17:33388first reading

Engagement

14 posts held, back to 16 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
110.2%
avg views ÷ 376 subscribers
Avg views / post
415
13 posts measured
Reaction rate
19.6%
reactions ÷ views · ER floor
Posts in window
13
of 14 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 5 August 2026
Posts held14 (16 July 20265 August 2026)
Views total5,389
Reactions total1,058
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 20: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.

Reaction mix

1,127 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 35.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 519717758801074310740535.9%
custom 524039472576412020420017.7%
custom 542951126690747102418016.0%
custom 535964773114291759713111.6%
custom 533465399359757077012110.7%
custom 5312127796368152750907.99%

Custom emoji. Every row above is a 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 14 of the 14 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 1,127reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Telegram Stars

Stars received
14
across the posts below
Posts paid on
4
of 14 we hold a reading for · 29%
Most on one post
6
single highest reading

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

5 Aug 2026, 15:07 UTC87 views12 reactionsread 6 August 2026
Forwarded from @gagarina_writePhoto

Внимание на котика! Это 🤩🤩🤩🤩🤩🤩🤩🤩 Вас 600! Шесть сотен роднулек! Спасибо вам большое за подписку, за поддержку моего творчества! 💓 Как и обещала: в честь любимых подписчиков, объявляю розыгрыш бесплатной фотосессии ‼️ В ЧЁМ СУТЬ: Разыгрываю бесплатное участие в индивидуальном проекте, по вашей идее или с предоставлением полностью готового образа и реквизита. Мои услуги фотографа или видеографа бесплатно! Вариант

custom 53596477311429175978custom 54295112669074710243custom 51971775880107431071

4 Aug 2026, 14:49 UTC318 views80 reactions2 Starsread 6 August 2026

Posted without readable text

custom 519717758801074310738custom 542951126690747102418custom 524039472576412020416custom 53121277963681527503custom 53346539935975707703custom 53596477311429175972

3 Aug 2026, 11:15 UTC191 views80 reactions1 Starread 6 August 2026

Posted without readable text

custom 535964773114291759735custom 542951126690747102421custom 519717758801074310720custom 52403947257641202042custom 53346539935975707702

31 Jul 2026, 21:46 UTC310 views101 reactionsread 6 August 2026
Photo

Мне кажется начало артблока выглядит именно так

custom 531212779636815275046custom 519717758801074310729custom 542951126690747102420custom 53346539935975707704custom 52403947257641202041custom 53596477311429175971

31 Jul 2026, 08:33 UTC509 views98 reactions5 Starsread 6 August 2026
Photo

Dont keep following 🌟

custom 519717758801074310747custom 524039472576412020429custom 542951126690747102422

30 Jul 2026, 17:13 UTC380 views100 reactionsread 6 August 2026

Posted without readable text

custom 524039472576412020445custom 533465399359757077026custom 531212779636815275021custom 51971775880107431076custom 53596477311429175972

29 Jul 2026, 07:32 UTC327 views94 reactionsread 6 August 2026

Posted without readable text

custom 519717758801074310744custom 524039472576412020426custom 533465399359757077020custom 53121277963681527504

24 Jul 2026, 20:08 UTC522 views95 reactions6 Starsread 6 August 2026
Photo

Понятия не имею

custom 524039472576412020445custom 519717758801074310727custom 533465399359757077018custom 54295112669074710243custom 53596477311429175972

23 Jul 2026, 17:59 UTC557 views98 reactionsread 6 August 2026
Photo

⠀ ⠀ 🔠🔠🔠🔠 ⠀ 🔠🔠🔠🔠🔠🔠🔠🔠 ⠀ ❌❌❌ 💫 Photographer 💫 Cosplayer ➖➖➖➖➖➖➖➖➖➖➖ ⠀ #Gachiakuta #RudoSurebrec

custom 542951126690747102442custom 519717758801074310731custom 524039472576412020419custom 53346539935975707705custom 53596477311429175971

22 Jul 2026, 14:10 UTC512 views91 reactionsread 6 August 2026

Posted without readable text

custom 519717758801074310742custom 535964773114291759724custom 542951126690747102419custom 53346539935975707706

22 Jul 2026, 12:51 UTC414 views60 reactionsread 6 August 2026
Photo

Через 5 минут их всех посадили приносите кириешки Фото от Анечки

custom 519717758801074310729custom 533465399359757077014custom 542951126690747102414custom 53596477311429175973

21 Jul 2026, 11:15 UTC759 views84 reactionsread 6 August 2026
Photo

🤩🤩 🤩🤩 🤩 🌟🌟🌟🌟🌟 🤩 ⠀ ⠀ 🌟🌟🌟🌟🌟🌟 •••••••••••• 𝘊𝘳𝘢𝘤𝘬 𝘣𝘢𝘣𝘺, 𝘺𝘰𝘶 𝘥𝘰𝘯'𝘵 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘺𝘰𝘶 𝘸𝘢𝘯𝘵 𝘉𝘶𝘵 𝘺𝘰𝘶 𝘬𝘯𝘰𝘸 𝘵𝘩𝘢𝘵 𝘺𝘰𝘶 𝘩𝘢𝘥 𝘪𝘵 𝘰𝘯𝘤𝘦 ••••••••••••• 😀😀😀😀😀😀😀😀 😀😀😀😀😀😀😀😀 🤍Ph/rt🤍 #TamsyCaines #Gachiakuta

custom 519717758801074310738custom 533465399359757077023custom 531212779636815275015custom 54295112669074710247custom 53596477311429175971

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 7,711 of 1,481,243entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

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 12 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“NeN2914¹⁸⁺” (@nnnnnennnna), 376 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/nnnnnennnna.

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.