BIZTRAC BETA
General medical practice activities

LILLEVANN DRIFT AS

Org. no. 930998680 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 1.1m
Equity NOK 984,000
Incorporated 2023
Share capital NOK 30,000

LILLEVANN DRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 930998680. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive legevirksomhet samt investering i andre selskaper for drifts- og økonomiske formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 1.1m
Equity
NOK 984,000
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns LILLEVANN DRIFT AS?

MAGNUS ESPOLIN JOHNSON
LILLEVANN DRIFT AS
NOK 3.7m rev. · NOK 1.1m profit

LILLEVANN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LILLEVANN DRIFT AS own?

LILLEVANN DRIFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LILLEVANN DRIFT AS

Who owns LILLEVANN DRIFT AS?

MAGNUS ESPOLIN JOHNSON is the largest registered owner, with 100.0%.

What is the revenue of LILLEVANN DRIFT AS?

LILLEVANN DRIFT AS had revenue of NOK 3.7m in 2025.

Who is the general manager of LILLEVANN DRIFT AS?

Magnus Espolin Johnson is registered as general manager of LILLEVANN DRIFT AS.

Where is LILLEVANN DRIFT AS based?

LILLEVANN DRIFT AS has its business address in Oslo.

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.