BIZTRAC BETA
General medical practice activities

FORNEBULYS LEGEKONTOR AS

Org. no. 931631438 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 125,000
Equity NOK 173,000
Incorporated 2023
Share capital NOK 30,000

FORNEBULYS LEGEKONTOR AS is registered as a limited company in Bærum, Akershus with organisation number 931631438. 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 30 shares. The company's stated purpose is: “Drift av legekontor og helsetjenester. Kjøp og salg av produkter som naturlig hører inn under dette. Deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 125,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 125,000
Equity
NOK 173,000
Est. value
NOK 678,000

Financial health · 2024

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.6%
Good
Equity as a share of total capital

Who owns FORNEBULYS LEGEKONTOR AS?

PORYA HAKIMNEJAD
FORNEBULYS LEGEKONTOR AS
NOK 2.6m rev. · NOK 125,000 profit

FORNEBULYS LEGEKONTOR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FORNEBULYS LEGEKONTOR AS

Who owns FORNEBULYS LEGEKONTOR AS?

PORYA HAKIMNEJAD is the largest registered owner, with 50.0%.

What is the revenue of FORNEBULYS LEGEKONTOR AS?

FORNEBULYS LEGEKONTOR AS had revenue of NOK 2.6m in 2024.

Who is the general manager of FORNEBULYS LEGEKONTOR AS?

Porya Hakimnejad is registered as general manager of FORNEBULYS LEGEKONTOR AS.

Where is FORNEBULYS LEGEKONTOR AS based?

FORNEBULYS LEGEKONTOR AS has its business address in Fornebu.

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.