BIZTRAC BETA
Buying and selling of own real estate

MILITARIUM AS

Org. no. 915239552 Limited company (AS) Tønsberg Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −58,000
Equity NOK 8.3m
Incorporated 2015
Share capital NOK 26.2m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−58k kr).

MILITARIUM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 915239552. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 26.2m, divided into 747357 shares. The company's stated purpose is: “Investering i aksjer, andeler og verdipapirer”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −58,000
Equity
NOK 8.3m
Est. value
NOK 5.9m

Financial health · 2024

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

Who owns MILITARIUM AS?

BJØRN J. HANSEN HOLDING AS
MILITARIUM AS
NOK 0 rev. · NOK −58,000 profit

MILITARIUM AS has 13 registered shareholders:

All shareholders and roles →

Which companies does MILITARIUM AS own?

MILITARIUM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MILITARIUM AS

Who owns MILITARIUM AS?

BJØRN J. HANSEN HOLDING AS is the largest registered owner, with 34.8%.

What is the revenue of MILITARIUM AS?

MILITARIUM AS had revenue of NOK 0 in 2024.

Who is the general manager of MILITARIUM AS?

Bjørn Jemtegård Hansen is registered as general manager of MILITARIUM AS.

Where is MILITARIUM AS based?

MILITARIUM AS has its business address in Tønsberg.

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.