BIZTRAC BETA
Rental and operating of own or leased real estate

SMESTADMOEN NÆRINGSBYGG AS

Org. no. 921800908 Limited company (AS) Gjøvik Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −1.8m
Equity NOK 20.1m
Incorporated 2018
Share capital NOK 1.0m

Signals

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

SMESTADMOEN NÆRINGSBYGG AS is registered as a limited company in Gjøvik, Innlandet with organisation number 921800908. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Investere i næringseiendom, herunder å delta i andre selskaper med lignende virksomhet og hva som hermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −1.8m
Equity
NOK 20.1m
Est. value
NOK 15.5m

Financial health · 2024

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.3%
Satisfactory
Equity as a share of total capital

Who owns SMESTADMOEN NÆRINGSBYGG AS?

MIRAMARE CAPITAL AS
SMESTADMOEN NÆRINGSBYGG AS
· NOK −1.8m profit

SMESTADMOEN NÆRINGSBYGG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SMESTADMOEN NÆRINGSBYGG AS own?

SMESTADMOEN NÆRINGSBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SMESTADMOEN NÆRINGSBYGG AS

Who owns SMESTADMOEN NÆRINGSBYGG AS?

MIRAMARE CAPITAL AS is the largest registered owner, with 92.0%.

Where is SMESTADMOEN NÆRINGSBYGG AS based?

SMESTADMOEN NÆRINGSBYGG AS has its business address in Biri.

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.