BIZTRAC BETA
Development of building projects

MÅRSTIG BOLIG AS

Org. no. 924718862 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −44,000
Equity NOK −239,000
Incorporated 2020
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−239k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−44k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MÅRSTIG BOLIG AS is registered as a limited company in Bergen, Vestland with organisation number 924718862. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bolig- og tomteutvikling samt andre produkter/tjenester som naturlig hører sammen med dette, herunder delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −44,000
Equity
NOK −239,000

Financial health · 2024

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

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

Who owns MÅRSTIG BOLIG AS?

MÅRSTIG HOLDING AS
MÅRSTIG BOLIG AS
· NOK −44,000 profit

MÅRSTIG BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MÅRSTIG BOLIG AS er morselskap for 5 datterselskaper:

Frequently asked questions about MÅRSTIG BOLIG AS

Who owns MÅRSTIG BOLIG AS?

MÅRSTIG HOLDING AS is the largest registered owner, with 100.0%.

Where is MÅRSTIG BOLIG AS based?

MÅRSTIG BOLIG AS has its business address in Hylkje.

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.