BIZTRAC BETA
Other education activities

FLIGHTSAFETY INTERNATIONAL NORWAY AS

Org. no. 897712202 Limited company (AS) Sola Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 38.9m
Operating profit NOK 809,000
Equity NOK 44.0m
Incorporated 2011
Employees 6
Share capital NOK 100,000

FLIGHTSAFETY INTERNATIONAL NORWAY AS is registered as a limited company in Sola, Rogaland with organisation number 897712202. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Luftfartsopplæring, relaterte forretningsformål og alle andre lovlige forretningsformål.”. The most recent filed accounts, for the 2024 financial year, show NOK 38.9m in revenue and NOK 809,000 in operating profit.

Key figures · 2024

Revenue
NOK 38.9m
Operating profit
NOK 809,000
Equity
NOK 44.0m
Est. value
NOK 33.0m

Financial health · 2024

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

Who owns FLIGHTSAFETY INTERNATIONAL NORWAY AS?

FLIGHT SAFETY INTERNATIONAL INC
FLIGHTSAFETY INTERNATIONAL NORWAY AS
NOK 38.9m rev. · NOK 809,000 profit

FLIGHTSAFETY INTERNATIONAL NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLIGHTSAFETY INTERNATIONAL NORWAY AS

Who owns FLIGHTSAFETY INTERNATIONAL NORWAY AS?

FLIGHT SAFETY INTERNATIONAL INC is the largest registered owner, with 100.0%.

What is the revenue of FLIGHTSAFETY INTERNATIONAL NORWAY AS?

FLIGHTSAFETY INTERNATIONAL NORWAY AS had revenue of NOK 38.9m in 2024.

Where is FLIGHTSAFETY INTERNATIONAL NORWAY AS based?

FLIGHTSAFETY INTERNATIONAL NORWAY AS has its business address in Sola.

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.