BIZTRAC BETA
Retail sale of pleasure boats and equipment

MARITIM CENTER EIENDOM AS

Org. no. 897558092 Limited company (AS) Tromsø Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 1.2m
Equity NOK 4.1m
Incorporated 2011
Share capital NOK 740,000

MARITIM CENTER EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 897558092. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 2011. Registered share capital is NOK 740,000, divided into 740 shares. The company's stated purpose is: “Investering av fast eiendom, herunder kjøp, salg, leie og utleie av fast eiendom og alt som for øvrig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 1.2m
Equity
NOK 4.1m
Est. value
NOK 4.9m

Financial health · 2024

Liquidity
0.66
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.1%
Good
Equity as a share of total capital

Who owns MARITIM CENTER EIENDOM AS?

MARITIM HOLDING AS
MARITIM CENTER EIENDOM AS
NOK 2.1m rev. · NOK 1.2m profit

MARITIM CENTER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARITIM CENTER EIENDOM AS

Who owns MARITIM CENTER EIENDOM AS?

MARITIM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MARITIM CENTER EIENDOM AS?

MARITIM CENTER EIENDOM AS had revenue of NOK 2.1m in 2024.

Who is the general manager of MARITIM CENTER EIENDOM AS?

Asle Roar Olaussen is registered as general manager of MARITIM CENTER EIENDOM AS.

Where is MARITIM CENTER EIENDOM AS based?

MARITIM CENTER EIENDOM AS has its business address in Tromsø.

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.