BIZTRAC BETA
Rental and operating of own or leased real estate

MØRING AS

Org. no. 912861228 Limited company (AS) Stranda Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −93,000
Equity NOK −6.1m
Incorporated 2013
Share capital NOK 5.5m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−6,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−93k kr).

MØRING AS is registered as a limited company in Stranda, Møre og Romsdal with organisation number 912861228. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 5.5m, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −93,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −93,000
Equity
NOK −6.1m

Financial health · 2024

Liquidity
157.65
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.3%
Weak
Equity as a share of total capital

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

Who owns MØRING AS?

KJØLÅS STANSEKNIVER AS
MØRING AS
NOK 0 rev. · NOK −93,000 profit

MØRING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MØRING AS own?

MØRING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MØRING AS

Who owns MØRING AS?

KJØLÅS STANSEKNIVER AS is the largest registered owner, with 50.0%.

What is the revenue of MØRING AS?

MØRING AS had revenue of NOK 0 in 2024.

Where is MØRING AS based?

MØRING AS has its business address in Stranda.

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.