BIZTRAC BETA
Rental and operating of own or leased real estate

TURBINVEIEN 2-4 AS

Org. no. 929810791 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 130,000
Operating profit NOK −9.9m
Equity NOK 42.4m
Incorporated 2022
Share capital NOK 14.7m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9,9 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TURBINVEIEN 2-4 AS is registered as a limited company in Oslo, Oslo with organisation number 929810791. 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 14.7m, divided into 14658495 shares. The company's stated purpose is: “Utvikling, drift og utleie av eiendom samt annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 130,000 in revenue and NOK −9.9m in operating profit.

Key figures · 2025

Revenue
NOK 130,000
Operating profit
NOK −9.9m
Equity
NOK 42.4m
Est. value
NOK 38.7m

Financial health · 2025

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

Who owns TURBINVEIEN 2-4 AS?

OBOS EIENDOM AS
TURBINVEIEN 2-4 AS
NOK 130,000 rev. · NOK −9.9m profit

TURBINVEIEN 2-4 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TURBINVEIEN 2-4 AS

Who owns TURBINVEIEN 2-4 AS?

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

What is the revenue of TURBINVEIEN 2-4 AS?

TURBINVEIEN 2-4 AS had revenue of NOK 130,000 in 2025.

Where is TURBINVEIEN 2-4 AS based?

TURBINVEIEN 2-4 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.