biztrac. BETA
COMPANY REGISTER PROFILE
956479142 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

ØKONOMIKONSULENT ATLE FLØ

Org. no. 956479142 Sole proprietorship (ENK) Ulstein Active
Ownership graph ↗
Revenue 2024 NOK 670,000
Operating profit NOK 476,000
Equity NOK −115,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−115k kr).

ØKONOMIKONSULENT ATLE FLØ is registered as a sole proprietorship in Ulstein, Møre og Romsdal with organisation number 956479142. The business is classified under business and other management consultancy activities (NACE 70.200). The most recent filed accounts, for the 2024 financial year, show NOK 670,000 in revenue and NOK 476,000 in operating profit.

Former names: ØKO-CONSULT Atle Birger Flø, STATSAUTORISERT REVISOR ATLE BIRGER FLØ

Key figures · 2024

Revenue
NOK 670,000
▲ +69 %
Operating profit
NOK 476,000
▲ +90 %
Equity
NOK −115,000
▼ −66 %
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-452.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØKONOMIKONSULENT ATLE FLØ?

No shareholders are registered for ØKONOMIKONSULENT ATLE FLØ in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ØKONOMIKONSULENT ATLE FLØ

What is the revenue of ØKONOMIKONSULENT ATLE FLØ?

ØKONOMIKONSULENT ATLE FLØ had revenue of NOK 670,000 in 2024.

Who is the general manager of ØKONOMIKONSULENT ATLE FLØ?

Atle Birger Flø is registered as general manager of ØKONOMIKONSULENT ATLE FLØ.

Where is ØKONOMIKONSULENT ATLE FLØ based?

ØKONOMIKONSULENT ATLE FLØ has its business address in Ulsteinvik.

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.