BIZTRAC BETA
General medical practice activities

BORGUND LEGEKONTOR AS

Org. no. 898796922 Limited company (AS) Ålesund Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 939
Equity NOK −76,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−76k kr).

BORGUND LEGEKONTOR AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 898796922. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive legesenter med alt det innebærer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 939 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 939
Equity
NOK −76,000
Est. value
NOK 7,000

Financial health · 2025

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BORGUND LEGEKONTOR AS?

SHIVA BADIEE
BORGUND LEGEKONTOR AS
NOK 3.0m rev. · NOK 939 profit

BORGUND LEGEKONTOR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BORGUND LEGEKONTOR AS

Who owns BORGUND LEGEKONTOR AS?

SHIVA BADIEE is the largest registered owner, with 50.0%.

What is the revenue of BORGUND LEGEKONTOR AS?

BORGUND LEGEKONTOR AS had revenue of NOK 3.0m in 2025.

Who is the general manager of BORGUND LEGEKONTOR AS?

Ole Reza Drønen is registered as general manager of BORGUND LEGEKONTOR AS.

Where is BORGUND LEGEKONTOR AS based?

BORGUND LEGEKONTOR AS has its business address in Ålesund.

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.