โVS SANKE๐น๐ท thanks to my editor ๐ @lovemee209
Signed lvm

Channel
@kanekiN1
On this record: Growth ยท Engagement ยท Reactions ยท Stars ยท Posts ยท Citations ยท Handles named that no longer answer ยท Cite this entry
741subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1002659642259 |
|---|---|
| Type | Channel |
| Username | @kanekiN1 |
| Created | Between 1 March 2025 and 31 July 2025โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/kanekiN1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 22:56 | 741 | -1 |
| 6 Aug 2026, 23:31 | 742 | first reading |
20 posts held, back to 19 April 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 3 August 2026 |
|---|---|
| Posts held | 20 (19 April 2026 โ 3 August 2026) |
| Views total | 633 |
| Reactions total | โ |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 6 Aug 2026, 23:31 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.
7,591 reactions across 17 posts, in 24 distinct kinds. The most used accounts for 12.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ฅ | 945 | 12.4% | |
| โค | 931 | 12.3% | |
| ๐ | 875 | 11.5% | |
| ๐ฏ | 856 | 11.3% | |
| ๐คฉ | 826 | 10.9% | |
| ๐ฅฐ | 766 | 10.1% | |
| ๐ | 758 | 9.99% | |
| ๐ | 745 | 9.81% | |
| โคโ๐ฅ | 731 | 9.63% | |
| customย 5296480809602023717 | 46 | 0.606% | |
| customย 5312051285820733327 | 36 | 0.474% | |
| โก | 19 | 0.25% | |
| ๐ | 12 | 0.158% | |
| ๐ | 10 | 0.132% | |
| ๐ | 9 | 0.119% | |
| ๐คฏ | 7 | 0.092% | |
| ๐ | 6 | 0.079% | |
| ๐ด | 3 | 0.04% | |
| ๐คฃ | 3 | 0.04% | |
| ๐ | 2 | 0.026% | |
| 4 further kinds | 5 | 0.066% |
Custom emoji. 2 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 17 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 7,591reactions 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 19 April 2026 to 3 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.
A paid reaction is a reader spending Telegram Stars โ bought with money โ on a post by @kanekiN1. 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 20 most recent posts we hold for this entry, published 19 April 2026 to 3 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.
โVS SANKE๐น๐ท thanks to my editor ๐ @lovemee209
Signed lvm
โVS PAHAN๐ท๐บ (1-0) thanks to my editor ๐ @lovemee209
Signed lvm
Video, posted without a caption
Signed ๐
666 EMPIRE MOBILE LIST ๐ 1- GENERAL๐ช๐ฌ| VISI๐ฆ๐ฑ 2- IDR๐ง๐ฆ| RAX๐ฎ๐ท| RAIWEN๐น๐ท 3- FAZ3A๐ต๐ธ| BADBOY๐ฒ๐ฆ 4- ALASKA๐ฉ๐ช| JNAZH๐ธ๐พ 5- SASUKE๐ง๐ฌ| CLOUD๐ฆ๐ซ 6- MONEYKEN๐ฐ๐ฌ| HADY๐ช๐ฌ 7- ALOK๐ฑ๐ง 8- WAYNE๐ท๐บ 9- ELDAB3๐ช๐ฌ 10- KANEKI๐น๐ท| STRIKER๐ช๐ฌ IBRAHIMGFX DESIGNER ๐จ
โค4customย 53120512858207333272๐1๐1๐ฅ1๐คฉ1๐คฏ1
Signed ๐
โVS BABL๐ฎ๐ถ 1-0 I threw a grenade even though I was AFK, and it got a kill without any info ๐
โค4โก2๐2๐ฅ2customย 53120512858207333272๐1๐1๐ค1
Signed ๐
โVS CODE7๐ซ๐ท Even though I was AFK, I'm better than everyone else ๐
๐2๐ฅ2โค1๐1๐คฉ1๐คฏ1customย 53120512858207333271
Signed ZYRON
โVS ARMAN๐ฆ๐ฟ 1-1 Bead eze player ๐จ๐ปโ๐ฆฏโโก๏ธ
โค3โก1๐1๐1๐ฅ1๐ค1๐1customย 53120512858207333271
Signed ๐
โWOOZY๐บ๐ฆ UNRIVALED TURNEMENT MACH ๐
customย 53120512858207333273โค2๐1๐ฅ1๐คฉ1๐คฏ1
Signed ๐
โvs KVARA๐ฌ๐ช She's accusing me of cheating ๐
โค10๐ฅ4๐3customย 52964808096020237172customย 53120512858207333272โก1๐1๐1
Signed ๏ธ ๐
โVS VOIN๐น๐ฏ (13-0) ๐ UNRIVALED TURNEMENT MACH ๐
customย 529648080960202371710customย 53120512858207333272โค1๐1๐ฅ1๐1
Signed ๏ธ ๐
โVS MSQNM๐ฐ๐ฟ 1-0
โค11๐ฅ5๐2๐1๐คฉ1customย 52964808096020237171customย 53120512858207333271
Signed ๏ธ ๐
โWAYNO๐ท๐บ 1-0
โค22๐ฅ5โก2๐2๐2๐1๐คฉ1customย 52964808096020237171
Showing the 12 most recent of 20 posts we hold for @kanekiN1. 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 โ 717,420 of 1,336,469entries 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.
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 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.
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.
@kanekiN1 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
References a handle that is not a live channel โ we have no record it ever was one.
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 7 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐๐๐โ (@kanekiN1), 741 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/kanekiN1.
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.