BIZTRAC BETA
COMPANY REGISTER PROFILE
918567445 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Freight ocean transport

FONNES MANAGEMENT AS

Org. no. 918567445 Limited company (AS) Austrheim Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −88,000
Equity NOK −3.9m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,9 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−88k kr).

FONNES MANAGEMENT AS is registered as a limited company in Austrheim, Vestland with organisation number 918567445. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og drive skip, skipsfart, og alt som er naturlig forbundet med dette, herunder også salg av varer og tjenester. Selskapet kan også delta med eierinteresser i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −88,000
▼ −87 %
Equity
NOK −3.9m
▼ −93 %

Financial health · 2025

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

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

Who owns FONNES MANAGEMENT AS?

FONNES MANAGEMENT AS
· NOK −88,000 profit

FONNES MANAGEMENT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FONNES MANAGEMENT AS

Who owns FONNES MANAGEMENT AS?

ROY OVE FONNES is the largest registered owner, with 50.0%.

Who is the general manager of FONNES MANAGEMENT AS?

Roy Ove Fonnes is registered as general manager of FONNES MANAGEMENT AS.

Where is FONNES MANAGEMENT AS based?

FONNES MANAGEMENT AS has its business address in Fonnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.