BIZTRAC BETA
Rental and operating of own or leased real estate

TVERRVEIEN 3 HOLDING AS

Org. no. 834071932 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −102,000
Equity NOK 18.5m
Incorporated 2024
Share capital NOK 40,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−102k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-07-08 Avregistrert registrert 2026-07-08.

TVERRVEIEN 3 HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 834071932. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 1000 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.”.

Key figures · 2025

Operating profit
NOK −102,000
Equity
NOK 18.5m
Est. value
NOK 16.8m

Financial health · 2025

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

Who owns TVERRVEIEN 3 HOLDING AS?

MALLING HANDELSEIENDOM HOLDING AS
TVERRVEIEN 3 HOLDING AS
· NOK −102,000 profit

TVERRVEIEN 3 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TVERRVEIEN 3 HOLDING AS own?

TVERRVEIEN 3 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TVERRVEIEN 3 HOLDING AS

Who owns TVERRVEIEN 3 HOLDING AS?

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

Where is TVERRVEIEN 3 HOLDING AS based?

TVERRVEIEN 3 HOLDING 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.