BIZTRAC BETA
Development of building projects

STOREBRAND LURAMYRVEIEN 11 AS

Org. no. 988148784 Limited company (AS) Surnadal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 552,000
Equity NOK 60.2m
Incorporated 2005
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STOREBRAND LURAMYRVEIEN 11 AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 988148784. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte eiendommen, og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 552,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 552,000
Equity
NOK 60.2m
Est. value
NOK 43.0m

Financial health · 2024

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

Who owns STOREBRAND LURAMYRVEIEN 11 AS?

STOREBRAND EIENDOM TRYGG AS
STOREBRAND LURAMYRVEIEN 11 AS
NOK 1.1m rev. · NOK 552,000 profit

STOREBRAND LURAMYRVEIEN 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOREBRAND LURAMYRVEIEN 11 AS

Who owns STOREBRAND LURAMYRVEIEN 11 AS?

STOREBRAND EIENDOM TRYGG AS is the largest registered owner, with 100.0%.

What is the revenue of STOREBRAND LURAMYRVEIEN 11 AS?

STOREBRAND LURAMYRVEIEN 11 AS had revenue of NOK 1.1m in 2024.

Where is STOREBRAND LURAMYRVEIEN 11 AS based?

STOREBRAND LURAMYRVEIEN 11 AS has its business address in Surnadal.

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.