BIZTRAC BETA
Rental and operating of own or leased real estate

MARKVEIEN 39 AS

Org. no. 829705222 Limited company (AS) Alta Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −372,000
Equity NOK −807,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

MARKVEIEN 39 AS is registered as a limited company in Alta, Finnmark with organisation number 829705222. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendom med og uten bebyggelse, kjøp og salg og utvikling av eiendom og bygg, oppføring av boliger og næringsbygg for utleie og salg, utleie og drift av bolig, næringsbygg og eiendom samt deltagelse i andre selskaper og alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −372,000
Equity
NOK −807,000

Financial health · 2025

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

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

Who owns MARKVEIEN 39 AS?

NORDLYSBYEN EIENDOM AS
MARKVEIEN 39 AS
· NOK −372,000 profit

MARKVEIEN 39 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARKVEIEN 39 AS

Who owns MARKVEIEN 39 AS?

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

Where is MARKVEIEN 39 AS based?

MARKVEIEN 39 AS has its business address in Alta.

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.