BIZTRAC BETA
Civil engineering activities

KI POWER ENGINEERING AS

Org. no. 932195682 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 229,000
Equity NOK 244,000
Incorporated 2023
Share capital NOK 30,000

KI POWER ENGINEERING AS is registered as a limited company in Asker, Akershus with organisation number 932195682. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen byggteknisk konsulentvirksomhet - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 229,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 229,000
Equity
NOK 244,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.2%
Good
Equity as a share of total capital

Who owns KI POWER ENGINEERING AS?

KNUT INGE AASE
KI POWER ENGINEERING AS
NOK 2.4m rev. · NOK 229,000 profit

KI POWER ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KI POWER ENGINEERING AS

Who owns KI POWER ENGINEERING AS?

KNUT INGE AASE is the largest registered owner, with 100.0%.

What is the revenue of KI POWER ENGINEERING AS?

KI POWER ENGINEERING AS had revenue of NOK 2.4m in 2024.

Who is the general manager of KI POWER ENGINEERING AS?

Knut Inge Aase is registered as general manager of KI POWER ENGINEERING AS.

Where is KI POWER ENGINEERING AS based?

KI POWER ENGINEERING AS has its business address in Asker.

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.