BIZTRAC BETA
Rental and operating of own or leased real estate

ISAKVEIEN AS

Org. no. 991423028 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK 7.5m
Equity NOK 52.1m
Incorporated 2007
Share capital NOK 191,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-10 Adresseendring registrert 2026-06-10.

ISAKVEIEN AS is registered as a limited company in Oslo, Oslo with organisation number 991423028. 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 191,000, divided into 4024 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 8.8m in revenue and NOK 7.5m in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK 7.5m
Equity
NOK 52.1m
Est. value
NOK 53.7m

Financial health · 2025

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

Who owns ISAKVEIEN AS?

ØST BYGG & HANDEL AS
ISAKVEIEN AS
NOK 8.8m rev. · NOK 7.5m profit

ISAKVEIEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ISAKVEIEN AS er morselskap for 2 datterselskaper:

Frequently asked questions about ISAKVEIEN AS

Who owns ISAKVEIEN AS?

ØST BYGG & HANDEL AS is the largest registered owner, with 100.0%.

What is the revenue of ISAKVEIEN AS?

ISAKVEIEN AS had revenue of NOK 8.8m in 2024.

Where is ISAKVEIEN AS based?

ISAKVEIEN 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.