Telegram RegisterThe public register of Telegram

Channel

kjær

@n01me

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

80subscribers

+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-1003193339145
TypeChannel
Username@n01me
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/n01me

Growth

809 Aug 2026, 22:45 — 80 subscribers10 Aug 2026, 00:31 — 80 subscribers9 Aug 2026, 22:4510 Aug 2026, 00:31
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 79–81 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 00:3180no change
9 Aug 2026, 22:4580first reading

Engagement

13 posts held, back to 1 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
111.0%
avg views ÷ 80 subscribers
Avg views / post
88.8
5 posts measured
Reaction rate
21.2%
reactions ÷ views · ER floor
Posts in window
5
of 13 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 held13 (1 June 20265 August 2026)
Views total444
Reactions total94
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 22: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.

Reaction mix

344 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 39.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 539357749174498829513739.8%
custom 539344902497819493310931.7%
custom 53934489476687836279828.5%

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 13 of the 13 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 344reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 1 June 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.

Recent posts

5 Aug 2026, 23:55 UTC48 views20 reactionsread 9 August 2026
Photo

если вы не отправляете маме вашей любви фотографии с таким текстом то в чем смысл

custom 539357749174498829510custom 53934490249781949336custom 53934489476687836274

5 Aug 2026, 23:34 UTC49 views15 reactionsread 9 August 2026

совесть слишком странная штука. почему-то от нее страдают только те кто никоим образом ее испытывать не должен

custom 53935774917449882958custom 53934490249781949335custom 53934489476687836272

31 Jul 2026, 22:33 UTC101 views15 reactionsread 9 August 2026

с августом! не забудьте задернуть шторы!

custom 53934490249781949339custom 53934489476687836274custom 53935774917449882952

31 Jul 2026, 11:13 UTC107 views20 reactionsread 9 August 2026

в очередной раз убеждаюсь что самое главное умение в жизни это вовремя прикинуться дурачком

custom 539344894766878362710custom 53934490249781949335custom 53935774917449882955

27 Jul 2026, 18:59 UTC139 views24 reactionsread 9 August 2026
Photo

фотография хорошенького кроля 🩶

custom 539357749174498829515custom 53934490249781949336custom 53934489476687836273

9 Jul 2026, 19:40 UTC228 views26 reactionsread 9 August 2026

с утра очутилась в пробной версии экзистенциального кризиса подумав о желании вернуться в прошлое для исправления собственной жизни поначалу я так ярко загорелась этой идеей потому что мне действительно многое хотелось бы изменить. я бы обязательно купила кучу биткоинов по на тот момент мизерной цене чтобы сейчас ни о чем не париться. отвела бабушку к врачу чтобы предотвратить тот ужас который нам с семьей пришлось

custom 539357749174498829512custom 53934490249781949338custom 53934489476687836276

18 Jun 2026, 19:16 UTC231 views33 reactionsread 9 August 2026

удивительный (нет) фанфакт: когда в жизни все стабильно действительно хорошо желание писать куда-либо и кому-либо с каждым днем только уменьшается со скоростью света

custom 539357749174498829514custom 539344902497819493311custom 53934489476687836278

17 Jun 2026, 19:05 UTC235 views49 reactionsread 9 August 2026
Photo

словами не передать как сильно я люблю горы

custom 539344894766878362721custom 539357749174498829515custom 539344902497819493313

9 Jun 2026, 04:22 UTC215 views28 reactionsread 9 August 2026

Я КУПИЛА НАМ С TESORO MIO БИЛЕТЫ НА КОНЦЕРТ БТС В БАНГКОКЕ

custom 539357749174498829517custom 53934490249781949336custom 53934489476687836275

1 Jun 2026, 20:43 UTC226 views23 reactionsread 9 August 2026

а вы тоже ничего не выдаете в эфир днями или даже неделями а потом вас прорывает? /ш айм соу сорри

custom 539344902497819493312custom 53934489476687836277custom 53935774917449882954

1 Jun 2026, 20:42 UTC216 views21 reactionsread 9 August 2026

моя странная мечта которая не может быть осуществлена в жизни это фраза людей обо мне после смерти «у нее была действительно красивая улыбка». и речь вовсе не о зубах

custom 539357749174498829511custom 53934489476687836275custom 53934490249781949335

1 Jun 2026, 20:33 UTC207 views34 reactionsread 9 August 2026

возможно меня не так поймут но я достаточно хорошо и одновременно плохо поняла что настоящая дружба не может быть построена исключительно на общих интересах. да изначально большинство так и находит себе друзей с которыми потом может общаться достаточно долгое время и перенимать интересы друг друга продолжая подпитывать этот легкий дофамин но в конце концов наступает момент когда ты просто слушаешь человека и осознаеш

custom 539344894766878362714custom 539344902497819493311custom 53935774917449882959

Showing the 12 most recent of 13 posts we hold for @n01me. 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,033,018 of 1,345,403entries 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.

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.

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

“kjær” (@n01me), 80 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/n01me.

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.