BIZTRAC BETA
Freight air transport

FLYSENTERET AS

Org. no. 942840667 Limited company (AS) Bodø Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 800,000
Operating profit NOK 541,000
Equity NOK 827,000
Incorporated 1987
Share capital NOK 350,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FLYSENTERET AS is registered as a limited company in Bodø, Nordland with organisation number 942840667. The business is classified under freight air transport (NACE 51.210). The company was incorporated in 1987. Registered share capital is NOK 350,000. The company's stated purpose is: “Ved egen virksomhet eller gjennom deltagelse i andre selskap å drive luftfart eller annen virk- somhet i tilknytning til luftfart. Selskapet kan også ha interesse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 800,000 in revenue and NOK 541,000 in operating profit.

Key figures · 2024

Revenue
NOK 800,000
Operating profit
NOK 541,000
Equity
NOK 827,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns FLYSENTERET AS?

AAB NORD INVEST AS
FLYSENTERET AS
NOK 800,000 rev. · NOK 541,000 profit

FLYSENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLYSENTERET AS

Who owns FLYSENTERET AS?

AAB NORD INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of FLYSENTERET AS?

FLYSENTERET AS had revenue of NOK 800,000 in 2024.

Who is the general manager of FLYSENTERET AS?

Audun Andreas Bækø is registered as general manager of FLYSENTERET AS.

Where is FLYSENTERET AS based?

FLYSENTERET AS has its business address in Bodø.

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.