BIZTRAC BETA
General medical practice activities

KROKEN LEGEKONTOR AS

Org. no. 991933131 Limited company (AS) Tromsø Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 840,000
Equity NOK 970,000
Incorporated 2007
Employees 7
Share capital NOK 440,000

KROKEN LEGEKONTOR AS is registered as a limited company in Tromsø, Troms with organisation number 991933131. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2007 and has 7 registered employees. Registered share capital is NOK 440,000, divided into 440 shares. The company's stated purpose is: “Drift av legekontor, utleie av kontortjenester og utstyr for praktiserende leger, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 840,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 840,000
Equity
NOK 970,000
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns KROKEN LEGEKONTOR AS?

MARIA LORENTZEN
KROKEN LEGEKONTOR AS
NOK 4.9m rev. · NOK 840,000 profit

KROKEN LEGEKONTOR AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KROKEN LEGEKONTOR AS

Who owns KROKEN LEGEKONTOR AS?

MARIA LORENTZEN is the largest registered owner, with 25.0%.

What is the revenue of KROKEN LEGEKONTOR AS?

KROKEN LEGEKONTOR AS had revenue of NOK 4.9m in 2024.

Who is the general manager of KROKEN LEGEKONTOR AS?

Håkon Brustad is registered as general manager of KROKEN LEGEKONTOR AS.

Where is KROKEN LEGEKONTOR AS based?

KROKEN LEGEKONTOR AS has its business address in Krokelvdalen.

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.