BIZTRAC BETA
Other captive investment companies

STINE MARIE MØLLEROP HOLDING AS

Org. no. 814498182 Limited company (AS) Indre Østfold Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −107
Equity NOK 49,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

STINE MARIE MØLLEROP HOLDING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 814498182. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Foreta investering i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −107
Equity
NOK 49,000
Est. value
NOK 134,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STINE MARIE MØLLEROP HOLDING AS?

STINE MARIE MØLLEROP
STINE MARIE MØLLEROP HOLDING AS
· NOK −107 profit

STINE MARIE MØLLEROP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STINE MARIE MØLLEROP HOLDING AS own?

STINE MARIE MØLLEROP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STINE MARIE MØLLEROP HOLDING AS

Who owns STINE MARIE MØLLEROP HOLDING AS?

STINE MARIE MØLLEROP is the largest registered owner, with 100.0%.

Who is the general manager of STINE MARIE MØLLEROP HOLDING AS?

Stine Marie Møllerop is registered as general manager of STINE MARIE MØLLEROP HOLDING AS.

Where is STINE MARIE MØLLEROP HOLDING AS based?

STINE MARIE MØLLEROP HOLDING AS has its business address in Spydeberg.

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.