BIZTRAC BETA
Freight coastal transport

FJELD SVEA AS

Org. no. 933225178 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 44.3m
Operating profit NOK −26.3m
Equity NOK −20.3m
Incorporated 2024
Share capital NOK 40,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−20,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−26,3 mill kr).

FJELD SVEA AS is registered as a limited company in Oslo, Oslo with organisation number 933225178. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 10000 shares. The company's stated purpose is: “Å eie og drive skip, samt annen tilknyttet virksomhet, samt investere i selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 44.3m in revenue and NOK −26.3m in operating profit.

Key figures · 2024

Revenue
NOK 44.3m
Operating profit
NOK −26.3m
Equity
NOK −20.3m

Financial health · 2025

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

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

Who owns FJELD SVEA AS?

BLUE FJD AS
FJELD SVEA AS
NOK 44.3m rev. · NOK −26.3m profit

FJELD SVEA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJELD SVEA AS

Who owns FJELD SVEA AS?

BLUE FJD AS is the largest registered owner, with 100.0%.

What is the revenue of FJELD SVEA AS?

FJELD SVEA AS had revenue of NOK 44.3m in 2024.

Who is the general manager of FJELD SVEA AS?

Sissel Grefsrud is registered as general manager of FJELD SVEA AS.

Where is FJELD SVEA AS based?

FJELD SVEA AS has its business address in Oslo.

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.