BIZTRAC BETA
Other technical consultancy

FO HOLDING AS

Org. no. 989191292 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 530,000
Equity NOK 3.9m
Incorporated 2005
Share capital NOK 713,000

FO HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 989191292. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2005. Registered share capital is NOK 713,000, divided into 713332 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskap, samt hva som naturlig faller inn under dette. Salg av tekniske og administrative konsulenttjenester herunder utleie av personell.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 530,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 530,000
Equity
NOK 3.9m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns FO HOLDING AS?

FRODE OLSEN
FO HOLDING AS
NOK 2.0m rev. · NOK 530,000 profit

FO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FO HOLDING AS own?

FO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FO HOLDING AS

Who owns FO HOLDING AS?

FRODE OLSEN is the largest registered owner, with 100.0%.

What is the revenue of FO HOLDING AS?

FO HOLDING AS had revenue of NOK 2.0m in 2024.

Who is the general manager of FO HOLDING AS?

Frode Olsen is registered as general manager of FO HOLDING AS.

Where is FO HOLDING AS based?

FO HOLDING AS has its business address in Kristiansand S.

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.