Telegram RegisterThe public register of Telegram
Telegram profile photo for Nейт

Channel

Nейт

@natelvl3

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

667subscribers

-1 since we began measuring on 8 November 2026

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

Register entry

Telegram ID-1004447782394
TypeChannel
Username@natelvl3
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 November 2026
Last confirmed live9 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/natelvl3

Growth

667668667.58 Nov 2026, 06:47 — 668 subscribers8 Nov 2026, 07:22 — 668 subscribers9 Nov 2026, 13:07 — 667 subscribers8 Nov 2026, 06:479 Nov 2026, 13:07
3 measurements spanning 1 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 667–668 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Nov 2026, 13:07667-1
8 Nov 2026, 07:22668no change
8 Nov 2026, 06:47668first reading

Engagement

12 posts held, back to 31 October 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
69.7%
avg views ÷ 667 subscribers
Avg views / post
465
11 posts measured
Reaction rate
18.9%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 9 of 11 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 November 2026
Posts held12 (31 October 2026 – 7 November 2026)
Views total5,115
Reactions total687
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 07:22 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

687 reactions across 7 posts, in 18 distinct kinds. The most used accounts for 20.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 536189612934248928913820.1%
custom 534835277460828888713319.4%
custom 533464627554134045910515.3%
custom 5116175844837950263659.46%
custom 5291887402208495726578.30%
custom 5339227549652259358517.42%
custom 5359520462671984063405.82%
🆒253.64%
custom 5458705314964604869202.91%
custom 5377638425727898998131.89%
custom 5339378002356641156121.75%
custom 533704705918056640971.02%
custom 537063636202005964260.873%
custom 535707341793998969450.728%
custom 521973244985188489040.582%
custom 533957766250132903630.437%
custom 544952544084470324820.291%
custom 534373422877117042510.146%

Custom emoji. 17 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 are Telegram’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 9 of the 12 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 687 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 31 October 2026 to 7 November 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
76
across the posts below
Posts paid on
6
of 12 we hold a reading for · 50%
Most on one post
22
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @natelvl3. 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 12 most recent posts we hold for this entry, published 31 October 2026 to 7 November 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

Telegram’s own ‘edited’ marker: 0 of 12 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 12:55 UTC249 views76 reactions11 Starsread 8 November 2026
Photo

AU: SpiderDad читать в комментариях 🤩🤩🤩 в этой части так же присутствует пирс - персонаж дирола из его ау skulldad & glitchdaughter #spiderdad #peterparker part 5. part 4 . part 3 . part 2 . part 1

custom 533464627554134045945custom 537763842572789899810custom 53393780023566411569custom 53706363620200596426custom 53395776625013290363custom 54495254408447032482custom 53437342287711704251

5 Nov 2026, 21:49 UTC379 views151 reactions15 Starsread 8 November 2026
Photo

Читать в комментариях #winterdadwolfson часть 4 часть 3 часть 2 часть 1

custom 511617584483795026365custom 533464627554134045932🆒25custom 53483527746082888875custom 53570734179399896945custom 53595204626719840635custom 52197324498518848904custom 53392275496522593584

4 Nov 2026, 13:36 UTC418 views24 reactionsread 8 November 2026

арты/видео с нейтом и алексом, которые вы когда-то там мне делали (спасибо огромное кстати, мне приятно очень) я закинула в архив

custom 534835277460828888722custom 53618961293424892892

4 Nov 2026, 09:46 UTC458 views118 reactions5 Starsread 8 November 2026
Photo

#parksborn . trend ?

custom 536189612934248928958custom 534835277460828888724custom 535952046267198406315custom 53346462755413404597custom 54587053149646048697custom 52918874022084957265custom 53392275496522593582

3 Nov 2026, 18:04 UTC505 views130 reactions22 Starsread 8 November 2026
Photo

AU: SpiderDad читать в комментариях 🤩🤩🤩 в этой части так же присутствует упоминание пирс - персонаж дирола из его ау skulldad & glitchdaughter #spiderdad #peterparker part 4 . part 3 . part 2 . part 1

custom 536189612934248928970custom 534835277460828888726custom 533922754965225935819custom 54587053149646048696custom 53370470591805664094custom 53346462755413404592custom 53595204626719840632custom 52918874022084957261

2 Nov 2026, 23:59 UTC542 views78 reactions13 Starsread 8 November 2026
Photo

В крови по локоть « Питер впервые на собственной шкуре осознает, что быть героем - это не только спасать людей. Иногда приходится сталкиваться с тем, что будет съедать твою совесть и вину изнутри » ЧИТАТЬ ТУТ 2/4 #irondadspiderson 2 часть | 1 часть

custom 529188740220849572648custom 533464627554134045911custom 53392275496522593588custom 53595204626719840633custom 53618961293424892893custom 54587053149646048693custom 53483527746082888872

2 Nov 2026, 19:00 UTC507 views110 reactions10 Starsread 8 November 2026
Photo

#irondadspiderson

custom 534835277460828888754custom 533922754965225935818custom 535952046267198406315custom 53346462755413404598custom 53618961293424892895custom 54587053149646048694custom 52918874022084957263custom 53370470591805664093

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

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

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

“Nейт” (@natelvl3), 667 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/natelvl3.

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.