BIZTRAC BETA
Other cleaning activities

NORDIC FLIGHT SERVICE AS

Org. no. 920572537 Limited company (AS) Nannestad Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 474,000
Equity NOK 2.1m
Incorporated 2018
Employees 6
Share capital NOK 30,000

NORDIC FLIGHT SERVICE AS is registered as a limited company in Nannestad, Akershus with organisation number 920572537. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2018 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tjenester knyttet til flytransport, og virksomhet som står i forbindelse med dette, herunder å delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 474,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 474,000
Equity
NOK 2.1m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns NORDIC FLIGHT SERVICE AS?

JOHN STAFFAN AHLBOM
NORDIC FLIGHT SERVICE AS
NOK 5.2m rev. · NOK 474,000 profit

NORDIC FLIGHT SERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDIC FLIGHT SERVICE AS

Who owns NORDIC FLIGHT SERVICE AS?

JOHN STAFFAN AHLBOM is the largest registered owner, with 35.0%.

What is the revenue of NORDIC FLIGHT SERVICE AS?

NORDIC FLIGHT SERVICE AS had revenue of NOK 5.2m in 2025.

Who is the general manager of NORDIC FLIGHT SERVICE AS?

John Staffan Ahlbom is registered as general manager of NORDIC FLIGHT SERVICE AS.

Where is NORDIC FLIGHT SERVICE AS based?

NORDIC FLIGHT SERVICE AS has its business address in Nannestad.

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.