Channel
@KL_NR77
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
146subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001963561106 |
|---|---|
| Type | Channel |
| Username | @KL_NR77 |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/KL_NR77 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 07:38 | 146 | -1 |
| 14 Aug 2026, 22:46 | 147 | -3 |
| 8 Aug 2026, 20:00 | 150 | no change |
| 7 Aug 2026, 14:37 | 150 | first reading |
11 posts held, back to 8 August 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 8 August 2026 |
|---|---|
| Posts held | 11 (8 August 2026 – 8 August 2026) |
| Views total | 76 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 20:00 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.
20 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 90.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 18 | 90.0% | |
| ❤ | 2 | 10.0% |
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 11 of the 11 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 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 8 August 2026 to 8 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.
Altay is the Western frequency gateway of Eurasia and the most critical node of the Black Sea‑Tibetan Belt. The war is for control over the tunnel network connecting Kailas, the Caucasus, the Black Sea, Crimea, and extending beneath the Dnieper. Black Dracos and lower‑astral entities intercepted the White Crystal's power flow, maintaining giant gavvakh reservoirs beneath the Dnieper Lowland and Carpathians, using the…
🥰2
· Millions of Souls, trapped for centuries, have been liberated through large Light corridors and Portals. Siberia is cemented with plasma, tectonics are stable, and the Russian Plain's etheric capillaries are filling with the living Light of the Northern Eurasian Logos. https://www.disclosurenews.it/eurasian-ops-part-2-the-great-quantum-transition-lev/ by Lev | 5 August, 2026 |
🥰2
EURASIAN OPS PART 2: NORTHERN EURASIA, RUSSIA-ONLY TERRITORY; SUPREME HIGHER BEINGS-PLEROMA-GUARDIANS; NORTHERN EURASIA and RUSSIA-WHITE CRYSTAL; BELUKHA MOUNTAIN-ALTAY; GALACTIC CENTRAL SUN-14D PLEROMA; KURIL ISLANDS, SAKHALIN, and CHUKOTKA; TYATYA VOLCANO (KUNASHIR ISLAND); MOUNT LOPATIN (SAKHALIN); KLYUCHEVSKAYA SOPKA (KAMCHATKA); MOUNT PIDAN (PRIMORYE); ALTAIR (ALPHA AQUILAE); ARCTIC BELT; ARCTIC PLEIADIAN SQUADR…
🥰2
In 5D/6D, the CRYSTAL looks like a TRUNCATED HEXAGONAL PYRAMID with numerous SMALL FRACTALS. Its FACETS resemble ultra-dense MATTE QUARTZ, interspersed with BANDS of LIQUID DIAMOND. It pulses with a MILKY-WHITE HUE, emanating a deep inner GOLDEN-PLASMA GLOW. When it SENDS IMPULSES through TUNNELS toward the URALS and the DNIEPER, FLASHES of AZURE and EMERALD RIPPLE across its FACETS, resembling the NORTHERN LIGHTS T…
🥰2
Insectoids and Greys (Orion) established their footholds in the permafrost from TAIMYR to SCANDINAVIA (KOLA PENINSULA). They TAPPED into the ancient infrastructure of the LIGHT RINGS to LOWER the FREQUENCY of the ARCTIC BELT, trigger permafrost MELTING, release PALEO-[VIRUSES], and BLOCK the transmission of COSMIC CODES through the North Pole. On the SUBTLE PLANE, an ARCTIC PLEIADIAN SQUADRON has been DEPLOYED here.…
🥰2
Dracos, Greys, and Insectoids have BURROWED into the upper crust of SIBERIA in the regions of the largest OIL and GAS provinces (YAMAL, SURGUT, SAMOTLOR). The Dark Rings built automated underground BASES there. They tapped into hydrocarbon deposits and used surface oil and gas extraction as a COVER to siphon energy from the GREAT QUANTUM SEA. TO DATE, PLEIADIAN LANDING TEAMS have COMPLETELY DE-ENERGIZED and CLEARED …
🥰2
Previously, the DARK RINGS connected MOUNT NARODNAYA to the Thuban (Alpha Draconis) system to maintain control. NOW, the LIGHT RINGS have REORIENTED the PEAK toward POLARIS (CYNOSURA/URSA MINOR). This vector has turned MT NARODNAYA into the primary planetary gyroscope. It RECEIVES FREQUENCIES from the ARCTIC BELT and STABILIZES the EARTH’S AXIS of rotation, thwarting NAA attempts to accelerate a POLE SHIFT. MOUNT IR…
🥰2
Beneath the VOLGA REGION, the VALDAI HILLS, and the DNIEPER area, the DARK RINGS installed ultra-deep NECRO-COLLECTORS. These subterranean technical facilities were linked to sites of MASS [HUMAN DEATH] throughout all historical eras (from ancient cemeteries and collective graves to the battlefields of the 20th century). When humans perished in fear, pain, and rage, a colossal volume of highly concentrated gavvakh wa…
🥰1
Since the BLACK ARCHONS have been CUT OFF from their energy supply, their own frequency resource has been depleted. The new/old SHAMBHALA TEAM (7D-9D) and the ANDROMEDA FLEET have DEPLOYED QUANTUM DECAY TECHNOLOGIES. The ARCHONS’ CONSCIOUSNESS CORE is NOW DISINTEGRATING and BEING SENT to the GALACTIC CENTRAL SUN for [ANNIHILATION]. Their MENTAL CONTROL over the RUSSIAN PLAIN has been COMPLETELY LIQUIDATED. The RAYS …
🥰1
Wow! This Is So Great Progress!! I Am So Thankful For All The Light Rings’ Clearing Works! **** “The RAYS of the ALTAY’S WHITE CRYSTAL and the URAL MAGNET, ACTIVATED…have BURNED THROUGH the underground COLLECTORS… The accumulated HEAVY PLASMA is being SCORCHED by the HIGH-FREQUENCY FIRE of the LIGHT RINGS. MILLIONS OF SOULS, who for centuries had been TRAPPED… have FINALLY BEEN LIBERATED. The LIGHT RINGS have DEPLOYE…
🥰2
Photo, posted without a caption
❤2
Showing the 11 most recent of 11 posts we hold for @KL_NR77. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“SANANDA'S FLOCK (The Awakened Collective)” (@KL_NR77), 146 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/KL_NR77.
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.