Рен & Иван ♪ он моггает
custom 540476016494958841195custom 531692287395105494165custom 524693295018387677240custom 540451221648759083319custom 52132019134236184605custom 54048682950462344105custom 52426885260629908232custom 53799779974932180502

Channel
@nikkla1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
478subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003710144027 |
|---|---|
| Type | Channel |
| Username | @nikkla1 |
| Created | Between 1 February 2026 and 21 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/nikkla1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:36 | 478 | +3 |
| 8 Aug 2026, 04:35 | 475 | no change |
| 7 Aug 2026, 13:15 | 475 | first reading |
20 posts held, back to 21 May 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (21 May 2026 – 5 August 2026) |
| Views total | 22,041 |
| Reactions total | 1,815 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 04:35 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
3,980 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 28.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5404760164949588411 | 1,151 | 28.9% | |
| custom 5404512216487590833 | 1,031 | 25.9% | |
| custom 5316922873951054941 | 845 | 21.2% | |
| custom 5253783779503278974 | 533 | 13.4% | |
| custom 5287336295947842306 | 222 | 5.58% | |
| custom 5408946147450451861 | 94 | 2.36% | |
| custom 5424989581172829918 | 49 | 1.23% | |
| custom 5246932950183876772 | 40 | 1.01% | |
| custom 5404868295046234410 | 6 | 0.151% | |
| custom 5213201913423618460 | 5 | 0.126% | |
| custom 5242688526062990823 | 2 | 0.05% | |
| custom 5379977997493218050 | 2 | 0.05% |
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 20 of the 20 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 3,980reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 May 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.
Рен & Иван ♪ он моггает
custom 540476016494958841195custom 531692287395105494165custom 524693295018387677240custom 540451221648759083319custom 52132019134236184605custom 54048682950462344105custom 52426885260629908232custom 53799779974932180502
скоро некст парт
custom 531692287395105494155custom 540476016494958841123custom 540894614745045186116custom 54045122164875908336custom 54249895811728299184custom 52873362959478423062custom 52537837795032789741
баловство новыми кистями Σ੧(❛□❛✿)
custom 5404512216487590833104custom 525378377950327897468custom 531692287395105494153custom 54249895811728299189custom 52873362959478423067custom 54089461474504518612custom 54048682950462344101
грустное я их очень люблю (゚´ω`゚) тиктоок
custom 5404760164949588411126custom 540451221648759083373custom 528733629594784230650custom 540894614745045186118custom 54249895811728299186custom 53169228739510549413custom 52537837795032789742
hii =(^.^)= спасибо за 4 сотни!!! давайте в честь этого парочку реквестов по алнст
custom 540451221648759083392custom 540476016494958841177custom 525378377950327897447custom 531692287395105494118custom 54089461474504518614custom 54249895811728299183custom 52873362959478423062
привет ♡
custom 525378377950327897448custom 540451221648759083340custom 540476016494958841115custom 53169228739510549416custom 52873362959478423063custom 54089461474504518611custom 54249895811728299181
коллаба с чудесной ван ♡(๑╹ω╹๑ )
custom 5404760164949588411106custom 540451221648759083378custom 531692287395105494148custom 525378377950327897415custom 52873362959478423063custom 54249895811728299181
сомневаюсь (актер ау (=^▽^)σ)
custom 5404760164949588411110custom 540451221648759083369custom 540894614745045186141custom 531692287395105494113custom 52873362959478423063custom 52537837795032789742custom 54249895811728299181
Пробник 🌟🌟 #alnst
custom 540451221648759083349custom 540476016494958841130custom 531692287395105494115custom 525378377950327897410custom 52873362959478423061custom 54249895811728299181
ребята, у нас пропали реакты, будет очень круто если кто-нибудь поделится голосами! (๑❛ᴗ❛๑)
custom 540476016494958841153custom 531692287395105494125custom 540451221648759083320custom 52537837795032789745custom 54249895811728299182custom 52873362959478423061
ойей что это там ~(๑•ૅㅁ•๑)
custom 5316922873951054941140custom 540451221648759083389custom 540476016494958841167custom 525378377950327897416custom 52873362959478423068custom 54249895811728299187
смешные джокэмо на фоне ЖЕСТИ в зомби стейдже Σ( ̄。 ̄) (спасибо огромное за 300 подпищ!!)
custom 525378377950327897496custom 531692287395105494172custom 540476016494958841153custom 540451221648759083325custom 52873362959478423061custom 54249895811728299181
Showing the 12 most recent of 20 posts we hold for @nikkla1. 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 — 222,012 of 1,176,251entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“n i k k l a 💿˚⁺˳✧” (@nikkla1), 478 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/nikkla1.
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.