BIZTRAC BETA
Rental and operating of own or leased real estate

TVETENVEIEN 40 EIENDOM AS

Org. no. 919680954 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 2.4m
Equity NOK 18.6m
Incorporated 2017
Share capital NOK 830,000

Signals

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

TVETENVEIEN 40 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 919680954. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 830,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.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 2.4m
Equity
NOK 18.6m
Est. value
NOK 17.0m

Financial health · 2025

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

Who owns TVETENVEIEN 40 EIENDOM AS?

DRAMMEN INTERIØRPARK AS
TVETENVEIEN 40 EIENDOM AS
NOK 5.3m rev. · NOK 2.4m profit

TVETENVEIEN 40 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TVETENVEIEN 40 EIENDOM AS

Who owns TVETENVEIEN 40 EIENDOM AS?

DRAMMEN INTERIØRPARK AS is the largest registered owner, with 100.0%.

What is the revenue of TVETENVEIEN 40 EIENDOM AS?

TVETENVEIEN 40 EIENDOM AS had revenue of NOK 5.3m in 2025.

Where is TVETENVEIEN 40 EIENDOM AS based?

TVETENVEIEN 40 EIENDOM 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.