BIZTRAC BETA
Rental and operating of own or leased real estate

ALMEDALSVEIEN 6 AS

Org. no. 980119521 Limited company (AS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 3.1m
Equity NOK 8.4m
Incorporated 1998
Share capital NOK 8.1m

Signals

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

ALMEDALSVEIEN 6 AS is registered as a limited company in Oslo, Oslo with organisation number 980119521. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 8.1m, divided into 500 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 3.1m
Equity
NOK 8.4m
Est. value
NOK 12.5m

Financial health · 2024

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

Who owns ALMEDALSVEIEN 6 AS?

ALMEDALSVEIEN HOLDING AS
ALMEDALSVEIEN 6 AS
NOK 4.6m rev. · NOK 3.1m profit

ALMEDALSVEIEN 6 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ALMEDALSVEIEN 6 AS er morselskap for 1 datterselskap:

Frequently asked questions about ALMEDALSVEIEN 6 AS

Who owns ALMEDALSVEIEN 6 AS?

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

What is the revenue of ALMEDALSVEIEN 6 AS?

ALMEDALSVEIEN 6 AS had revenue of NOK 4.6m in 2024.

Where is ALMEDALSVEIEN 6 AS based?

ALMEDALSVEIEN 6 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 15.06.2026.

Report a problem

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