BIZTRAC BETA
Rental and operating of own or leased real estate

MARIDALSVEIEN 266 AS

Org. no. 985822018 Limited company (AS) Asker Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 803,000
Equity NOK 2.6m
Incorporated 2003
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.

MARIDALSVEIEN 266 AS is registered as a limited company in Asker, Akershus with organisation number 985822018. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forvalte fast eiendom eller deler derav, samt eie, kjøpe eller selge andeler og dessuten forvalte, eie, kjøpe og selge aksjer og fondsandeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 803,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 803,000
Equity
NOK 2.6m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns MARIDALSVEIEN 266 AS?

SOLVIK HOLDING AS
MARIDALSVEIEN 266 AS
NOK 1.2m rev. · NOK 803,000 profit

MARIDALSVEIEN 266 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARIDALSVEIEN 266 AS

Who owns MARIDALSVEIEN 266 AS?

SOLVIK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MARIDALSVEIEN 266 AS?

MARIDALSVEIEN 266 AS had revenue of NOK 1.2m in 2024.

Where is MARIDALSVEIEN 266 AS based?

MARIDALSVEIEN 266 AS has its business address in Billingstad.

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.