BIZTRAC BETA
Rental and operating of own or leased real estate

MARVIKA ORLOGSTASJON AS

Org. no. 820992032 Limited company (AS) Kristiansand Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 4.5m
Equity NOK 10.0m
Incorporated 2018
Share capital NOK 60,000

Signals

1 flags
  • Nylig endring 2026-03-04 Adresseendring registrert 2026-03-04.

MARVIKA ORLOGSTASJON AS is registered as a limited company in Kristiansand, Agder with organisation number 820992032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Investering i, drift og utvikling av fast eiendom, investering i aksjer og verdipapirer samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 4.5m in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 4.5m
Equity
NOK 10.0m
Est. value
NOK 11.8m

Financial health · 2024

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

Who owns MARVIKA ORLOGSTASJON AS?

KRISTIANSAND NÆRINGSSELSKAP AS
MARVIKA ORLOGSTASJON AS
NOK 6.6m rev. · NOK 4.5m profit

MARVIKA ORLOGSTASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARVIKA ORLOGSTASJON AS

Who owns MARVIKA ORLOGSTASJON AS?

KRISTIANSAND NÆRINGSSELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of MARVIKA ORLOGSTASJON AS?

MARVIKA ORLOGSTASJON AS had revenue of NOK 6.6m in 2024.

Where is MARVIKA ORLOGSTASJON AS based?

MARVIKA ORLOGSTASJON AS has its business address in Kristiansand S.

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.