BIZTRAC BETA
Retail sale of pleasure boats and equipment

OSLO FJORDSERVICE AS

Org. no. 988210056 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK −1.7m
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

OSLO FJORDSERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 988210056. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Service for fritidsbåter og båtforeninger, dykkeroppdrag, salg og import av båter og motorer, båtutleie samt vinteropplag for båter. Entreprenørvirksomhet innen bygg og anlegg. Forvaltning og utleie av eiendom. Deltagelse i andre selskaper med dertil egnet virksomhet.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK −1.7m

Financial health · 2024

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

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

Who owns OSLO FJORDSERVICE AS?

HANS HERMAN BEHRENS
OSLO FJORDSERVICE AS
· NOK −12,000 profit

OSLO FJORDSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSLO FJORDSERVICE AS

Who owns OSLO FJORDSERVICE AS?

HANS HERMAN BEHRENS is the largest registered owner, with 90.0%.

Who is the general manager of OSLO FJORDSERVICE AS?

Hans Herman Behrens is registered as general manager of OSLO FJORDSERVICE AS.

Where is OSLO FJORDSERVICE AS based?

OSLO FJORDSERVICE 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.