BIZTRAC BETA
Other technical consultancy

08 OSLO MARITIME AS

Org. no. 825769242 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 717,000
Operating profit NOK 613,000
Equity NOK 3.0m
Incorporated 2020
Share capital NOK 30,000

08 OSLO MARITIME AS is registered as a limited company in Oslo, Oslo with organisation number 825769242. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby konsulenttjenester innen maritim sektor og investering i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 717,000 in revenue and NOK 613,000 in operating profit.

Key figures · 2025

Revenue
NOK 717,000
Operating profit
NOK 613,000
Equity
NOK 3.0m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns 08 OSLO MARITIME AS?

HANS-CHRISTIAN OPSANN
08 OSLO MARITIME AS
NOK 717,000 rev. · NOK 613,000 profit

08 OSLO MARITIME AS has 1 registered shareholder:

All shareholders and roles →

Which companies does 08 OSLO MARITIME AS own?

08 OSLO MARITIME AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about 08 OSLO MARITIME AS

Who owns 08 OSLO MARITIME AS?

HANS-CHRISTIAN OPSANN is the largest registered owner, with 100.0%.

What is the revenue of 08 OSLO MARITIME AS?

08 OSLO MARITIME AS had revenue of NOK 717,000 in 2025.

Who is the general manager of 08 OSLO MARITIME AS?

Hans-Christian Opsann is registered as general manager of 08 OSLO MARITIME AS.

Where is 08 OSLO MARITIME AS based?

08 OSLO MARITIME 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.