BIZTRAC BETA
Development of building projects

SMØLA EIENDOM AS

Org. no. 930081019 Limited company (AS) Smøla Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK −152,000
Equity NOK 720,000
Incorporated 2022
Share capital NOK 659,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−152k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SMØLA EIENDOM AS is registered as a limited company in Smøla, Møre og Romsdal with organisation number 930081019. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 659,000, divided into 30 shares. The company's stated purpose is: “Oppføre byggearbeider i egenregi for deretter salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK −152,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
Operating profit
NOK −152,000
Equity
NOK 720,000
Est. value
NOK 10.3m

Financial health · 2025

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

Who owns SMØLA EIENDOM AS?

SMØLA HOLDING AS
SMØLA EIENDOM AS
NOK 6.5m rev. · NOK −152,000 profit

SMØLA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SMØLA EIENDOM AS er morselskap for 4 datterselskaper:

Frequently asked questions about SMØLA EIENDOM AS

Who owns SMØLA EIENDOM AS?

SMØLA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SMØLA EIENDOM AS?

SMØLA EIENDOM AS had revenue of NOK 6.5m in 2025.

Where is SMØLA EIENDOM AS based?

SMØLA EIENDOM AS has its business address in Smøla.

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.