BIZTRAC BETA
Computer consultancy and computer facilities management activities

LAKEVIEW MANAGEMENT AS

Org. no. 914097185 Limited company (AS) Nittedal Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 104,000
Operating profit NOK 85,000
Equity NOK 461,000
Incorporated 2014
Share capital NOK 30,000

LAKEVIEW MANAGEMENT AS is registered as a limited company in Nittedal, Akershus with organisation number 914097185. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapet skal investere i virksomheter og eiendom, samt levere rådgivningstjenester”. The most recent filed accounts, for the 2025 financial year, show NOK 104,000 in revenue and NOK 85,000 in operating profit.

Key figures · 2025

Revenue
NOK 104,000
Operating profit
NOK 85,000
Equity
NOK 461,000
Est. value
NOK 577,000

Financial health · 2025

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

Who owns LAKEVIEW MANAGEMENT AS?

KNUT MORTEN AASRUD
LAKEVIEW MANAGEMENT AS
NOK 104,000 rev. · NOK 85,000 profit

LAKEVIEW MANAGEMENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAKEVIEW MANAGEMENT AS

Who owns LAKEVIEW MANAGEMENT AS?

KNUT MORTEN AASRUD is the largest registered owner, with 100.0%.

What is the revenue of LAKEVIEW MANAGEMENT AS?

LAKEVIEW MANAGEMENT AS had revenue of NOK 104,000 in 2025.

Who is the general manager of LAKEVIEW MANAGEMENT AS?

Knut Morten Aasrud is registered as general manager of LAKEVIEW MANAGEMENT AS.

Where is LAKEVIEW MANAGEMENT AS based?

LAKEVIEW MANAGEMENT AS has its business address in Nittedal.

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.