BIZTRAC BETA
Other education activities

KNUAL AS

Org. no. 930179213 Limited company (AS) Åsnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 177,000
Operating profit NOK 102,000
Equity NOK 103,000
Incorporated 2022
Share capital NOK 30,000

KNUAL AS is registered as a limited company in Åsnes, Innlandet with organisation number 930179213. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kursvirksomhet, prosjektering innen bygg og anlegg, uteomhusarbeider, guiding og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 177,000 in revenue and NOK 102,000 in operating profit.

Key figures · 2025

Revenue
NOK 177,000
Operating profit
NOK 102,000
Equity
NOK 103,000
Est. value
NOK 420,000

Financial health · 2024

Liquidity
5.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.2%
Very good
Equity as a share of total capital

Who owns KNUAL AS?

KNUT ERIK AALBERG
KNUAL AS
NOK 177,000 rev. · NOK 102,000 profit

KNUAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KNUAL AS own?

KNUAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KNUAL AS

Who owns KNUAL AS?

KNUT ERIK AALBERG is the largest registered owner, with 100.0%.

What is the revenue of KNUAL AS?

KNUAL AS had revenue of NOK 177,000 in 2025.

Where is KNUAL AS based?

KNUAL AS has its business address in Flisa.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.