biztrac. BETA
COMPANY REGISTER PROFILE
913315324 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

MMO HOLDING AS

Org. no. 913315324 Limited company (AS) Bamble Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 9.7m
Incorporated 2014
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

MMO HOLDING AS is registered as a limited company in Bamble, Telemark with organisation number 913315324. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Eierskap i andre aksjeselskap, og hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Former names: JØIJE HOLDING AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
▲ +48 %
Equity
NOK 9.7m
▼ −8 %
Est. value
NOK 9.1m

Financial health · 2025

Liquidity
2836.07
Very good
Current assets ÷ current liabilities
Profitability
6.2%
Satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns MMO HOLDING AS?

MMO HOLDING AS
NOK 0 rev. · NOK −9,000 profit

MMO HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MMO HOLDING AS own?

MMO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MMO HOLDING AS

Who owns MMO HOLDING AS?

Kim Tore Berg Olsen is the largest registered owner, with 50.0%.

What is the revenue of MMO HOLDING AS?

MMO HOLDING AS had revenue of NOK 0 in 2025.

Where is MMO HOLDING AS based?

MMO HOLDING AS has its business address in Langesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.