BIZTRAC BETA
Accounting and bookkeeping

FLYT ØKONOMI AS

Org. no. 932829894 Limited company (AS) Bodø Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 37,000
Equity NOK 171,000
Incorporated 2024
Employees 8
Share capital NOK 30,000

FLYT ØKONOMI AS is registered as a limited company in Bodø, Nordland with organisation number 932829894. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive regnskapskontor, yte konsulenttjenester, forretningsførsel og tjenester som er knyttet til regnskaps- og rådgivningsvirksomhet, herunder all virksomhet som naturlig faller inn under dette, samt investering i andre selskaper og aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 37,000
Equity
NOK 171,000
Est. value
NOK 333,000

Financial health · 2025

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

Who owns FLYT ØKONOMI AS?

FLYT BODØ AS
FLYT ØKONOMI AS
NOK 8.7m rev. · NOK 37,000 profit

FLYT ØKONOMI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLYT ØKONOMI AS

Who owns FLYT ØKONOMI AS?

FLYT BODØ AS is the largest registered owner, with 100.0%.

What is the revenue of FLYT ØKONOMI AS?

FLYT ØKONOMI AS had revenue of NOK 8.7m in 2025.

Who is the general manager of FLYT ØKONOMI AS?

Trine Bruun Olsen is registered as general manager of FLYT ØKONOMI AS.

Where is FLYT ØKONOMI AS based?

FLYT ØKONOMI 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.