BIZTRAC BETA
General medical practice activities

MAUDBUKTA LEGEKONTOR AS

Org. no. 999606253 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK −20,000
Equity NOK 223,000
Incorporated 2013
Share capital NOK 45,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−20k kr).

MAUDBUKTA LEGEKONTOR AS is registered as a limited company in Asker, Akershus with organisation number 999606253. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2013. Registered share capital is NOK 45,000, divided into 45 shares. The company's stated purpose is: “Å drive kontorfellesskap for samarbeidende leger ved Maudbukta Legekontor.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK −20,000
Equity
NOK 223,000
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns MAUDBUKTA LEGEKONTOR AS?

SVERRE THORSTENSEN
MAUDBUKTA LEGEKONTOR AS
NOK 3.6m rev. · NOK −20,000 profit

MAUDBUKTA LEGEKONTOR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAUDBUKTA LEGEKONTOR AS

Who owns MAUDBUKTA LEGEKONTOR AS?

SVERRE THORSTENSEN is the largest registered owner, with 33.3%.

What is the revenue of MAUDBUKTA LEGEKONTOR AS?

MAUDBUKTA LEGEKONTOR AS had revenue of NOK 3.6m in 2024.

Who is the general manager of MAUDBUKTA LEGEKONTOR AS?

Berit Marstein is registered as general manager of MAUDBUKTA LEGEKONTOR AS.

Where is MAUDBUKTA LEGEKONTOR AS based?

MAUDBUKTA LEGEKONTOR AS has its business address in Vollen.

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.