biztrac. BETA
COMPANY REGISTER PROFILE
922884579 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

NORGES FLYMEDISINSKE SENTER AS

Org. no. 922884579 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 10.3m
Operating profit NOK 989,000
Equity NOK 450,000
Incorporated 2019
Employees 11
Share capital NOK 30,000

NORGES FLYMEDISINSKE SENTER AS is registered as a limited company in Oslo, Oslo with organisation number 922884579. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utstedelser av flymedisinske godkjenninger til sivilt flygende personell.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.3m in revenue and NOK 989,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.3m
▲ +294 %
Operating profit
NOK 989,000
▲ +2188 %
Equity
NOK 450,000
▲ +575 %
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
69.0%
Very good
Return on total assets
Solidity
25.0%
Good
Equity as a share of total capital

Who owns NORGES FLYMEDISINSKE SENTER AS?

NORGES FLYMEDISINSKE SENTER AS
NOK 10.3m rev. · NOK 989,000 profit

NORGES FLYMEDISINSKE SENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORGES FLYMEDISINSKE SENTER AS

Who owns NORGES FLYMEDISINSKE SENTER AS?

Ståle Romstad is the largest registered owner, with 100.0%.

What is the revenue of NORGES FLYMEDISINSKE SENTER AS?

NORGES FLYMEDISINSKE SENTER AS had revenue of NOK 10.3m in 2025.

Where is NORGES FLYMEDISINSKE SENTER AS based?

NORGES FLYMEDISINSKE SENTER 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.