biztrac. BETA
COMPANY REGISTER PROFILE
991271643 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

MARKVEIEN 42 AS

Org. no. 991271643 Limited company (AS) Oslo Incorporated 2007 Active
Revenue 2025 NOK 1.4m
Operating profit NOK 641,000
Equity NOK 8.5m
Incorporated 2007
Share capital NOK 100,000

Signals

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

MARKVEIEN 42 AS is registered as a limited company in Oslo, Oslo with organisation number 991271643. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Deltagelse i andre selskaper/virksomheter, kjøp og salg av eiendom og utleie av eiendom, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 641,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▲ +162 %
Operating profit
NOK 641,000
▲ +49 %
Equity
NOK 8.5m
▲ +8 %
Est. value
NOK 7.9m

Financial health · 2025

Liquidity
4.90
Very good
Current assets ÷ current liabilities
Profitability
8.7%
Satisfactory
Return on total assets
Solidity
90.3%
Very good
Equity as a share of total capital

Who owns MARKVEIEN 42 AS?

MARKVEIEN 42 AS
NOK 1.4m rev. · NOK 641,000 profit

MARKVEIEN 42 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARKVEIEN 42 AS

Who owns MARKVEIEN 42 AS?

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

What is the revenue of MARKVEIEN 42 AS?

MARKVEIEN 42 AS had revenue of NOK 1.4m in 2025.

Where is MARKVEIEN 42 AS based?

MARKVEIEN 42 AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.